NASA-IMPACT / NASA-IMPACT/veda-deploy
COORDINATION BLOCKER Required MCP, SMDC, Instances! Update DEPLOYMENT_ROLE_ARN to variables from secret, and create least-permissive OIDC role
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Our DEPLOYMENT_ROLE_ARN is a secret environment variable. We don't need this to be secret, and it would be better if this were a variable so that we could see what stage has which ARN.
Additionally, though it's not easy to confirm because the DEPLOYMENT_ROLE_ARN is a secret, it appears that we are using a very permissive role (admin) and we should create a less permissive OIDC role to use for our deployments.
Acceptance Criteria
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
Review the deployment workflows and composite actions in this repository, then read the linked veda-deploy issues #194 and #195. Trace how DEPLOYMENT_ROLE_ARN is configured and used, and confirm that the variable-based configuration and least-permissive OIDC role satisfy both linked issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions
- Domain
- cloud, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100