Replies: 2 comments
-
Problem: when and which module data should be shown? A module can have many parameters and hiera data. Or: we parse all modules and show all module data. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Related to #299 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Request
Solution
Within HDM -> environments -> node -> Key
Check if the selected key first part of the name is a module name by:
modulepath
setting (usemodules
as default, multiple entries are separated by colon:
, can also be absolute path)Puppet.settings('basemodulepath')
Default:
modulepath
directories in order for a directory with the same namehiera.yaml
inside the directoryhiera.yaml
file existsIf module data exist, a button
module
will show up next to the key.Now HDM switches into module data view.
There should be a button
environment
which leads back to the environment data (ideally the one where we switched to module data view).Within the key list, only module data are shown.
The hiera data directory/file structured is build in the same way as we do it now with environment data.
When selecting a key, one sees the same view as in environment data.
Beta Was this translation helpful? Give feedback.
All reactions