influxdata / influxdata/influxdb
issue with influx apply with stackid for checks with error err_msg="failed to update checks"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
1. Export the resources from one influxdb instance(say X) using command >>influx export all(having dashboard, checks) to yaml file
2. Create a stack id on other instance of influxdb (Say Y)
3. Apply the exported yaml file using stackid >> Influx apply -stack-id <> -f <>
3. Resources got created in Y influxdb instance
4. Again export the resources from first influxdb instance( X) using command >>influx export all(having dashboard, checks) to yaml file
5. Apply the exported yaml file using already created stackid >> Influx apply -stack-id <> -f <>
__Expected behavior:__
**it should update all the resources**
as per the Documentation
When applying a template to an existing stack, InfluxDB checks to see if the resources in the template match existing resources. InfluxDB updates, adds, and removes resources to resolve differences between the current state of the stack and the newly applied template.
Apply a template associated with a stack.
Stacks make template application idempotent.
__Actual behavior:__
**It is not updating for Checks syaing error
metadata_name="metadataname" err_msg="failed to update checks[\"checkid-16digit\"]: task not found"**
Environment info:
InfluxDB Cloud 2.0
CLI tools version: Influx CLI 2.0.2
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
Start with the Influx CLI `export` and `apply -stack-id` entry points, focusing on the checks update path described in the reproduction. Reproduce the two-instance workflow with an exported YAML file; done means applying the same stack template updates checks without the `task not found` error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100