You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Foreman scenarios (foreman_proxy and lcm) depended heavily on sane defaults stored in answer files. Now the answer files are empty, so the default values are missing. Add sane defaults which can be used reasonably in any environment.
A related problem is defaults for Vagrant, which can be considered a special environment with additional sane defaults. My proposed solution is this:
Add generic, sane defaults to foreman_proxy.pp and lcm.pp
Create an answer file suitable for the Vagrant environment
Store and version the answer file
Ensure that the default (almost empty) answer file is overwritten during Vagrant provisioning with the answer file tailored for Vagrant
This way Vagrant-specifisms don't accidentally end up in production environments.
The text was updated successfully, but these errors were encountered:
Foreman was lacking default parameters, resulting to undefs and failing.
This commit adds default parameters to the class.
URL: Puppet-Finland#31
Signed-off-by: Petri Lammi <[email protected]>
The Foreman scenarios (foreman_proxy and lcm) depended heavily on sane defaults stored in answer files. Now the answer files are empty, so the default values are missing. Add sane defaults which can be used reasonably in any environment.
A related problem is defaults for Vagrant, which can be considered a special environment with additional sane defaults. My proposed solution is this:
This way Vagrant-specifisms don't accidentally end up in production environments.
The text was updated successfully, but these errors were encountered: