source-cooperative / source-cooperative/docs.source.coop
Document unattended credential acquisition
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 2
- Avg merge
- 25m
- Merged PRs (30d)
- 2
Description
Alongside.
Do
One page per environment covering how to get credentials, how they refresh, how long they last, and what failure looks like when refresh is skipped.
Environments to cover:
- GitHub Actions (ambient OIDC, no stored secret)
- Anything else, via an API key
Watch
State plainly that aws-actions/configure-aws-credentials does not currently work against /.sts, and show the SDK web-identity provider setup instead.
Part of source-cooperative/source.coop#491.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the existing documentation structure and navigation for credential guidance. Add one page for GitHub Actions and one for API-key environments, covering acquisition, refresh, lifetime, and skipped-refresh failures; document the SDK web-identity setup and the configure-aws-credentials limitation against /.sts. Verify that both environment paths are linked and complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100