NASA-IMPACT / NASA-IMPACT/veda-deploy
Re-think static + dynamic configuration for deployments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Right now, we depend on 'mono' secrets for deployments, which contain every value under the sun we might need for a deployment. This is often a blend of 'static' values (Stuff like a VPC ID) and 'dynamic' values (stuff like generated urls/ids).
I think it would be worth us re-looking at all the values our deployments use and consider if our methods of handling them are appropriate.
- This issue needs more fleshing out but putting this in as a placeholder at least.
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
No file, test, or entry point is named. Start by reviewing the deployment workflows and the values currently stored in the mono secrets, then document which values are static or dynamic and how each is handled. The issue does not define a completion criterion, so the desired configuration approach must be agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- cloud, devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100