Issue #6643 has been reported by Nigel Kersten.
----------------------------------------
Feature #6643: Make ensure mandatory.
https://projects.puppetlabs.com/issues/6643
Author: Nigel Kersten
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version: Telly
Affected Puppet version:
Keywords:
Branch:
(Proposal)
Take the following two cases:
<pre>
file { "/tmp/foo": }
</pre>
<pre>
file { "/tmp/foo":
content => foo",
}
</pre>
The first case doesn't create the file, the second does, even though the ensure
state hasn't been specified in either.
We've pushed this complexity down into the providers themselves, where they
need to handle all the various permutations of non-ensure properties, and
decide whether or not to set ensure.
I believe this is error-prone, and will end up varying significantly across
types and providers, resulting in confused users.
I'm proposing that we make ensure mandatory, and if you set any properties
other than "audit" on a resource when you haven't specified ensure, we either:
* error at a higher level
* provide a standard way of marking properties as providing an implicit
ensure value
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
