Hi community, I need a suggestion.
Some of my modules like nagios or nfs shares are having a lot of static
data which needs to be defined in the bottom of hierarchy.
It makes my file generic.yaml quite massive and not that readable.
What are the options do I have to separate this into more structured tree?
What are the best practices?
The first thing comes to mind is to add few more files in to hiera:
...
- %{::site}
- generic
- nagios_services
- nfs_shares
etc..
Or is it better to avoid this?
Any thoughts?
--
Andrey
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CACzr%3DFfQtU9Q5rjQT72Qur%2BzTqEcOHbG1x%2Bt5EnL7Bj1Hbv6Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
