Hi,
I just upgraded to 1.7.2 today from 1.6 after seeing this issue around wanting to use puppet default parameter values.
Is there a way to have this new puppet default value checkbox automatically checked under a few conditions.
a. when there is a default value via puppet
b. when someone clicks the override button.
Additionally, Is there a setting to control this behavior since it may not be desirable for everyone?
Corey
Hi Corey,
Currently use puppet default can't be automatically checked.
When puppet default is a simple value (like a boolean) you don't need it
on the parameter itself since the value will be sent correctly,
this was added in case the default uses a variable and you don't want to
send the string "$(…" but you want the actual value to be filled in.
You can also decide that only if a certain matcher applies to your host you
would go back to using puppet default.
I'm not sure I understand when you want it to be used automatically,
when someone clicks override you want to check the default and disregard
their changes?
When do you use the puppet default today? do all of your class parameters
use variables? would you like to prevent the option to override the value
when there is a default?
Hi,
I just upgraded to 1.7.2 today from 1.6 after seeing this issue around
wanting to use puppet default parameter values.Is there a way to have this new puppet default value checkbox
automatically checked under a few conditions.a. when there is a default value via puppet
b. when someone clicks the override button.Additionally, Is there a setting to control this behavior since it may
not be desirable for everyone?Corey
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
I usually always try to code default values for puppet parameters but if I
don't sometimes they are in hiera. Occasional, we will want to override
various default values form some host groups while other host groups work
just fine with the default puppet parameter values. And this is why the
use puppet value was created because if you don't override in all the host
groups then you get the $($…) output which I assume does not actually
resolve to a variable in the puppet code. Please correct me if I am wrong,
because I don't actually know.
Since I feel its safer to always have the use puppet default value checked
(at the puppet class level) its rather annoying to check not only the
override checkbox but now also the use puppet default value checkbox. This
is a pattern I do not wish to repeat. I just think if there was a setting
to control the default behavior for this additional checkbox it might save
me about 1000 mouse clicks.
Many of my hostgroups have the same classes and while some use the default
puppet values others do not and require someone with knowledge of the
puppet class to determine what the values of the parameters should be. So
If I can have users feel safer about inputing data or leaving the values
alone it would be much easier to control.
Corey