NASA-IMPACT / NASA-IMPACT/veda-deploy
Idea: Modify dispatch to pre-fill environment jobs if DEPLOY variables are configured
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What
The dropdown to select which jobs/components to deploy in a dispatch is helpful but doesn't make it easy to see which components a particular environment already has or should have.
Perhaps we can improve this by using the DEPLOY_ variables if set in the environment to pre-populate the selection for the dispatch. The operator could override these but this would give us some continuity between deployments.
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 workflow that implements dispatch and the environment DEPLOY_ variables. Trace how the current job or component selection is populated; done means configured environment values pre-fill the dispatch while operators can override them, with the relevant workflow checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100