Provisioning the folder structure from filesystem to Grafana

[DamGameHero]

Hello !

What do you think about using the provisioning the folder structure from filesystem to Grafana via a grr export ?

Currently with grr export in last release (v 0.1.0), dashboards are created in:

my-provisioning-dir/Dashboard/dashboard.json

Dashboard folder is a value that can't be changed. Line here, I guess:

grizzly/pkg/grizzly/workflow.go

Line 387 in b719359

dir := fmt.Sprintf("%s/%s", exportDir, resource.Kind())

However, to take advantage of the folder structure, it would be preferable to build the path like this:

my-provisioning-dir/grafanaDashboardFolder/dashboard.json

With grafanaDashboardFolder given like in the mydash.libsonnet example or in another way .

I had done this feature, but it was on the previous version. This has evolved since and I would like to know your opinion on this point.

➡️ malcolmholmes answered here: #103 (reply in thread)

[DamGameHero]

Finally, I will not use the foldersFromFilesStructure option because according to the documentation:

Note: folder and folderUid options should be empty or missing to make foldersFromFilesStructure work.

source

So the folder UIDs are automatically generated (we can't set them) what breaks coherence between the Grafana instances.
To choose the folder's UID, I could create the folders via the API before a grr export but I was no longer really in a provisioning logic. So I abandoned this option.