Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG] Key transformed to uppercase when exported to env var using wildcard #536

Open
martinsolberg opened this issue Mar 20, 2024 · 1 comment · May be fixed by #537 or #545
Open

[BUG] Key transformed to uppercase when exported to env var using wildcard #536

martinsolberg opened this issue Mar 20, 2024 · 1 comment · May be fixed by #537 or #545
Labels
bug Something isn't working

Comments

@martinsolberg
Copy link

Vault server version

v1.15.5

vault-action version

v3

Describe the bug

When getting multiple keys in a path using wildcard, the resulting environment variables have their case transformed to uppercase.

To Reproduce

with:
    secrets: |
        secret/data/ci/aws * | MYAPP_ ;

The key accessKey will be created as MYAPP_ACCESSKEY.

Expected behavior

The exported environment variable should retain the key case, e.g. MYAPP_accessKey.
@martinsolberg martinsolberg added the bug Something isn't working label Mar 20, 2024
@martinsolberg martinsolberg changed the title Key transformed to uppercase when exported to env var using wildcard [BUG] Key transformed to uppercase when exported to env var using wildcard Mar 20, 2024
@martinsolberg
Copy link
Author

vault-action/src/utils.js

Lines 11 to 13 in 77efb36

if (isEnvVar) {
outputKey = outputKey.toUpperCase();
}

Why?

@martinsolberg martinsolberg linked a pull request Mar 20, 2024 that will close this issue
Open
1 task
@bagf bagf linked a pull request Apr 26, 2024 that will close this issue
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@martinsolberg