Altinity / Altinity/clickhouse-operator
dry run?
Open
Nobody has claimed this yet.
stale
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Is it possible to view a list of changes CHOP will make before actually making the changes? sort of like dry run. I want to make changes to CRD yaml files and preview the change.
ps- is there a slack workspace for asking such questions?
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
No files, tests, or entry points are named; first map the CRD-change workflow and agree on the preview scope. Done should be defined as a reliable way to inspect planned changes without applying them.
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
- Needs clarification
- Newbie friendliness
- 25/100