stackabletech / stackabletech/superset-operator
clusterOperations key is under clusterConfig
Open
Nobody has claimed this yet.
release-note/action-required
size/S
type/bug
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 10
Description
This is not the case for other operators, it should be a top level key.
BREAKING CRD change
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 CRD definition and the operator code that reads clusterOperations under clusterConfig. Trace related operator configuration keys for the expected top-level structure, then update the CRD and affected handling so the breaking schema change is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100