Ask Your Question

Property values constrained by feature -vs- parameter constrained by feature

asked 2016-04-09 07:00:09 -0600

JohnsonEarls gravatar image

Hey all,

Just wondering: Is there a reason I'm not understanding for why a custom type's property values that include a :required_features option will raise a puppet error if the feature is not available, but parameters that include :required_features are silently [except for a debug message] ignored if the feature is not available?

-- Johnson

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2016-04-11 11:27:52 -0600

joshc gravatar image

Puppet properties are things that puppet will manage about a resource. So it will ensure the current value matches the desired (aka should) value specified in the manifest. Puppet parameters are not managed directly, but instead describe metadata about how the resource should be managed, e.g. the source parameter for package resources specifies where to retrieve the package if it's not insync.

Raising an error for property values makes sense, because puppet can't enforce the desired state without the provider feature present, e.g. gem, external executable, etc. Not raising an error for parameter values is somewhat surprising to me, and is probably just a bug.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-04-09 07:00:09 -0600

Seen: 49 times

Last updated: Apr 11 '16