Jira (PUP-10579) Request: Add "source" and "content" attributes to the exec resource
Title: Message Title
Jerald Sheets commented on PUP-10579
Re: Request: Add "source" and "content" attributes to the exec resource
I think this would be a good thing, but perhaps baking in the same behavior as other resources, where the "command" attribute would support remote items. So when I would normally use a file resource to place a file in /some/random/path, then execute it with "exec", perhaps baking it into the idiom like so: exec { 'thing': path => '/foo:/bar:/baz', command => 'puppet:///modules/foo/do_the_thing.sh', } might be a better route to that end? Puppet could use vardir or rundir, for example to place the script long enough for execution. Obviously, this could find itself to be onerous without disciplined use of conditionals like "onlyif" or "unless".
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.365066.1594042827000.101494.1594044120029%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Jerald Sheets assigned an issue to Josh Cooper I did the pull based on PUP10026 and am assigning it to you on instruction from Ben Ford. (still learning the process) I do hope I did this right!! Puppet / PUP-10026 skip_tags not documented for puppet agent Change By: Jerald Sheets Assignee: Jerald Sheets Josh Cooper 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325377.1568896957000.128463.1570130280364%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Jerald Sheets commented on PUP-10026 Re: skip_tags not documented for puppet agent I added the documentation for --skip_tags to the agent file puppet/lib/puppet/application/agent.rb as follows: '--skip_tags' is a flag used to filter resources. If this is set, then only resources not tagged with the specified tags will be applied. Values must be comma-separated. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325377.1568896957000.128421.1570129980935%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Jerald Sheets assigned an issue to Jerald Sheets Puppet / PUP-10026 skip_tags not documented for puppet agent Change By: Jerald Sheets Assignee: Jerald Sheets 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325377.1568896957000.128389.1570129260756%40Atlassian.JIRA.
Jira (FACT-1373) Facter with external fact containing a facter call fork-bombs the node
Title: Message Title Jerald Sheets commented on FACT-1373 Re: Facter with external fact containing a facter call fork-bombs the node I sort of crinkled my nose at the designation "esoteric usage". Why would a customer and/or partner NOT utilize facter to obtain a system IP, for instance, instead of trying to accommodate all platforms with some rather ugly awk lines? It is cross-platform, and a custom fact only need be utilized with a single line of code ($foo = `facter ipaddress`) on all platforms. It's the shell/perl equivalent of what we're encouraged to do at the component module level (as generic as possible code). It would seem to me that this should be expected to be a core usage of facter rather than the listed "esoteric" moniker. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (FACT-1373) Facter with custom fact containing a facter call fork-bombs the node
Title: Message Title Jerald Sheets created an issue Facter / FACT-1373 Facter with custom fact containing a facter call fork-bombs the node Issue Type: Bug Affects Versions: FACT 3.1.5, FACT 3.1.4 Assignee: Unassigned Components: Community, PE Created: 2016/03/18 10:51 AM Environment: Standard new install of PE 2015.3.3. RedHat 6.6 and Solaris 10 Labels: customer support facter Priority: Major Reporter: Jerald Sheets If you have an external fact that contains a call to facter, the machine begins to fork-bomb itself and usually control cannot be regained of the system if you cannot quickly get all puppet processes killed. Example fact:
