Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title Garrett Guillotte commented on PUP-9033 Re: Confirm and describe type-specific behavior when omitting the ensure attribute Bumping; this would still be useful. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.267532.1533135644000.33377.1599698880020%40Atlassian.JIRA.
Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9033 Confirm and describe type-specific behavior when omitting the ensure attribute Change By: Jorie Tappa Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title Jorie Tappa commented on PUP-9033 Re: Confirm and describe type-specific behavior when omitting the ensure attribute Additional discussion is necessary about whether we should unify the behavior in addition to documenting the state of the world Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-9033
Confirm and describe type-specific behavior when omitting the ensure attribute
Change By:
Garrett Guillotte
In types that use the default {{ensurable}} logic, the "ensure" property works in implied ways when it is not present. This default behavior is described in our [documentation's Type Reference page preamble |https://puppet.com/docs/puppet/latest/type.html] , but users also view individual type reference pages, and the modularization of types and providers means its documentation might be visible in multiple places that do not include the preamble .However, this isn't always clear in the individual types' description of the {{ensure}} attribute. For example, If a user specifies this below entry in their manifest/site.pp, puppet will not CREATE a file. But if the file exists, puppet will MODIFY the file.{code:puppet}file { 'test entry friendly name' : path => '/tmp/testfile', content => 'a whole bunch of testy content.'}{code}But the [file type documentation|https://puppet.com/docs/puppet/5.3/types/file.html#file-attribute-ensure] does not describe the behavior of omitting the attribute.This is further complicated by types that do not use the default {{ensurable}} logic, such as the {{group}} type prior to Puppet 5.4.0 (see PUP-7968).
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-9033 Confirm and describe type-specific behavior when omitting the ensure attribute Change By: Garrett Guillotte Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title
Garrett Guillotte created an issue
Puppet / PUP-9033
Confirm and describe type-specific behavior when omitting the ensure attribute
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/08/01 8:00 AM
Priority:
Normal
Reporter:
Garrett Guillotte
In types that use the default ensurable logic, the "ensure" property works in implied ways when it is not present. This default behavior is described in our documentation's Type Reference page. However, this isn't always clear in the individual types' description of the ensure attribute. For example, If a user specifies this below entry in their manifest/site.pp, puppet will not CREATE a file. But if the file exists, puppet will MODIFY the file.
file { 'test entry friendly name' :
path => '/tmp/testfile',
content => 'a whole bunch of testy content.'
}
But the file type documentation does not describe the behavior of omitting the attribute. This is further complicated by types that do not use
