Altinity / Altinity/clickhouse-operator
Support config substitutions from environment variables
Open
Nobody has claimed this yet.
enhancement
feature
stale
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
<max_query_size from_env="MAX_QUERY_SIZE" />
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
Use the linked ClickHouse config_env.xml as the behavioral reference. First locate the operator code that generates ClickHouse configuration and its existing configuration tests, then determine where the from_env="MAX_QUERY_SIZE" form should be accepted. Done means the substitution works in a managed cluster and is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100