influxdata / influxdata/influxdb
Experience when importing multiple pkgs that have conflicting resources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
This is more a request for input on how this will work. Image the following scenario where I want to apply multiple pkgs together:
pkg1
|- dashboard_1
pkg2
|- dashboard_1
The following could happen (not limited to these):
- both dashboards are all the same
- this should be safe, just take the 1 of each, no user action needed
- dashboard_1 and dashboard_2 are not the same
- user may want to make it a single dashboard composed together (user action required)
- consolidating dashboards would be akin to taking all cells from both dashboards and making a single dashboard out of it (removing any duplicate cells)
- user may not want this
- either fail, or ask user to rename one of the conflicting resources
- user may want to make it a single dashboard composed together (user action required)
There are a bunch of different resources, but this is the one with the highest likelihood of converging into one. I'd like to know what direction we want to take these 🤔.
Off the top of my head, I see the ability for users to pick what they want to do with conflicts as a good default option, then having a means to indicate when any confilcts arise to either fail or consolidate (best attempt at least).

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.
Assessment
This issue has not been assessed yet.