-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] The Vault action fails if the secret key contains a dot #504
Comments
Hi @AlexandarNaydenov ! I am sorry you are having trouble. Can you try to use single quotes around the key?
I believe that should allow proper handling of the dot character. |
I am dealing with a similar issue but with a space character instead of a dot.
Should this work, or are spaces not allowed in the name of the secret token? |
Hi @mourtallah, @fairclothjm, |
According to the JSONata docs, the correct character for quoting is the backtick Have you tried:
and
? |
This works for me by enclosing the key within square brackets.
|
Closing since @andyspiers's link to the JSONata docs seems to resolve the issue. https://docs.jsonata.org/simple
Please reopen an issue if you are still encountering trouble. |
Vault server version
Vault 1.14.3 enterprise
vault-action version
v2.7.4
Describe the bug
The Vault Action fails if the secret key contains a dot.
Example:
secret.token
To Reproduce
The yaml of the
vault-action
step:The first example with secret key
secret_token
works without problem, but ok the second one fails with an error log:Screenshot of the Vault UI:
Expected behavior
To work with both secret keys.
The text was updated successfully, but these errors were encountered: