-
Notifications
You must be signed in to change notification settings - Fork 140
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] - Vault action fails if the key does not contain a dot #505
Comments
Thanks for reporting this. If you are still having this issue, can you possibly provide more context such as the output of the KV secret read? That will help us investigate what may have occurred. |
I am still having this issue.
if I change ecsAppId to ecs.AppId , its able to fetch it. So that means ecsAppId is treated as single word and vault action failed to retrieve if key contains only single word. |
@Basil-V-Jose Hello, can you please provide the output from the kv commands:
We need more information about your configuration to debug further. I am unable to reproduce the issue. I tried the following with v2.5.0, v2.7.4 and v3:
Here is my kv output from Vault:
|
Please find my kv output from Vault:
Vault server version : v1.17.5 |
@Basil-V-Jose Thanks for that. Can you try removing the single quotes for the keys that don't contain dot characters? -mountpoint/data/TEST 'ecsAppId' | ecsAppId;
+mountpoint/data/TEST ecsAppId | ecsAppId; |
@fairclothjm , I removed the single quotes for the keys that don't contain dot characters and its able to fetch the secrets now. |
@Basil-V-Jose Glad to hear the issue is resolved! :) |
Vault server version
v1.14.1
vault-action version
v2.7.4
Describe the bug
I'm unable to retrieve secrets where key does not contains a dot via this action
To Reproduce
Expected behavior
I expect the secret to be retrieved and put in env as needed. If I modify the key in vault to username.workaround, and edit the above yaml, action fetches the secret.
Log Output
Error: Unable to retrieve result for data.data."'username'". No match data was found. Double check your Key or Selector.
The text was updated successfully, but these errors were encountered: