Jira (PUP-1410) Empty resource collectors can break long relationship chains
Title: Message Title
Nick Lewis updated an issue
Puppet / PUP-1410
Empty resource collectors can break long relationship chains
Change By:
Nick Lewis
Hi,When using chained resources, with a collection within the string, if the collection is empty, the chain is broken and the resources either side do not depend on each other.Example:test/manifests/init.pp{{code}}class test { $cr = ["1", "2"]exec{"pre":command => "/bin/true" }exec{"post":command => "/bin/true" }test::test{$cr: }Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]}{{code} } test/manifests/test.pp{{code}}define test::test{ exec{"echo $name":command => "/bin/echo $name",tag => "inter" }}{{code}}Run as is:!non_empty_collection.jpg!If we comment out:{{code}}test::test{$cr: }{{code}}So it is empty, we get "empty_collection.jpg", this:!empty_collection.jpg!To get the desired result and what I would have expected as the default, I have to manually add another relationship between "pre" and "post" to cater for the empty collection.{{code}}Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]Exec["pre"] -> Exec["post"]{{code}}Resulting in:!workaround.jpg!Is this the intended behaviour? I would expect the workaround relationship to be implicit (Pre -> a collection that happens to be empty -> post), as I do not know how many tags of "inter" will be created (in my real use, this is pulled from hiera)Thanks,Martin
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Group
Jira (PUP-1410) Empty resource collectors can break long relationship chains
Title: Message Title
Nick Lewis updated an issue
Puppet / PUP-1410
Empty resource collectors can break long relationship chains
Change By:
Nick Lewis
Hi,When using chained resources, with a collection within the string, if the collection is empty, the chain is broken and the resources either side do not depend on each other.Example:test/manifests/init.pp {{code}} class test { $cr = ["1", "2"]exec{"pre":command => "/bin/true" }exec{"post":command => "/bin/true" }test::test{$cr: }Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]} {{code} test/manifests/test.pp {{code}} define test::test{ exec{"echo $name":command => "/bin/echo $name",tag => "inter" }} {{code}} Run as is:!non_empty_collection.jpg!If we comment out: {{code}} test::test{$cr: } {{code}} So it is empty, we get "empty_collection.jpg", this:!empty_collection.jpg!To get the desired result and what I would have expected as the default, I have to manually add another relationship between "pre" and "post" to cater for the empty collection. {{code}} Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]Exec["pre"] -> Exec["post"] {{code}} Resulting in:!workaround.jpg!Is this the intended behaviour? I would expect the workaround relationship to be implicit (Pre -> a collection that happens to be empty -> post), as I do not know how many tags of "inter" will be created (in my real use, this is pulled from hiera)Thanks,Martin
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed
Jira (PUP-1410) Empty resource collectors can break long relationship chains
Title: Message Title
Nick Lewis updated an issue
Puppet / PUP-1410
Empty resource collectors can break long relationship chains
Change By:
Nick Lewis
Hi,When using chained resources, with a collection within the string, if the collection is empty, the chain is broken and the resources either side do not depend on each other.Example:test/manifests/init.pp{{ code monospaced }}class test { $cr = ["1", "2"]exec{"pre":command => "/bin/true" }exec{"post":command => "/bin/true" }test::test{$cr: }Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]}{{ code monospaced }}test/manifests/test.pp{{ code monospaced }}define test::test{ exec{"echo $name":command => "/bin/echo $name",tag => "inter" }}{{ code monospaced }}Run as is:!non_empty_collection.jpg!If we comment out:{{ code monospaced }}test::test{$cr: }{{ code monospaced }}So it is empty, we get "empty_collection.jpg", this:!empty_collection.jpg!To get the desired result and what I would have expected as the default, I have to manually add another relationship between "pre" and "post" to cater for the empty collection.{{ code monospaced }}Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]Exec["pre"] -> Exec["post"]{{ code monospaced }}Resulting in:!workaround.jpg!Is this the intended behaviour? I would expect the workaround relationship to be implicit (Pre -> a collection that happens to be empty -> post), as I do not know how many tags of "inter" will be created (in my real use, this is pulled from hiera)Thanks,Martin
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1410) Empty resource collectors can break long relationship chains
Title: Message Title
Nick Lewis updated an issue
Puppet / PUP-1410
Empty resource collectors can break long relationship chains
Change By:
Nick Lewis
Hi,When using chained resources, with a collection within the string, if the collection is empty, the chain is broken and the resources either side do not depend on each other.Example:test/manifests/init.pp {{monospaced}} class test { $cr = ["1", "2"]exec{"pre":command => "/bin/true" }exec{"post":command => "/bin/true" }test::test{$cr: }Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]} {{monospaced}} test/manifests/test.pp {{monospaced}} define test::test{ exec{"echo $name":command => "/bin/echo $name",tag => "inter" }} {{monospaced}} Run as is:!non_empty_collection.jpg!If we comment out: {{monospaced}} test::test{$cr: } {{monospaced}} So it is empty, we get "empty_collection.jpg", this:!empty_collection.jpg!To get the desired result and what I would have expected as the default, I have to manually add another relationship between "pre" and "post" to cater for the empty collection. {{monospaced}} Exec["pre"] -> Exec<| tag == 'inter' |> -> Exec["post"]Exec["pre"] -> Exec["post"] {{monospaced}} Resulting in:!workaround.jpg!Is this the intended behaviour? I would expect the workaround relationship to be implicit (Pre -> a collection that happens to be empty -> post), as I do not know how many tags of "inter" will be created (in my real use, this is pulled from hiera)Thanks,Martin
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You receiv
Jira (PUP-1410) Empty resource collectors can break long relationship chains
Title: Message Title
Nick Lewis commented on an issue
Re: Empty resource collectors can break long relationship chains
This syntax doesn't seem to actually create transitive dependencies, even if the middle bit does exist. It's effectively interpreted as:
Exec[pre] -> Exec<| tag == 'inter' |> Exec<| tag == 'inter' |> -> Exec[post]
In that case, it makes some sense that there wouldn't be a relationship between Exec[pre] and Exec[post].
However, as we've already fixed a similar issue regarding empty classes, this behavior is surprising at best.
Add Comment
Puppet / PUP-1410
Empty resource collectors can break long relationship chains
Hi, When using chained resources, with a collection within the string, if the collection is empty, the chain is broken and the resources either side do not depend on each other. Example: test/manifests/init.pp class test { $cr = ["1", "2"] exec{"pre": command => "/bin/true" } exec{"post": ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1056) puppet master should not trap SIGINT
Title: Message Title Nick Lewis assigned an issue to Patrick Hemmer Puppet / PUP-1056 puppet master should not trap SIGINT Change By: Nick Lewis Assignee: Patrick Hemmer Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1056) puppet master should not trap SIGINT
Title: Message Title Nick Lewis commented on an issue Re: puppet master should not trap SIGINT This seems likely, but I can't actually reproduce it. Can you please provide some more information about how to reproduce this, including your environment (config.ru, version of puppet + unicorn)? Add Comment Puppet / PUP-1056 puppet master should not trap SIGINT Puppet master currently traps SIGINT. This causes problems with rack servers, especially unicorn. Unicorn has it's own SIGINT trap and will shut down the worker processes when it receives it. However because puppet master is trapping SIGINT, unicorn doesn't get the signal, the worker processes are abandoned, and then die once they hit a timeout they ha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.g
Jira (PUP-1184) "puppet agent --genconfig" also create settings for puppet master
Title: Message Title Nick Lewis commented on an issue Re: "puppet agent --genconfig" also create settings for puppet master This is tricky because the config settings are somewhat ad hoc. Puppet doesn't actually know which settings correspond to which sections/applications. But this behavior is definitely wrong, in any case. Add Comment Puppet / PUP-1184 "puppet agent --genconfig" also create settings for puppet master When I run "puppet agent --genconfig > /tmp/puppet.conf", I did get the template for puppet. I not familiar what settings got generated are really needed. Can you confirm settings in puppet.conf are validd for puppet agent ? To me following two settings obviously below to puppet master not puppet agent. cert_inventory = /etc/opt/puppetclient268... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.c
Jira (PUP-1042) Puppet apply runmode should write classes.txt file
Title: Message Title Nick Lewis assigned an issue to Eric Sorenson It looks like there's a way to do this but it needs a decision of whether or not to turn it on by default. Puppet / PUP-1042 Puppet apply runmode should write classes.txt file Change By: Nick Lewis Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Nick Lewis commented on an issue Re: sshkey creates /etc/ssh/ssh_known_hosts with mode 600 This appears to be happening because we write the file using a Tempfile instance and then copy it into place. The default mode for Tempfile is 600. We should probably use Puppet::Util.replace_file, which allows setting the mode and has a saner default of 644. Plus it's generally a bit more robust/secure/standard. Add Comment Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Using the sshkey type /etc/ssh/ssh_known_hosts is created with mode 600 by default. This seems undesirable in most situations. I think the default should be 644. I didn't see anything obvious in the sshkey code that set it strictly on purpose. Does puppet default to 600 somewhere? And is there a simple way to tweak a type to use a different mode? Th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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, s
Jira (PUP-1240) err: Failed to apply catalog: Parameter repeat failed: Repeat must be 1 unless periodmatch is 'distance', not 'number'
Title: Message Title
Nick Lewis commented on an issue
Re: err: Failed to apply catalog: Parameter repeat failed: Repeat must be 1 unless periodmatch is 'distance', not 'number'
I can reproduce. It looks like the bug here is that when validate is called, the repeat property hasn't yet been munged to a number, so the comparison of repeat != 1 is always true.
Add Comment
Puppet / PUP-1240
err: Failed to apply catalog: Parameter repeat failed: Repeat must be 1 unless periodmatch is 'distance', not 'number'
schedule { 'fails': range => '17 - 20', period => daily, periodmatch => number, repeat => 1, } Produces this error: err: Failed to apply catalog: Parameter repeat failed: Re...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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.goog
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title
Nick Lewis commented on an issue
Re: Class names that match the node name are not evaluated
Appears to still be a problem as of 3.4.
Add Comment
Puppet / PUP-1357
Class names that match the node name are not evaluated
If I setup: class subversion { warning("I am class subversion") } and in my nodes.pp I have node subversion { include subversion } When i run puppet in verbose mode on subversion, I never see that warning.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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/groups/opt_out.
Jira (PUP-1357) Class names that match the node name are not evaluated
Title: Message Title
Nick Lewis commented on an issue
Re: Class names that match the node name are not evaluated
The issue here appears to be that node scopes are stored in the same place as class scopes, and they're stored by name. The existence of a class scope for a given class is used to determine whether or not a class has been evaluated. So the class is looked up, and then its scope is checked; since it exists, the class is assumed to already have been evaluated and we carry on. Oops.
Add Comment
Puppet / PUP-1357
Class names that match the node name are not evaluated
If I setup: class subversion { warning("I am class subversion") } and in my nodes.pp I have node subversion { include subversion } When i run puppet in verbose mode on subversion, I never see that warning.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1367) behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes
Title: Message Title
Nick Lewis commented on an issue
Re: behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes
As the redmine ticket was accepted, I'm marking this ready for engineering to correspond.
Add Comment
Puppet / PUP-1367
behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes
In 2.6.1 the following recipe: class a( $b_c = { 'b' => 'foo' } ) { notice $a::b_c if $a::b_c { notice $a::b_c['b'] } } class b { class{'a': b_c => false } } class b::c inherits b { Class['a']{ b_c => { 'b' => 'bleh' } } } class b::d { include ::b::c } include b::d produces the following outp...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 option
Jira (PUP-1032) The function API has "interesting" type conversions
Title: Message Title Nick Lewis assigned an issue to Eric Sorenson It looks like this still needs a decision about whether or not to explicitly do the coercions that the documentation incorrectly states always happen, or the update the documentation not to state that. Puppet / PUP-1032 The function API has "interesting" type conversions Change By: Nick Lewis Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1135) Undeprecate 'puppet kick' run mode
Title: Message Title Nick Lewis updated an issue Puppet / PUP-1135 Undeprecate 'puppet kick' run mode Change By: Nick Lewis People interested in ` bq. Please not deprecate puppet kick ` functionality should set up . We use puppet in some our projects, and not use mcollective , also dont plan use mcollective . Supporting it causes problems like #10418 Why? Mcollective is require mq (activemq/rabbitmq & etc) and provides unneeded functionality . Let's consider removing it for Telly. We can use one function from mcollective puppet agent runonce, but why do we need to install extra software, and extra daemon on each agent? Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1135) Undeprecate 'puppet kick' run mode
Title: Message Title Nick Lewis commented on an issue Re: Undeprecate 'puppet kick' run mode I'm rewording this ticket a bit to reflect that the new request is actually to not deprecate puppet kick. Add Comment Puppet / PUP-1135 Undeprecate 'puppet kick' run mode People interested in `puppet kick` functionality should set up mcollective. Supporting it causes problems like #10418. Let's consider removing it for Telly. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1135) Undeprecate 'puppet kick' run mode
Title: Message Title Nick Lewis updated an issue Puppet / PUP-1135 Undeprecate 'puppet kick' run mode Change By: Nick Lewis Summary: Deprecate Undeprecate 'puppet kick' run mode Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1135) Undeprecate 'puppet kick' run mode
Title: Message Title Nick Lewis assigned an issue to Eric Sorenson Puppet / PUP-1135 Undeprecate 'puppet kick' run mode Change By: Nick Lewis Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-914) expanded_relationship.dot should not have both containment and relationship edges
Title: Message Title Nick Lewis commented on an issue Re: expanded_relationship.dot should not have both containment and relationship edges I believe the problem here isn't that containment is represented, but that both the admissible and completed whits masquerade as the class in the dot file. Where they are really named Whit[admissible_foo] and Whit[completed_foo], they both stringify themselves as Class[foo]. Since every resource in the class has an edge from the admissible whit and an edge to the completed whit, in the dot output, they end up having an edge to and an edge from the class. Add Comment Puppet / PUP-914 expanded_relationship.dot should not have both containment and relationship edges # Overview # Running against master (2.7.0rc3-135-g520cbc0) I notice that using --graph has obvious cycles in the graph when the catalog itself does not actually have cycles and applies cleanly. Please see the attached screenshot. Talking with Daniel, the suspicion is that the graphing output is not drawing a distinction between containment edges... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are
Jira (PUP-1240) err: Failed to apply catalog: Parameter repeat failed: Repeat must be 1 unless periodmatch is 'distance', not 'number'
Title: Message Title Nick Lewis updated an issue Puppet / PUP-1240 err: Failed to apply catalog: Parameter repeat failed: Repeat must be 1 unless periodmatch is 'distance', not 'number' Change By: Nick Lewis Reporter: redmine.exporter Jo Rhett Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1986) Permissions for libdir are set arbitrarily
Title: Message Title Nick Lewis created an issue Puppet / PUP-1986 Permissions for libdir are set arbitrarily Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 19/Mar/14 11:10 AM Priority: Normal Reporter: Nick Lewis It appears that the mode for libdir is set during pluginsync, to the mode of the lib/ directory of some module being synced (apparently whichever comes first). However, the owner and group are always set to root. This means that a module which is readable only by puppet in the modulepath becomes readable only by root in the libdir. That causes problems for users who install modules with restrictive umasks and wish to install plugins for the puppet master, since it isn't actually allowed to load them from the libdir (and require won't find them in the modulepath). Worse still, the mode is set separately from the standard settings catalog, which means even overriding it in puppet.conf will cause it to be set correctly and then changed later by pluginsync. Add Comment
Jira (PDB-1016) Race condition in puppetdb init script `restart` action
Title: Message Title Nick Lewis moved an issue PuppetDB / PDB-1016 Race condition in puppetdb init script `restart` action Change By: Nick Lewis Component/s: RE Component/s: PuppetDB Component/s: RE Affects Version/s: PE 3.3.0 Workflow: Puppet Enterprise Engineering Workflow Key: PE PDB - 4771 1016 Project: Puppet Enterprise [Internal] PuppetDB Add Comment
Jira (PUP-3147) New gid fact is causing problems in one of my defined types
Title: Message Title Nick Lewis commented on PUP-3147 Re: New gid fact is causing problems in one of my defined types This looks sort of related to PUP-3505 , but it happens with both current and future parser, even with that fix. I found that if you add a default of undef to the $gid param on account::base then it's correctly undef. 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.
Jira (PUP-3147) New gid fact is causing problems in one of my defined types
Title: Message Title Nick Lewis commented on PUP-3147 Re: New gid fact is causing problems in one of my defined types Reopening as this still seems like incorrect behavior, despite having a workaround. 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.
Jira (PUP-2105) Puppet config face and the --configprint option operate directly on environment.conf.
Title: Message Title Nick Lewis commented on PUP-2105 Re: Puppet config face and the --configprint option operate directly on environment.conf. The use case in PE is for the agent installer to be able to set puppet.conf to point at the correct server before puppet runs. In that case, there's no module available that can do it. I don't have much opinion beyond wanting that specific use case to continue working. We don't have a specific need to modify environment.conf. 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.
Jira (PUP-2531) Provide validation tool for EPP
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet / PUP-2531 Provide validation tool for EPP Change By: Nick Lewis Assignee: Nick Lewis 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.
Jira (PUP-2531) Provide validation tool for EPP
Title: Message Title Nick Lewis commented on PUP-2531 Re: Provide validation tool for EPP Merged to master in 5224ead. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (BOLT-719) Allow modulepath to include paths relative to the Boltdir
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-719 Allow modulepath to include paths relative to the Boltdir Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-719) Allow modulepath to include paths relative to the Boltdir
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-719 Allow modulepath to include paths relative to the Boltdir Change By: Nick Lewis Release Notes: New Feature 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 (BOLT-719) Allow modulepath to include paths relative to the Boltdir
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-719 Allow modulepath to include paths relative to the Boltdir Change By: Nick Lewis Release Notes Summary: If relative paths (such as "modules" or "site") are included in the modulepath setting specified in the config file, they will now be based on the Boltdir rather than the current working directory. This allows a Boltdir to be used portably between multiple users.This is a breaking change for any users who were relying on the previous behavior. 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 (BOLT-766) Add site to the end of the default modulepath
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-766 Add site to the end of the default modulepath Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-766) Add site to the end of the default modulepath
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-766 Add site to the end of the default modulepath Change By: Nick Lewis Release Notes: New Feature 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 (BOLT-766) Add site to the end of the default modulepath
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-766 Add site to the end of the default modulepath Change By: Nick Lewis Release Notes Summary: The default modulepath in Bolt is now `Boltdir/modules:Boltdir/site`. This provides a directory that can be managed from a Puppetfile with `bolt puppetfile install` (Boltdir/modules), as well as a directory that can contain custom content not managed by a Puppetfile (Boltdir/site). 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 (BOLT-766) Add site to the end of the default modulepath
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-766 Add site to the end of the default modulepath Change By: Nick Lewis Fix Version/s: BOLT Next 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 (BOLT-643) Add apply functionality to bolt_shim
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-643 Add apply functionality to bolt_shim Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Nick Lewis commented on BOLT-840 Re: Include unvendored Puppet 6 content in Bolt We need to install these to a location where we can skip syncing them to agents during apply(), because they're a) unnecessary, b) potentially incompatible with Puppet 5 agents. 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 (BOLT-842) set_feature(), etc functions should work with a TargetSpec
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-842 set_feature(), etc functions should work with a TargetSpec Issue Type: Improvement Assignee: Unassigned Created: 2018/09/17 4:16 PM Priority: Normal Reporter: Nick Lewis Currently, set_feature() and related functions operate on a single Target instance, which requires one to call get_targets() and loop over the results to set a feature on multiple targets. Those functions should accept a TargetSpec and expand it if necessary. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-843) Generate a "retry" file when some nodes fail
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-843 Generate a "retry" file when some nodes fail Issue Type: New Feature Assignee: Unassigned Created: 2018/09/17 4:17 PM Priority: Normal Reporter: Nick Lewis When a task/command/script/upload fails, Bolt should generate a retry file that includes the list of nodes that failed. That simplifies iterative workflows, whereby a user can try to run a task, make any needed adjustments on failed nodes, and then try it again. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-840 Include unvendored Puppet 6 content in Bolt Change By: Nick Lewis Release Notes: Bug Fix 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 (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-840 Include unvendored Puppet 6 content in Bolt Change By: Nick Lewis Release Notes Summary: The apply() functionality is now compatible with Puppet 6 agents. 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 (BOLT-852) password doesnt work with winrm
Title: Message Title Nick Lewis commented on BOLT-852 Re: password doesnt work with winrm It looks like that was introduced as a fix for BOLT-124. That ticket points out that encoding the URI component didn't work, but doesn't provide any justification for why it ought to, and I can't imagine users would intuit that they ought to encode those components. Our docs don't mention that behavior. I think it would be fine to simply reverse that change. 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 (BOLT-854) run-as can corrupt task stdin over ssh
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-854 run-as can corrupt task stdin over ssh Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-854) run-as can corrupt task stdin over ssh
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-854 run-as can corrupt task stdin over ssh Issue Type: Bug Assignee: Unassigned Created: 2018/09/19 11:25 AM Priority: Normal Reporter: Nick Lewis When using complex stdin for a task (like when using apply() for instance), running bolt with run-as can corrupt the input. When using run-as, we generate a wrapper script that invokes the command and has the stdin inline in a bash heredoc. We don't quote that heredoc, which means it's possible for certain escape sequences to be honored and cause incorrect input. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-854) run-as can corrupt task stdin over ssh
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-854 run-as can corrupt task stdin over ssh Change By: Nick Lewis Sprint: Bolt Kanban 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 (BOLT-719) Allow modulepath to include paths relative to the Boltdir
Title: Message Title Nick Lewis commented on BOLT-719 Re: Allow modulepath to include paths relative to the Boltdir The default path for modules is modules inside the Boltdir That should say the default path is modules:site. 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 (BOLT-854) run-as can corrupt task stdin over ssh
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-854 run-as can corrupt task stdin over ssh Change By: Nick Lewis Release Notes: Bug Fix 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 (BOLT-854) run-as can corrupt task stdin over ssh
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-854 run-as can corrupt task stdin over ssh Change By: Nick Lewis Release Notes Summary: This fixes an issue where tasks could sometimes receive corrupted input when using --run-as over SSH. Tasks should now reliably receive correctly-formatted JSON input. 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 (BOLT-857) apply() loads Puppet features from the default modulepath
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-857 apply() loads Puppet features from the default modulepath Issue Type: Bug Assignee: Unassigned Created: 2018/09/20 1:18 PM Priority: Normal Reporter: Nick Lewis When running an apply() block with a module that adds a new Puppet feature, Puppet will attempt to load that feature from the default modulepath instead of the temporary modulepath containing the synced plugins. That can cause features not to be loaded, or for the wrong version to be loaded. We override current_environment in the Puppet context with a new modulepath, but we don't override the environments element of the context. Some code looks up current_environment, but other code looks up environments and then retrieves the environment from that list. Since we're not overriding that value, it contains the default version of that environment. Add Comment
Jira (BOLT-857) apply() loads Puppet features from the default modulepath
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-857 apply() loads Puppet features from the default modulepath Change By: Nick Lewis Release Notes: Bug Fix 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 (BOLT-857) apply() loads Puppet features from the default modulepath
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-857 apply() loads Puppet features from the default modulepath Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-857) apply() loads Puppet features from the default modulepath
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-857 apply() loads Puppet features from the default modulepath Change By: Nick Lewis Sprint: Bolt Kanban 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 (BOLT-857) apply() loads Puppet features from the default modulepath
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-857 apply() loads Puppet features from the default modulepath Change By: Nick Lewis Release Notes Summary: The apply() function was incorrectly loading module content that happened to be present on the target node. It will now only load content present on the Bolt controller. 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 (BOLT-816) Support using control repo as boltdir
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-816 Support using control repo as boltdir Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-627) Secure password prompt fails on Windows
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-627 Secure password prompt fails on Windows Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-829 modulepath argument does not handle paths with spaces Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title Nick Lewis commented on BOLT-829 Re: modulepath argument does not handle paths with spaces I see this behavior happen in cygwin with any batch script and an argument containing spaces. I honestly have no idea what's going on, but it doesn't look like it's really Bolt-related... 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 (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title Nick Lewis commented on BOLT-829 Re: modulepath argument does not handle paths with spaces Because we don't believe any users want to run bolt via cygwin, and it's only an issue for testing, I think any solution here probably revolves around modifying how bolt is invoked by the tests. Calling ruby.exe -S bolt seems perhaps like the best bet. 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 (BOLT-413) Displaying certain types is overly verbose
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-413 Displaying certain types is overly verbose Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-858) I want to apply a manifest remotely without a plan
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-858 I want to apply a manifest remotely without a plan Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Nick Lewis commented on BOLT-832 Re: Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large The 65536 byte limit was a regression that will be fixed in the next PE releases. The proper limit, which is configurable, is 64mb. That issue should only have affected the allowable size of task requests, not of responses. Response sizes should have been properly using the configurable 64mb limit. If there’s a problem there, I would love to know more detail. 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 (BOLT-928) Purge old task files from the task cache
Title: Message Title Nick Lewis commented on BOLT-928 Re: Purge old task files from the task cache http://ruby-concurrency.github.io/concurrent-ruby/master/Concurrent/TimerTask.html 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 (BOLT-951) `facts` plan doesn't set facts on any nodes when some nodes fail
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-951 `facts` plan doesn't set facts on any nodes when some nodes fail Issue Type: Bug Assignee: Unassigned Created: 2018/10/25 10:28 AM Priority: Normal Reporter: Nick Lewis Previously, the facts plan swallowed all errors and returned unconditional success, only setting facts on the nodes that had succeeded. It was then improved to throw errors when something failed. That change also caused the plan to no longer set any facts if some nodes have failed. Whereas the user previously had no real option of failing when the plan failed, they now have no real option of continuing when the plan succeeded, as it won't have done any work. The plan should catch errors in the facts task, set facts on whichever nodes succeeded, and then propagate the error if one happened. Add Comment
Jira (BOLT-858) I want to apply a manifest remotely without a plan
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-858 I want to apply a manifest remotely without a plan Change By: Nick Lewis Release Notes Summary: This introduces a new command `bolt apply`, which is used to directly apply Puppet manifest code on targets without having to wrap them in an `apply()` block in a plan. 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 (BOLT-644) Collect analytics on catalogs applied with bolt.
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-644 Collect analytics on catalogs applied with bolt. Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-969) bolt-server clears its tmpdir during cache purging
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-969 bolt-server clears its tmpdir during cache purging Issue Type: Bug Assignee: Unassigned Created: 2018/11/09 1:52 PM Priority: Normal Reporter: Nick Lewis By default, bolt-server clears out any cached tasks (directories in cache) which haven't been touched in a week. Unfortunately, bolt-server also uses a tmp dir in the cache as the temporarily download location for tasks until copying them into the proper location. That tmp dir is also subject to the cache purge, which means it will be deleted if no new tasks have been downloaded in the past week. Once that directory has been deleted, new task downloads will fail until bolt-server is restarted, at which point it will recreate the directory. The cache/tmp directory should either be moved outside the cache directory or excluded from the purge. Add Comment
Jira (BOLT-815) Mark bolt_shim file content arguments as sensitive
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-815 Mark bolt_shim file content arguments as sensitive Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-815) Mark bolt_shim file content arguments as sensitive
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-815 Mark bolt_shim file content arguments as sensitive Change By: Nick Lewis Sprint: Bolt Kanban 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 (BOLT-817) Support an array of directories for modulepath in config
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-817 Support an array of directories for modulepath in config Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-817) Support an array of directories for modulepath in config
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-817 Support an array of directories for modulepath in config Change By: Nick Lewis Release Notes: Enhancement 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 (BOLT-817) Support an array of directories for modulepath in config
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-817 Support an array of directories for modulepath in config Change By: Nick Lewis Release Notes Summary: The `modulepath` setting in `bolt.yaml` can now be specified as an array of directories, rather than just a PATH-like string, allowing a single `bolt.yaml` to be used on both *nix and Windows clients. 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 (BOLT-1022) Allow for hyphens in aliases and group names
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases and group names Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1022) Allow for hyphens in aliases and group names
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases and group names Change By: Nick Lewis Release Notes: Enhancement 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 (BOLT-1022) Allow for hyphens in aliases and group names
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases and group names Change By: Nick Lewis Release Notes Summary: Group names and node aliases in the Bolt inventory can now contain hyphens. 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 (BOLT-987) Add CLI front end to plan executor
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-987 Add CLI front end to plan executor Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1094) Bolt Puppetfile install deletes modules in modules directory.
Title: Message Title Nick Lewis commented on BOLT-1094 Re: Bolt Puppetfile install deletes modules in modules directory. We should check whether any modules are present that aren't declared in the Puppetfile and refuse to do any work unless something like --force is specified. 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 (BOLT-987) Add CLI front end to plan executor
Title: Message Title Nick Lewis commented on BOLT-987 Re: Add CLI front end to plan executor I have a basic version of this working up in a github repo: https://github.com/puppetlabs/puppet-plan It should basically work once BOLT-1007 and BOLT-1009 are working. At least, it can start a plan, wait for it to finish, and then print the result. 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 (BOLT-1100) `bolt puppetfile install` fails to install forge modules when run from cmd.exe
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1100 `bolt puppetfile install` fails to install forge modules when run from cmd.exe Issue Type: Bug Assignee: Unassigned Created: 2019/01/24 11:22 AM Priority: Normal Reporter: Nick Lewis When running bolt on windows from cmd.exe, we don't properly set up the environment to use our SSL certificate bundle. This causes `bolt puppetfile install` to fail to install modules because it can't trust the forge. We should include a bolt.bat wrapper that sets up the proper environment, akin to the puppet.bat wrapper in the puppet-agent package. Currently, we just use the auto-generated wrapper from rubygems, which doesn't meet our needs. Add Comment
Jira (BOLT-1100) `bolt puppetfile install` fails to install forge modules when run from cmd.exe
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1100 `bolt puppetfile install` fails to install forge modules when run from cmd.exe Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1100) `bolt puppetfile install` fails to install forge modules when run from cmd.exe
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1100 `bolt puppetfile install` fails to install forge modules when run from cmd.exe Change By: Nick Lewis Sprint: Bolt Kanban 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 (BOLT-1057) BoltSpec::Run functions accept options inconsistently
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1057
BoltSpec::Run functions accept options inconsistently
Change By:
Nick Lewis
Some of the boltspec run functions have arguments with defaults while others have options. We should standardize on one method. Whoever pulls the ticket try to optimize experience here. Maybe require more arguments and consolidate key-word arguments into a single options hash. Specifically if there is a params hash or arguments array then require those always. Everything else belongs in options hash. Special notes about run_script: https://github.com/puppetlabs/bolt/blob/9427286edf5f69c9d7bb2a041be29515ab8633c1/lib/bolt_spec/run.rb#L43`arguments` array is required, options hash is a keyword argument. That way you can pass the options hash without it being interpreted as the keyword arguments. {code} run_script(script, targets, arguments, options: {}, config: nil, inventory: nil) {code} Finally, whoever makes PR, mention it in slack bc it will affect people.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1100) Bolt powershell module is not reliably installed
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1100 Bolt powershell module is not reliably installed Change By: Nick Lewis Summary: `bolt puppetfile install` fails to install forge modules when run from cmd.exe Bolt powershell module is not reliably installed 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 (BOLT-1100) Bolt powershell module is not reliably installed
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1100
Bolt powershell module is not reliably installed
Change By:
Nick Lewis
When In certain cases, the powershell wrapper for Bolt is not loaded when running bolt on windows from cmd powershell . exe That causes either the bolt command to not be found , we don't properly set up or the environment to not be set up appropriately. In particular, we use our an environment variable to configure the SSL certificate bundle . This causes ` , so failing to set that up means {{ bolt puppetfile install ` to }} will fail to install modules because it can't trust from the forge. We should Cases where the wrapper might not be loaded include a {{bolt :• PS 2 . bat}} wrapper that sets up the proper environment 0 and 3.0 don't automatically load modules. For this case , akin we should add [documentation similar to PDK|] explaining how to install the {{puppet module manually . bat}} wrapper in • PS 6.0 uses a different module path. It's unclear what the puppet-agent package solution for this problem is . Currently, we just use • Certain execution policies may forbid the auto-generated wrapper from rubygems, which doesn't meet our needs loading of unsigned modules . We should introduce a signing step to the build process.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1100) Bolt powershell module is not reliably installed
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1100
Bolt powershell module is not reliably installed
Change By:
Nick Lewis
In certain cases, the powershell wrapper for Bolt is not loaded when running powershell. That causes either the bolt command to not be found, or the environment to not be set up appropriately. In particular, we use an environment variable to configure the SSL certificate bundle, so failing to set that up means {{bolt puppetfile install}} will fail to install modules from the forge.Cases where the wrapper might not be loaded include:• PS 2.0 and 3.0 don't automatically load modules. For this case, we should add [documentation similar to PDK| https://puppet.com/docs/pdk/1.x/install_pdk_windows.html#task-3944 ] explaining how to install the module manually.• PS 6.0 uses a different module path. It's unclear what the solution for this problem is.• Certain execution policies may forbid the loading of unsigned modules. We should introduce a signing step to the build process.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1107) plan executor should use the internal API to connect to orchestrator
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1107 plan executor should use the internal API to connect to orchestrator Issue Type: Improvement Assignee: Unassigned Created: 2019/01/31 2:23 PM Priority: Normal Reporter: Nick Lewis Currently, the plan executor service uses the public API to connect to orchestrator with a token. That means that it can only run plans started by the same user as its token was generated for. It should use a client certificate instead, which will allow it to use the internal API, which can run tasks and finish plans for any user. This requires work in orchestrator_client-ruby to support configuration via certificates. Add Comment This message
Jira (BOLT-1107) plan executor should use the internal API to connect to orchestrator
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1107 plan executor should use the internal API to connect to orchestrator Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1107) plan executor should use the internal API to connect to orchestrator
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1107 plan executor should use the internal API to connect to orchestrator Change By: Nick Lewis Sprint: Bolt Kanban 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 (BOLT-1107) plan executor should use the internal API to connect to orchestrator
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1107 plan executor should use the internal API to connect to orchestrator Change By: Nick Lewis Issue Type: Improvement Sub-task Parent: BOLT-986 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 (BOLT-992) Modify WinRM timeout error message
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-992 Modify WinRM timeout error message Change By: Nick Lewis Summary: Modify WinRM timeout error message 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 (BOLT-1125) Add info about what was run to Result or ResultSet
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1125 Add info about what was run to Result or ResultSet Change By: Nick Lewis Sprint: Bolt Ready for Grooming 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 (BOLT-1125) Add info about what was run to Result or ResultSet
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1125 Add info about what was run to Result or ResultSet Issue Type: Improvement Assignee: Unassigned Created: 2019/02/11 2:19 PM Priority: Normal Reporter: Nick Lewis Currently, the Result and ResultSet types don't include any fields indicating what they are the result of. That makes it difficult to write any generic functions to operate on results, for instance to report them to an external source. One of those types should include an appropriate field or fields to determine what kind of thing was run and what the instance was. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1127 Bolt should echo port if custom SSH port is used Change By: Nick Lewis Team: Bolt 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 (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1127 Bolt should echo port if custom SSH port is used Change By: Nick Lewis Sprint: Bolt Ready for Grooming 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 (BOLT-1057) BoltSpec::Run functions accept options inconsistently
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1057 BoltSpec::Run functions accept options inconsistently Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1100) Bolt powershell module is not reliably installed
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1100 Bolt powershell module is not reliably installed Change By: Nick Lewis 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 (BOLT-1100) Bolt powershell module is not reliably installed
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1100 Bolt powershell module is not reliably installed Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1073) Notice level logger is not configured during plan tests
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1073 Notice level logger is not configured during plan tests Change By: Nick Lewis Assignee: Nick Lewis 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 (BOLT-1073) Notice level logger is not configured during plan tests
Title: Message Title Nick Lewis commented on BOLT-1073 Re: Notice level logger is not configured during plan tests `BoltSpec::Plans.init` does currently call `Logging.init` with the appropriate set of log levels. Is that something we need to make automatic or can we expect users to call that method in `spec_helper`? 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 (BOLT-305) Task metadata should allow defaults for parameter values
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-305 Task metadata should allow defaults for parameter values Change By: Nick Lewis Sprint: Bolt Ready for Grooming 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 (BOLT-1151) Load and show simple plans.
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1151 Load and show simple plans. Change By: Nick Lewis Assignee: Nick Lewis 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.
