Skip to content

Reproduce issue related to consuming secrets that are created using createOrUpdateRepoSecret

Notifications You must be signed in to change notification settings

lakshmajee/issue-gh-actions-rest-secets

Repository files navigation

Notes

  • add AWS_SECRET_ACCESS_KEY in github secrets
  • create personal access token with repo write scope and store it in TEST_WRITE_TOKEN
  • run create-secret.yml workflow, which will store DUMMY_AWS_IAM_ROLE_ASSUME in gh secrets
  • add SAME_SECRET_MANUALLY_ADDED in gh secrets with same value (same aws role)
  • now run test secrets acceissibility by running
    • test_secrets_access.yml (secrets managed from other workflow)
    • test_secrets_manual_access.yml (manually managed secrets )

After running create-secret.yml (Bootstrap) workflow, the GH seccrets UI looks like below

image

The workflow created a secret named `DUMMY_AWS_IAM_ROLE_ASSUME`

About

Reproduce issue related to consuming secrets that are created using createOrUpdateRepoSecret

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published