Make environment configurable via workload spec
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
We will have customers with different environment needs, so we should make this configurable for each cluster (or each site?). Ability to enter dev/stage/prod/qa/test/preprod, ect should populate to the cluster/site name and resource names and whatnot.
Eventually for Azure, we should make this part of the standard naming convention, ----<other-descriptor, etc>
Contributor guide
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 tracing how the workload spec is parsed and how cluster, site, and resource names are generated. Clarify whether configuration belongs per cluster or site, define the supported environment values, and establish the Azure naming convention; done means those values consistently affect the relevant names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100