Change to the yaml only dashboard configuration key - filename #1955
Unanswered
WallyDW
asked this question in
Core functionality
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe your core improvement
When setting up yaml only dashboards the lines in the configuration.yaml require you to use a filename to import your tabs.
The filename is actually just an enforced !include, but the file that the filename refers to will include all the tabs for your views, which will most likely quickly be rather big, so you will need to split it up with includes of some version.
This means the file will often just contain the key views: and then a number of include keys. If onf of the include_dir variants is used, then it might just be a single line.
I suggest the filename key under the dashboards: key in the configuration.yaml be changed to views: and let it be a normal key that can just use include like other options.
Current limitations
The filename does not really follow the standard of being able to use includes and it splits the configuration in a non-intuitive way.
Technical benefits
The change will make the configuration in line with the rest of the standard and it will allow the user more flexibility and possibly also remove some extra files that contain no real information.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions