influxdata / influxdata/influxdb
Influx apply creates duplicate Tasks and Notification Rules.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Create a Task
2. Export template
* `influx export all -f template.yaml`
3. Apply template (previews show the task as being added, not unchanged/replaced)
* `influx apply -f template.yaml`
Seeing the same behavior with Notification Rules.
> I'm happy to work up a PR if we agree this is a bug.
__Expected behavior:__
A single copy of the task exists, and the preview shows unchanged or replaced.
__Actual behavior:__
A duplicate task is created.
__Environment info:__
* System info: Run `uname -srm` and copy the output here
* Linux 5.10.102.1-microsoft-standard-WSL2 x86_64
* InfluxDB version: Run `influxd version` and copy the output here
* InfluxDB v2.6.1 (git: 9dcf880fe0) build_date: 2022-12-29T15:53:07Z
* Influx CLI 2.6.1 (git: 61c5b4d) build_date: 2022-12-29T15:41:09Z
* Other relevant environment details: Container runtime, disk info, etc
* Docker image: influxdb:2.6-alpine
__Config:__
Running using Docker Compose and running the CLI commands by execing into the running container.
Contributor guide
Research direction
Start with the `influx export all -f template.yaml` and `influx apply -f template.yaml` CLI entry points, reproducing the behavior for both Tasks and Notification Rules. Compare the apply preview and resulting resources against the exported template; done means the exported configuration is idempotent, with no duplicate resources and an unchanged or replaced preview.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- cli, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100