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.

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

GitHub Actions Secrets are Uppercased #863

Open
jamesward opened this issue Oct 29, 2024 · 2 comments
Open

GitHub Actions Secrets are Uppercased #863

jamesward opened this issue Oct 29, 2024 · 2 comments

Comments

@jamesward
Copy link

GitHub Actions uppercases secret keys. This makes it a bit awkward to set keys like:

ORG_GRADLE_PROJECT_mavenCentralUsername

Can the internal logic for all env vars support uppercase variants as well? Also it'd be nice if all uppercase was the default.

@kibotu
Copy link

kibotu commented Dec 17, 2024

true, I kind of have to map them in the workflow due to this, e.g.
https://github.com/kibotu/AndroidResourceExtensions/blob/master/.github/workflows/android.yml#L32-L37

    env:
      ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.MAVEN_CENTRAL_USER_NAME }}
      ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}
      ORG_GRADLE_PROJECT_signingInMemoryKey: ${{ secrets.SIGNING_IN_MEMORY_KEY }}
      ORG_GRADLE_PROJECT_signingInMemoryKeyId: ${{ secrets.SIGNING_IN_MEMORY_KEY_ID }}
      ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.SIGNING_IN_MEMORY_KEY_PASSWORD }}

not sure if there is an easier way to handle this

@christian-draeger
Copy link

am running into the same issue. thx @kibotu for the workaround.
i would really like to see uppercase env var support as well to get rid of the env var mapping in github actions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants