canonical / canonical/knative-operators
improve error messaging if required config options are not defined
Open
enhancement
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 2
Description
For both serving and eventing, if the user does not specify the namespace they will get a nondescript lightkube error that makes it difficult to understand a config option has been missed. Improve this error message, or possibly validate the config values before starting the charm.
Contributor guide
Research direction
Reproduce the missing-namespace case for both serving and eventing, then inspect where charm configuration is handled before startup. Done means users receive a clear message identifying the missing namespace instead of a nondescript lightkube error, or the configuration is validated before startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100