Paul Ingles

The validation fails with more information- would be good to include that in the error message too.

Hi, We did think about putting passwords into either configuration on the blueshift instance or in environment variables. In the end we decided against it given all our data on...

interesting! how about using `{:redshift-connection :some-identifier ...` inside the manifest, then inside config.edn: ``` clj {:redshift-connections {:some-identifier {:jdbc-url "" ...}} ``` Blueshift can then use the specified connection or one...

To be honest, this would probably also make it a little easier to cleanup some of the repetition in manifests. I'd definitely welcome a pull request if I/we don't get...

Awesome- thanks for all your hard work! We're going to try and get some time today/tomorrow to take a look and get it merged. We'll keep you posted :)

@nduijvelshoff could you give us the errors you're getting/build output and we'll see if we can debug the problem

Wow, super strange. I've take a clean clone on a new laptop and can build with: ``` $ go get -v -t ./... $ CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o...

Agreed- it's nice to offer the more general access to secrets rather than exclusively database credentials. My only comment/concern is that `api.Secret` has a different interface to `vault.Credentials` (the struct...

But yeah, tests to prove behaviour would be good to add @Joseph-Irving 😄

Hi @aaron-trout, this came up in another project of ours (https://github.com/uswitch/kiam/pull/159) recently. I know having to mount the host certs it makes it slightly more onerous to cluster operators to...