Jira (PUP-3630) Odd behavior with noop
Title: Message Title
Charlie Sharpsteen commented on PUP-3630
Re: Odd behavior with noop
A minimum re-production case for this behavior consists of a defined type and a class which declares a noop resource of that time type:
# atype.pp
define noop_test::atype(
$content_string = 'some content',
) {
file{/tmp/$title:
ensure = file,
content = $content_string,
}
}
Jira (PUP-3630) Odd behavior with noop
Title: Message Title Jay Wallace created an issue Puppet / PUP-3630 Odd behavior with noop Issue Type: Bug Assignee: Unassigned Created: 2014/11/06 12:48 PM Labels: support Priority: Normal Reporter: Jay Wallace This behavior is really quirky. It seems if a defined type is restructured to include the noop parameter, you get the expected behavior described initially in the ticket (ie a noop overwrite). Without restructuring the defined type, noop = false will not take precedence over what is set in let's say site.pp. This could be due to an issue with the way noop is being inherited by the resources with the defined type. I am using inherited pretty loosely here, as this isn't actually the way this works. Further investigation needed, please feel free to either escalate or open a bug with my last update. Add Comment
Jira (PUP-3630) Odd behavior with noop
Title: Message Title Lee Lowder updated an issue Puppet / PUP-3630 Odd behavior with noop Change By: Lee Lowder Thisbehaviorisreallyquirky.Itseemsifadefinedtypeisrestructuredtoincludethenoopparameter,yougettheexpectedbehaviordescribedinitiallyintheticket(ieanoopoverwrite).Withoutrestructuringthedefinedtype,noop=falsewillnottakeprecedenceoverwhatissetinlet'ssaysite.pp.Thiscouldbeduetoanissuewiththewaynoopisbeinginheritedbytheresourceswiththedefinedtype.Iamusinginheritedprettylooselyhere,asthisisn'tactuallythewaythisworks. Furtherinvestigationneeded,pleasefeelfreetoeitherescalateoropenabugwithmylastupdate. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
