influxdata / influxdata/helm-charts
Yaml integers converted to floats, not recognized as Go integer.
- Dominant language
- Mustache
- Stars
- 257
- Forks
- 347
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 9
Description
Using influxdata/influxdb 4.12.5
If you pass large integer values eg:
```
config:
data:
max-values-per-tag: 10000000
```
yaml converts that to `1e7` in the toml file, which then influx chokes on parsing because it expects an integer.
If you put the helm value in quotes to keep it, the quotes get preserved into the toml as well as `"10000000"`, and influx can still not parse that value.
Contributor guide
Research direction
Reproduce the issue by rendering the Helm chart with the shown max-values-per-tag value, then inspect the generated TOML and the chart templates that handle this configuration. Compare unquoted and quoted values; done means the rendered TOML preserves the value as an integer that InfluxDB accepts without retaining quotes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, yaml
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100