influxdata / influxdata/influxdata-docker
Retention Policy as a environment variable for influxdb
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
I would like to know if we can add a env variable as DURATION, REPLICA and SHARD_GRP_DURATION for the retention policy. I am currently using K8s with plain influxdb image and grafana. Its not simple to provide the retention policy as of now.
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
No file or test is named in the issue. Start by inspecting the Docker image's existing environment-variable handling and retention-policy entry point; confirm how DURATION, REPLICA, and SHARD_GRP_DURATION are passed from a Kubernetes deployment. Done means those variables configure the InfluxDB retention policy without manual setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100