k0sproject / k0sproject/k0sctl
Return an error if environment variables are not set
- Dominant language
- Go
- Stars
- 582
- Forks
- 113
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 34
Description
The docs show a few different options for environment variable manipulation [here](https://github.com/k0sproject/k0sctl#environment-variable-substitution).
It would be great if we had an option where k0sctl would error if it is not set, similar to the bash `${SOME_VARIABLE?error message goes here}`. I'm using k0sctl in a CI pipeline and utilise environment variables heavily.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the environment variable substitution section in the linked k0sctl documentation and trace the implementation behind those options. Determine how an unset variable is currently handled and identify the relevant tests before defining the error behavior. Done means CI use of an unset variable produces an error, with coverage for the new option and its message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100