mayadata-io / mayadata-io/d-operators
proposal: custom resource to apply environment variables
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemSatement: As a DevOps admin I have several applications that depend on environment variables. I would like to expose the available environment variables via a kubernetes custom resource. This would help me implement my tasks in a kubernetes friendly way.
kind: EnvGet
spec:
include:
- <regex>
exclude:
- <regex>
status:
phase:
# will hold environment variable key: value pairs
variables:
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 reviewing the repository's existing Kubernetes controller and custom-resource patterns. Define how the EnvGet resource should expose environment variables, apply its include and exclude regexes, and report phase and variables in status; done requires those behaviors to be specified and implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100