robn / consul

Perl client library for Consul

Oh hi! 👋

I'm Rob (he/him), an old time computer guy from Australia with interests in storage, hardware, operating systems, infrastructure software, embedded systems, networks and everything in between.

These days I'm working on OpenZFS, because there's a lot of data out there and it'd be nice not to lose any of it.

Let's build OpenZFS together!

OpenZFS is an open-source project with no single company behind it, and so lives or dies through the generous support of its users. But, the needs of corporate users with massive amounts of storage hardware and money to spend are often not the same as what small organisations or power users want. The parts of OpenZFS that support those users often don’t get much work because there’s no company interested in funding it, and individuals can rarely afford to hire a developer directly.

This is where you can help. I want to put some of my time into the unloved parts of OpenZFS and the surrounding community, to make sure it remains a viable option for anyone who is serious about their data. This takes many forms, from making sure OpenZFS works well as newer operating system updates arrive, to making sure lesser used features continue to work well; from answering questions and taking ideas, to presenting at user groups and conferences.

These things take time, money, or both, and your support will allow me to help keep OpenZFS available as a modern, powerful data storage platform for all kinds of data and all kinds of users.

consul's Issues

Check and update ACL support for consul >= 1.4.0

Consul changed the ACL subsystem in 1.4.0. See here: https://www.consul.io/docs/acl/acl-system.html

Its possible this is just robn/Test-Consul#7, and then remove the skip_all from t/20-acl-api.t.

Agent::service_register crashes if service is a string

service_register can take a Consul::Service or a string as its first param. If a string, its supposed to create a Consul::Service, but the constructor args are wrong.

Require specific version of Type::Utils

http://www.cpantesters.org/cpan/report/a079b966-6bf3-1014-8315-ad5b5711512c

It fails with 0.038. It succeeds with 1.002001. Somewhere in between, I guess.

0.7 KV transaction API

Hello, this is a friendly reminder that 0.7.0 was released about a week ago.

The main change that matters for this distro is the kv API now supports a txn endpoint for doing transactional kv and locking stuff.

Also, robn/Test-Consul#2 and #4 will make the upgrade path much easier since it loosens the version requirements. This bit me pretty hard. :(

Validate method params

86bf3d6 made it clear to me that I really need constraint checking on method unpacking too. I've been using compile from Type::Params elsewhere for this, and I like it a lot, so lets do that.

Consul Version requirement seems too strict.

Recently I upgraded my cluster to Consul 0.7.0, and while the API did not change much (a new endpoint was added for transactional kv calls) this module now fails to install. There is no reason this module will not work on 0.7.0.

Seems to me this module is more about supporting the v1 API rather than just a specific version of Consul. Declaring in the docs that it matches the spec of a particular version makes sense, but to wholesale block the install if a very specific version is not installed doesn't make sense to me. And, yes, I could skip the tests, and that is what I've done.

KV get_value helper method

From a user:

Otherwise there's extra checking for is this variable defined or is the value what I expect. Having a function return undef if there's nothing in the kv for that key would be useful

I think undef might be a reasonable proxy for not-found, but I think it belongs in a utility package because it doesn't quite align with the HTTP API, and there's probably other non-value conditions possible in some situations (server errors, block timeouts, etc). More thought required.

KV->get_all should return empty array when none found

Right now it returns undef, but for consistency it should return [].

Add Token Support

It doesn't appear, at least by grepping the POD, that this library supports the ability to specify a custom auth token.