mdb / concourse-consul-kv-resource

A Concourse resource for getting and setting values to and from Consul's KV store

Hello 👋

I live in Philadelphia and work as a multi-disciplinary software engineer & designer. I'm currently a Software Engineer at Warner Bros. Discovery focused on HBO Max Samsara focused on cloud infrastructure and platform engineering.

Over the years, I've developed front end web applications, created backend microservices and REST APIs, automated cloud infrastructure management, and built continuous deployment pipelines for large-scale, highly available distributed systems. I like using and contributing to open source software.

I've also worked in graphic and UX design, and as an artist. Prints of my visual work can be purchased at Tiendah.

mikeball.info is my personal website and blog.

concourse-consul-kv-resource's Issues

feature request: support specifying the ca-cert file

this is a feature request to support specifying the ca-cert file

i'm using root/intermediate/leaf pki pattern for my consul nodes, so I need to be able to specify the ca-cert file in addition to the consul client key/cert

the value is printed while doing a "get"

When I try to get a value from consul, the entire value is printed in the pipeline. i.e anyone can view it from the concourse-ui
Sample pipeline:

resources:

• name: config
  type: consul-kv
  source:
  token: my-acl-token
  host: my-consul.com
  tls_cert: my-cert-string
  tls_key: my-cert-key-string
  key: my/key

jobs:

• name: get-my-consul-key
  plan:
  • get: config

UI Output:

This enables anyone (even without access to consul) can view the KV stored in the concourse ui

This resource displays the consul value on the pipeline. Consul value contains secret variables and it needs to be hidden.

Check doesn't return current value

Hi! Thanks for making this concourse resource, it has made interacting with our consul servers in our CI pipelines very easy to work with!

I am however, unable to use the resource to trigger jobs if a consul value changes, instead it appears the checkAction returns the current date instead of the value of the key which causes concourse to trigger the job in step with the polling of the key, as opposed to when the key has changed.

Would you accept a patch that changed the ref: Date.now().toString() to value: value.value in order to get this behavior? By always returning the current version, it would appear to work with the guidance in the concourse docs around the example of a git resource having been push -f'ed over.

Thanks again for the resource!

check should only return a new version if the key's value is different from the last version

Currently, check always returns a new version. Instead, it should arguably only return a new version if the key's value in Consul is different from the Concourse resource version. It would also be useful if additional metadata were embedded in the version, such as the last time the version was updated.

Require image for ARM64 architecture

Hi Team,

I am trying to use the clapclapexcitement/concourse-consul-kv-resource image on the arm64 platform but it seems it is not available for arm64.

I have successfully built the image using the command docker build -t image_name . on the arm64 platform without making any changes in the Dockerfile.

I have used Github action to build and push the image for both the platforms.

Commit Link - odidev@7d16618

Github action link - https://github.com/odidev/concourse-consul-kv-resource/runs/3408316261?check_suite_focus=true

Docker Hub Link - https://hub.docker.com/repository/registry-1.docker.io/odidev/concourse-consul-kv-resource/tags?page=1&ordering=last_updated

Do you have any plans on releasing arm64 images?

It will be very helpful if an arm64 image is available. If interested, I will raise a PR.

Delete operation does not exist

Congrutulations on your work.
I need to have the feature to delete consul key. Is it possible for you to add that feature?

Improve documentation to clarify `in`

Currently, get writes the key's value to a file which can be passed to downstream tasks. The documentation should ideally make this more clear.