Skip to content

Use OIDC from GitHub settings instead of action #2

@froggleston

Description

@froggleston

Currently we use two org/repo level secrets to manage access to AWS Secrets Manager for the equivalent of the SANDPAPER_WORKFLOW token.

A new formal OIDC support beta feature has been rolled out in public preview which would allow us to use proper short-lived tokens per workflow instead of manually regenerated PATs per month. This may be useful for repo-scoped properties to control behaviour, instead of the current access levels per singular carpentries-bot PAT.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions