Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Vault field syntax not working as documented #1517
Concourse version: 3.4.0
In the docs, in section Credential Management > Using Vault > Credential Lookup Rules it says:
I can't get this to work.
I add this to vault:
This pipeline works as expected:
When running, say-hello writes
However, if I add two more params, using the field syntax it fails
This time, say-hello fails with:
Thanks. So to clarify for anyone reading this in the future.
Would it be possible to defer always using
@jtarchie : I have a little
Let’s imagine this usecase:
We need to store a Vault
If this grows, there will be a big amount of objects with only one
to avoid a huge mess.
Is this something which you (as concourse team) is considering to support?
I’d very much welcome that.
@janaurka, you can do the later.
And then reference them using
Vault has this weird concept of paths that have key-value pairs, when it really feels like keys with key-value pairs.
@HCanber, this does seem like a bug. We will see if we can support both.
Probably related to this: nested paths don't seem to work either:
using it as
putting it inside of the pipeline name (e.g.
Beep boop! This issue has been idle for long enough that it's time to check
If it is, what is blocking it? Would anyone be interested in submitting a
If no activity is observed within the next week, this issue will be