google-github-actions / google-github-actions/auth
Workload identity with Service Account outdated
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Description
TL;DR
I followed all the steps to setup my workload identity for my GH action to authenticate on GCP but it was working. I checked the logs in my IDP but no logs there.
I found out that the attribute-mapping is outdated or wrong. I've used the official documentation here and now my GH actions are able to authenticate. Might be better to just reference your documentation to this official rather than duplicate and have to keep it
Expected behavior
No response
Observed behavior
No response
Action YAML
NA
Log output
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the repository's workload identity documentation and attribute-mapping guidance with the linked official Google Cloud documentation. Update the outdated guidance or replace it with a reference to the official source; done means GitHub Actions users can follow the documented mapping to authenticate successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, google-cloud
- Domain
- authentication, cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100