Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grafana API won't move dashboards to new folder unless the contents have changed #28512

Open
johncornish opened this issue Oct 23, 2020 · 3 comments

Comments

@johncornish
Copy link

What happened:
We edited our provisioning/dashboards.yml file we're using on our Grafana deployment to change what folder the dashboards show up in on the Grafana UI. Upon redeploy / restart, only the dashboards that had their contents changed since the last restart were moved into the new folder, while the remaining 5 stayed stuck in the old one.

What you expected to happen:
Any time you make a change to dashboard provisioning folder location, I would expect it to move all dashboards into the new folder and delete the old one. However, neither is happening.

How to reproduce it (as minimally and precisely as possible):

  1. Create a dashboard JSON file
  2. Create a dashboard provisioning file that puts that JSON into a folder, e.g. "Folder A"
  3. Start / restart Grafana
  4. Edited the provisioning config (e.g. change folder to "Folder B"), but leave the dashboard JSON unchanged
  5. Start / restart Grafana
  6. Go to the UI and notice that both "Folder A" and "Folder B" are present, and that your dashboard should still be stuck in "Folder A"

Anything else we need to know?:
Nah

Environment:

  • Grafana version: v7.1.5
  • Data source type & version: Prometheus
  • OS Grafana is installed on: Ubuntu
  • User OS & Browser: MacOS & Chrome
  • Grafana plugins: Statusmap by Flant JSC
  • Others:
@hugohaggmark
Copy link
Contributor

hugohaggmark commented Oct 26, 2020

Thank you for reporting this @johncornish, I've confirmed this on latest master 9a241a2

@hugohaggmark hugohaggmark added this to Inbox in Backend Platform Backlog via automation Oct 26, 2020
@wbrowne wbrowne moved this from Inbox to Features in Backend Platform Backlog Oct 26, 2020
@marefr marefr removed this from Features in Backend Platform Backlog Oct 28, 2020
Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

@github-actions github-actions bot added the stale Issue with no recent activity label Jan 21, 2024
@samjewell
Copy link
Contributor

not stale

@samjewell samjewell removed the stale Issue with no recent activity label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants