Can you share some of your code? This is somewhat complicated to follow,
but probably simpler to view the code.
However, I believe that what you want is to add a parameter to the class
that includes profile_tuned, perhaps called $is_oracle. If the parameter is
false, include profile_tuned, if true
Many thanks for your reply Gavin. I have basically gone down this route in
my thinking too, except rather than use a fact, I will set up our ENC (a
custom ENC we've written) to set a global variable 'role' which can then be
used to drive the hiera hierarchy.
A fact would mean we would have to
David
If you can expose the role as a top-level fact, then you can use that to drive
the hiera hierarchy. You can then override the required class params in a role
specific yaml file.
HTH
Gav
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gro
Hello,
Assume an open source Puppet deployment using the roles and profiles
paradigm and Heira
(https://puppet.com/presentations/designing-puppet-rolesprofiles-pattern)
Lets say I have a role module called 'role_applicationX' which includes two
profile modules - "profile_oracle_server" and "pr
