Jira (BOLT-200) Prevent WinRM stream reading deadlock
Title: Message Title Geoff Nichols assigned an issue to Ethan Brown Puppet Task Runner / BOLT-200 Prevent WinRM stream reading deadlock Change By: Geoff Nichols Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-200) Prevent WinRM stream reading deadlock
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet Task Runner / BOLT-200 Prevent WinRM stream reading deadlock Change By: Geoff Nichols Assignee: Ethan Brown Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-200) Prevent WinRM stream reading deadlock
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet Task Runner / BOLT-200 Prevent WinRM stream reading deadlock Change By: Geoff Nichols Assignee: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-72) Don't invoke new powershell instances
Title: Message Title Ethan Brown commented on BOLT-72 Re: Don't invoke new powershell instances I put together a few quick tests around understanding if there is bleed across invocations, but I think some more work should be done to fully vet. It appears that the between the PowerShell ServerRemoteHost using a RunspacePool when executing PowerShell code, and the winrm gem performing runspace management, that each command invocation is isolated already. I ran some simple tests with Bolt over command, script and task execution, and noticed that no state was shared from one command to the next. Note that in this case, script and task were both running against new powershell.exe instances, but the behavior of command is enough to conclude that state is not shared. https://gist.github.com/Iristyle/56b3108be7c9b401effe21a364880b74#results So in broader terms, I think that we can move forward on simplifying the PowerShell execution mechanism so that Invoke-Interpreter is not called under the hood to launch a new powershell.exe for the sake of isolating runs. This also means that we shouldn't need anything like the runspace manager in the PowerShell module at https://github.com/puppetlabs/puppetlabs-powershell/blob/master/lib/puppet_x/templates/powershell/init_ps.ps1 as runspaces are already being managed. It seems reasonable to assume that ResetRunspaceState is already called on the Runspaces as they're handed out ... but worst case scenario we may have to perform some up-front Runspace cleanup like what's done in the PowerShell module at https://github.com/puppetlabs/puppetlabs-powershell/blob/d0166e4ec6b7e6f1abdb21f9efb439a700940ee1/lib/puppet_x/templates/powershell/init_ps.ps1#L414-L463 When this change is made, some tests should be added to show state doesn't bleed (we may have to ask the winrm library to use some well-known GUIDs to get the same runspace out of the pool) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-208) WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks
Title: Message Title Ethan Brown commented on BOLT-208 Re: WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks Merged to master in https://github.com/puppetlabs/bolt/commit/332513f5506a891214ece22a10c45d941cb28940 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Title: Message Title
Zach Reichert updated an issue
Puppet Task Runner / BOLT-209
Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Change By:
Zach Reichert
*Given *An empty known_hosts file *When *{code}mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity! mvaypj4nxldckoj.delivery.puppetlabs.net: Host key verification failed for mvaypj4nxldckoj.delivery.puppetlabs.net: fingerprint 7a:78:5a:da:31:f5:b7:68:b8:4a:49:92:30:cb:48:ee is unknown for "mvaypj4nxldckoj.delivery.puppetlabs.net,10.32.122.70" ucqxte3fgv2l7v7.delivery.puppetlabs.net: Host key verification failed for ucqxte3fgv2l7v7.delivery.puppetlabs.net: fingerprint 9d:b1:85:d4:b2:4a:73:d2:aa:7a:8c:f7:bd:08:c2:d3 is unknown for "ucqxte3fgv2l7v7.delivery.puppetlabs.net,10.32.119.57" odcckquiw5m46l9.delivery.puppetlabs.net: Host key verification failed for odcckquiw5m46l9.delivery.puppetlabs.net: fingerprint 23:d3:c3:60:24:40:08:55:e6:db:16:cb:95:f9:5f:90 is unknown for "odcckquiw5m46l9.delivery.puppetlabs.net,10.32.124.170" Ran on 3 nodes in 0.07 seconds{code}*Then*I expect to see a non-zero exit code{code}[1] pry(#)> result.exit_code=> 0{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet
Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Title: Message Title
Zach Reichert updated an issue
Puppet Task Runner / BOLT-209
Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Change By:
Zach Reichert
*Given *An empty known_hosts file*When *{code}mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity! mvaypj4nxldckoj.delivery.puppetlabs.net: Host key verification failed for mvaypj4nxldckoj.delivery.puppetlabs.net: fingerprint 7a:78:5a:da:31:f5:b7:68:b8:4a:49:92:30:cb:48:ee is unknown for "mvaypj4nxldckoj.delivery.puppetlabs.net,10.32.122.70" ucqxte3fgv2l7v7.delivery.puppetlabs.net: Host key verification failed for ucqxte3fgv2l7v7.delivery.puppetlabs.net: fingerprint 9d:b1:85:d4:b2:4a:73:d2:aa:7a:8c:f7:bd:08:c2:d3 is unknown for "ucqxte3fgv2l7v7.delivery.puppetlabs.net,10.32.119.57" odcckquiw5m46l9.delivery.puppetlabs.net: Host key verification failed for odcckquiw5m46l9.delivery.puppetlabs.net: fingerprint 23:d3:c3:60:24:40:08:55:e6:db:16:cb:95:f9:5f:90 is unknown for "odcckquiw5m46l9.delivery.puppetlabs.net,10.32.124.170" Ran on 3 nodes in 0.07 seconds{code}*Then*I expect to see a non-zero exit code{code}[1] pry(#)> result.exit_code=> 0{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet
Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Title: Message Title
Zach Reichert updated an issue
Puppet Task Runner / BOLT-209
Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Change By:
Zach Reichert
* Given * An empty known_hosts file * When * {code}mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity! mvaypj4nxldckoj.delivery.puppetlabs.net: Host key verification failed for mvaypj4nxldckoj.delivery.puppetlabs.net: fingerprint 7a:78:5a:da:31:f5:b7:68:b8:4a:49:92:30:cb:48:ee is unknown for "mvaypj4nxldckoj.delivery.puppetlabs.net,10.32.122.70" ucqxte3fgv2l7v7.delivery.puppetlabs.net: Host key verification failed for ucqxte3fgv2l7v7.delivery.puppetlabs.net: fingerprint 9d:b1:85:d4:b2:4a:73:d2:aa:7a:8c:f7:bd:08:c2:d3 is unknown for "ucqxte3fgv2l7v7.delivery.puppetlabs.net,10.32.119.57" odcckquiw5m46l9.delivery.puppetlabs.net: Host key verification failed for odcckquiw5m46l9.delivery.puppetlabs.net: fingerprint 23:d3:c3:60:24:40:08:55:e6:db:16:cb:95:f9:5f:90 is unknown for "odcckquiw5m46l9.delivery.puppetlabs.net,10.32.124.170" Ran on 3 nodes in 0.07 seconds{code} * Then * I expect to see a non-zero exit code{code}[1] pry(#)> result.exit_code=> 0{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google
Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Title: Message Title Zach Reichert updated an issue Puppet Task Runner / BOLT-209 Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file Change By: Zach Reichert Environment: Centos 7 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Title: Message Title Zach Reichert commented on BOLT-209 Re: Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file For context on centos7 I get exit code 255 when I attempt this manually [root@mvaypj4nxldckoj ~]# ssh r...@mvaypj4nxldckoj.delivery.puppetlabs.net The authenticity of host 'mvaypj4nxldckoj.delivery.puppetlabs.net (10.32.122.70)' can't be established. ECDSA key fingerprint is f0:4f:93:08:cf:a7:05:da:7e:ec:f9:a0:e7:b0:4f:47. Are you sure you want to continue connecting (yes/no)? no Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file
Title: Message Title Zach Reichert created an issue Puppet Task Runner / BOLT-209 Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file Issue Type: Bug Affects Versions: BOLT 0.7.0 Assignee: Unassigned Created: 2017/11/07 2:44 PM Priority: Normal Reporter: Zach Reichert Given An empty known_hosts file When mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity! mvaypj4nxldckoj.delivery.puppetlabs.net:
Jira (PDOC-188) Document our own modules with Puppet Strings
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-188 Document our own modules with Puppet Strings Change By: Hailee Kenney Eventually we should work towards Strings compatible comments in all puppetlabs supported modules (as this is the standard we're proposing other people hold their modules too to ). We should start though by picking a list of several modules, at least one or two of which are rather complicated, to document with Strings. That way, users have examples to look to when trying to figure out how to document their own modules. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-188) Document our own modules with Puppet Strings
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-188 Document our own modules with Puppet Strings Change By: Hailee Kenney Eventually we should work towards Strings compatible comments in all puppetlabs supported modules (as this is the standard we're proposing other people hold their modules too). We should start though by picking a list of several modules, at least one or two of which are rather complicated, to document with Strings. That way, users have examples to look to when trying to figure out how to document their own modules. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-186) Comprehensive strings style guide
Title: Message Title Hailee Kenney commented on PDOC-186 Re: Comprehensive strings style guide Just a note that this is something we should probably interface with Vox about. They've been using Strings in their modules for a while and probably have some good ideas around best practices we should take into account. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-183) Puppet Strings 2.0.0 (?)
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 (?) Change By: Hailee Kenney The next steps to get strings to a state where we and the community agree it's actually complete.More details in this doc:https://docs.google.com/document/d/1Tj1Y_RxKzP5lGJKXwxQWzNpYu_wVMpYF4JTuhkc2oqw/edit Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-189) PDK Integration
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-189 PDK Integration Change By: Hailee Kenney Key: MODULES PDOC - 5825 189 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-188) Document our own modules with Puppet Strings
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-188 Document our own modules with Puppet Strings Change By: Hailee Kenney Key: MODULES PDOC - 5820 188 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-184) Add ability to generate Markdown
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-184 Add ability to generate Markdown Change By: Hailee Kenney Summary: Add ability to generate mark down Markdown Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-187) Strings 2.0.0 improvements blog post
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-187 Strings 2.0.0 improvements blog post Change By: Hailee Kenney Key: MODULES PDOC - 5824 187 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Alex Dreyer commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans I don't like target node for two reasons: 1. It seems excessively verbose for something you use in most plans. 2. It's 'node centric' and targets should eventually align with things people don't like to call nodes like devices and services. I'm bad at naming things though. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-186) Comprehensive strings style guide
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-186 Comprehensive strings style guide Change By: Hailee Kenney Key: MODULES PDOC - 5819 186 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-185) Keep generated content in sync with static content in README automatically
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-185 Keep generated content in sync with static content in README automatically Change By: Hailee Kenney Summary: Keep generated content in sync with static content in readme README automatically Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-185) Keep generated content in sync with static content in readme automatically
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-185 Keep generated content in sync with static content in readme automatically Change By: Hailee Kenney Key: MODULES PDOC - 5823 185 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDOC-184) Add ability to generate mark down
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-184 Add ability to generate mark down Change By: Hailee Kenney Issue Type: Story New Feature Key: MODULES PDOC - 5821 184 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8128) Add URI data type
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-8128
Add URI data type
Change By:
Thomas Hallgren
A new {{URI}} parameterized data type should be added. The type is described as:{code:puppet}type IntegerParameter = Variant[Type[Init[Integer]],Type[Undef],Type[NotUndef]]type StringParameter = Variant[String,Regexp,Type[Enum],Type[Pattern],Type[Undef],Type[NotUndef]]type URI = Object[ type_parameters => {'scheme' => StringParameter,'user_info' => StringParameter,'host' => StringParameter,'port' => IntegerParameter,'path' => StringParameter,'query' => StringParameter,'fragment' => StringParameter,'opaque' => StringParameter, }, attributes => {'scheme' => String,'user_info' => { type => Optional[String], value => undef },'host' => { type => Optional[String], value => undef },'port' => { type => Optional[Integer[0,default]], value => undef },'path' => { type => Optional[String], value => undef },'query' => { type => Optional[String], value => undef },'fragment' => { type => Optional[String], value => undef },'opaque' => { type => Optional[String], value => undef }, }]{code}and {{'opaque'}} is mutually exclusive to all other attributes except {{'scheme'}}.An instance can be assembled from the individual parts (provided as a hash) or parsed from a string and make the parts available as instance attributes.The {{URI}} data type is parameterized so that it can constrain both what parts may or may not contain and what those parts in turn must match. Since the parts are well known by name, e.g.:{code} hierarchical┌───┴─┐authority path┌───┴───┐┌───┴┐ abc://username:passw...@example.com:123/path/data?key=value=value2#fragid1 └┬┘ └───┬───┘ └┬┘ └┬┘ └─┬─┘ └──┬──┘scheme userinfo host port query fragment urn:example:mammal:monotreme:echidna └┬┘ └──┬───┘scheme opaque{code} it is possible to describe a parameterized {{URI}} as taking one parameter described as:{code:puppet}Variant[ String[1], Hash[Enum[scheme,userinfo,host,port,path,query,fragment,opaque],Variant[Regexp,String,Type[Enum],Type[Pattern],Type[Undef],Type[NotUndef{code}A missing field indicates that the field is unconstrained. *Examples:*Allow any http/https URI without query or fragments (scheme comparisons must always be case-insensitive):{code:puppet}URI[scheme => Enum[http,https,true], query => Undef, fragment => Undef]{code}Require that the URI has an absolute path:{code:puppet}URI[path => /^\// ]{code}or conversely, require it to be relative:{code:puppet}URI[path => /^[^/]/ ]{code} and, as described in the initial proposal, it's still possible to constrain by using a string. Here, the URI is constrained by 'scheme' and 'host':{code:puppet}URI['http://forge.puppet.com']{code}
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title
Thomas Hallgren commented on PUP-8020
Re: Add data types Nodes and Node to puppet for tasks/plans
Alex Dreyer, yes, you did comment on that PR. And then Henrik Lindberg asked: "IMO - taken out of context it seems a bit too generic. @adreyer are you sure you want just Target? The first time a user may see it is when they read the source of a plan, and they see something like plan foo(Array[Target] $targets) { } - and you then have to think "what is a Target for a plan?"... whereas TargetNode tells you that this is about a node.". I agree with Henrik that the name "Target" is very generic.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1590) Replace ParsedFile with Augeas
Title: Message Title Josh Cooper commented on PUP-1590 Re: Replace ParsedFile with Augeas Michael Smith worked on getting Augeas compiling/working on Windows, see PA-1163. Also we package augeas binaries, lenses, and ruby bindings in puppet-agent. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken in 5.3.3
Title: Message Title Josh Cooper commented on PUP-8126 Re: puppet module install --module_repository broken in 5.3.3 Thanks Christoph Maser. Based on your comment, I'm going to close this. Please reopen if I misunderstood. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-151) Display results as they occur, instead of when all nodes finish
Title: Message Title
Josh Cooper commented on BOLT-151
Re: Display results as they occur, instead of when all nodes finish
To see the new behavior, you can run a sleep command against multiple hosts. The results will be returned based on the randomized sleep order (from least to most), and the total time to execute the command is about as long as the longest sleep time:
$ bx bolt command run 'TM=$(( ( RANDOM % 5 ) + 1)); echo sleeping $TM; sleep $TM' --nodes={m1e986glbi6q1nh,mjhelchmer5bza2,g4m5j35dig6pi2j,heyddx1or8535oo}.delivery.puppetlabs.net -k
mjhelchmer5bza2.delivery.puppetlabs.net:
sleeping 2
m1e986glbi6q1nh.delivery.puppetlabs.net:
sleeping 3
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Rick Sherman commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices In speaking with Kenn Hussey we may be able to merge this feature back down to 1.10.x and 5.3.x as it supports some of our broader goals. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Thomas Kishel commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices Yay! The 'upside' is, by having target use the url fact, FACTER_url is still available. I tried to identify an alternate mechanism to pass the device object, but was unable navigate the indirection ... # f5.rb def self.transport if Puppet::Util::NetworkDevice.current #we are in `puppet device` Puppet::Util::NetworkDevice.current.transport else puts caller #we are in `puppet resource` Puppet::Util::NetworkDevice::Transport::F5.new(Facter.value(:url)) end
Jira (BOLT-72) Don't invoke new powershell instances
Title: Message Title Ethan Brown commented on BOLT-72 Re: Don't invoke new powershell instances Note that this as currently described, this runs a bit counter to BOLT-208. I believe that (after some research into how "isolated" script executions are given the current model), that this ticket should be about more generally optimizing the PowerShell workflow for executing scripts / tasks. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-208) WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks
Title: Message Title Ethan Brown created an issue Puppet Task Runner / BOLT-208 WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks Issue Type: New Feature Affects Versions: BOLT 0.7.0 Assignee: Ethan Brown Created: 2017/11/07 11:28 AM Fix Versions: BOLT 0.8.0 Priority: Normal Reporter: Ethan Brown At this time, there are 3 different execution models in Bolt for WinRM: command - runs PowerShell code directly in the connected WinRM instance - note that for separate Bolt CLI invocations that each command appears to run isolated from one another (presumably the WinRM host creates runspaces / clears state) script - runs a PowerShell script by invoking powershell.exe task - runs arbitrary Ruby based tasks, PowerShell tasks, and Puppet files - using a file extension based registry
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Alex Dreyer commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans I thought I commented on the PR that melinda, michelle and myself looked at how we use "target" in the UI/Docs and we can just change that and call the types "Target" and "Targets" I don't think the regex is that important for now as long as parsing errors generate useful messages Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Florian Klink commented on PUP-8048 Re: puppet / facter fails randomly in low memory situations Running facter --debug alone doesn't fail, and shows a value for operatingsystem. Doing the initial puppet run fails reproducible on a VM with 128MB RAM. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title David Schmitt commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices Thomas Kishel having this will likely fix, or provide a fix for https://github.com/DavidS/puppet-resource_api/blob/60ff8bccbff381b54fd3e67bb2418f1201c0174f/lib/puppet/resource_api/base_context.rb#L10 The only "downside" (if you can even call it that) is that it'll only work for new versions of puppet, and therefore the FACTER_url workaround will likely still be necessary until old versions go out of support. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3630) Configurable facts blacklist
Title: Message Title Susan McNerney commented on PDB-3630 Re: Configurable facts blacklist We will need to defer this to the next LTS z, which will be in Jan/Feb. (2016.4.10), due to lack of time to resolve getting it into 2016.4.9 before our launch window. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3754) (maint) update facts-blacklist docs
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3754 (maint) update facts-blacklist docs Issue Type: Bug Assignee: Unassigned Created: 2017/11/07 10:21 AM Priority: Normal Reporter: gepetto-bot update and move facts blacklist docs to the correct section Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3753) (maint) update facts-blacklist docs
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3753 (maint) update facts-blacklist docs Issue Type: Bug Assignee: Unassigned Created: 2017/11/07 10:15 AM Priority: Normal Reporter: gepetto-bot Update and move blacklist docs to correct section Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8128) Add URI data type
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8128 Add URI data type Issue Type: New Feature Assignee: Thomas Hallgren Created: 2017/11/07 10:14 AM Fix Versions: PUP 5.4.0 Priority: Normal Reporter: Thomas Hallgren A new URI parameterized data type should be added. The type is described as: type IntegerParameter = Variant[Type[Init[Integer]],Type[Undef],Type[NotUndef]] type StringParameter = Variant[String,Regexp,Type[Enum],Type[Pattern],Type[Undef],Type[NotUndef]] type URI = Object[
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Thomas Kishel commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices David Schmitt I recently discovered PDK-610. Does this relate/is this compatible with your work? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans I'll divide this ticket into two tickets then. One for the URI data type (the implementation is complete) and then this one. Alex Dreyer, do you see any point in enforcing a regexp pattern on the string? If so, what regexp? Also, there's still an open question on the PR whether or not it's OK to call the new type described in this ticket TargetNode. I think that would be mine and Henrik's preference. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3752) (maint) update links in release process readme
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3752 (maint) update links in release process readme Issue Type: Bug Assignee: Unassigned Created: 2017/11/07 9:45 AM Priority: Normal Reporter: gepetto-bot update links to the Jenkins manual promotion jobs in the release-process docs Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3630) Configurable facts blacklist
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3630 Configurable facts blacklist Change By: Russell Mull Fix Version/s: PDB 4.2.3.7 Fix Version/s: 4.2.3.8 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken in 5.3.3
Title: Message Title Christoph Maser commented on PUP-8126 Re: puppet module install --module_repository broken in 5.3.3 Hm actually i thought i closed this one. As i said the issue is response['pagination']['next'] returns flase on our in-house puppet-forge changing it to return nil resolves the problem- This https://github.com/puppetlabs/puppet/blob/master/lib/puppet/forge.rb#L231 together with https://github.com/puppetlabs/puppet/blob/master/lib/puppet/forge.rb#L110 is the cause Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Josh Cooper commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices Ah my bad, I missed the linked PR. Thanks for reopening. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-45) Display JSON results
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-45 Display JSON results Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Thomas Kishel commented on PUP-8041 Re: Replace FACTER_url with --target for puppet resource with devices My last comment here, regarding Alexander's 'apply_to_device' questions? If so, this should remain open as it has an open PR under review. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-45) Display JSON results
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-45 Display JSON results Change By: Alex Dreyer Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3630) Configurable facts blacklist
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3630 Configurable facts blacklist Change By: Russell Mull Fix Version/s: PDB 4.2.3.6 Fix Version/s: 4.2.3.7 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken in 5.3.3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8126 puppet module install --module_repository broken in 5.3.3 Change By: Josh Cooper Affects Version/s: PUP 5.3.3 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken in 5.3.3
Title: Message Title Josh Cooper commented on PUP-8126 Re: puppet module install --module_repository broken in 5.3.3 ping Jesse Scott, Ethan Brown I think this is related to https://github.com/puppetlabs/puppet/commit/77606f9ccf828976871a72a61df3066b826aa210 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken in 5.3.3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8126 puppet module install --module_repository broken in 5.3.3 Change By: Josh Cooper Summary: puppet module install --module_repository broken ion in 5.3.3 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken ion 5.3.3
Title: Message Title Michael Smith commented on PUP-8126 Re: puppet module install --module_repository broken ion 5.3.3 Running with --trace would help debugging what code handles this poorly. Mind running that and adding it to the ticket? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8127) Refacter ParseError and ResourceError for better I18n support
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8127
Refacter ParseError and ResourceError for better I18n support
Change By:
Eric Delaney
For better translations we should look at refactoring ExternalFileError and the things built on it like ParseError and Resource Error. As you can see from the below code we append to a message based on line, file, and position information, but this makes it hard to translate. Also note that these messages are not decorated for translation. {code} module ExternalFileError# This module implements logging with a filename and line number. Use this# for errors that need to report a location in a non-ruby file that we# parse.attr_accessor :line, :file, :pos# May be called with 3 arguments for message, file, line, and exception, or# 4 args including the position on the line.#def initialize(message, file=nil, line=nil, pos=nil, original=nil) if pos.kind_of? Exceptionoriginal = pospos = nil end super(message, original) @file = file unless (file.is_a?(String) && file.empty?) @line = line @pos = posenddef to_s msg = super @file = nil if (@file.is_a?(String) && @file.empty?) if @file and @line and @pos"#{msg} at #{@file}:#{@line}:#{@pos}" elsif @file and @line"#{msg} at #{@file}:#{@line}" elsif @line and @pos "#{msg} at line #{@line}:#{@pos}" elsif @line"#{msg} at line #{@line}" elsif @file"#{msg} in #{@file}" elsemsg endend end{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-3647) Puppet stores files forever in state.yaml
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-3647 Puppet stores files forever in state.yaml Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: Many users would like to use recurse. Having it lead to poor performance isn't good. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to
Jira (PUP-8127) Refacter ParseError and ResourceError for better I18n support
Title: Message Title Eric Delaney created an issue Puppet / PUP-8127 Refacter ParseError and ResourceError for better I18n support Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2017/11/07 8:29 AM Priority: Normal Reporter: Eric Delaney For better translations we should look at refactoring ExternalFileError and the things built on it like ParseError and Resource Error. As you can see from the below code we append to a message based on line, file, and position information, but this makes it hard to translate. module ExternalFileError # This module implements logging with a filename and line number. Use this # for errors that need to report a location in a
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Alex Dreyer commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans There is a default in bolt which can be set with the --transport option. I don't think users should have to specify the scheme in the strings they pass and munging the string itself in bolt seems like it defeats the purpose of parsing this in puppet. URI does seem too strict. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Issue Type: Improvement Assignee: Unassigned Created: 2017/11/07 8:28 AM Priority: Normal Reporter: Nick Walker The Problem By default, PDB sync will try to sync all reports in the database with the other PuppetDB. Syncing all of the reports in the database is generally not valuable and syncing a smaller portion and then growing the new sync node as new reports come in would likely work great for 90% of users. In this case, you could set the sync-report-ttl to say 1d while leaving report-ttl at 14d. When setting up a new sync node you'd only sync 1d of reports and over the next 13 days the new reports coming in would bring the sync node up to the 14d of report-ttl. This also allows for sync to go down for multiple days and then come back up relatively quickly depending on how you decide to configure these settings. Having this as a configurable setting provides a release valve when you're trying to get sync working and you don't want to wait for 14 days of reports to sync. You just want sync working now and you don't care about the reports syncing all the way back in time.
Jira (PDB-3224) Add the ability to stop processing different types of commands via API
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: This would reduce the impact of performing maintenance because it would only take down the portion of the API that hits the tables that maintenance is running against. Once maintenance is complete the command queue would be able to work through it's backlog. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3747 PDB holds summary query transactions open during long syncs Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: When you reconnect a partitioned HA setup this can cause the postgresql nodes to slow to a crawl a few hours later as these long running transactions prevent maintenance.This can take hours to resolve CS Severity: 4 - Major CS Business Value: 4 - $ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8020) Add data types Nodes and Node to puppet for tasks/plans
Title: Message Title Thomas Hallgren commented on PUP-8020 Re: Add data types Nodes and Node to puppet for tasks/plans An string like 'www.example.com' does not represent a valid URI because it has not have a scheme. On the other hand, my assumption would be that the scheme is already determined (ssh or winrm). That in turn makes me wonder if the URI isn't too strict for a node representation. Do we really want to force the user to add the scheme? If not, what's the purpose of using a URI? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1781 Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 Change By: Kenn Hussey Fix Version/s: FACT 3.9.3 Fix Version/s: FACT 3.9.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken ion 5.3.3
Title: Message Title Christoph Maser commented on PUP-8126 Re: puppet module install --module_repository broken ion 5.3.3 The issue is the used in-house forge software. It returns false for response['pagination']['next'] Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8126) puppet module install --module_repository broken ion 5.3.3
Title: Message Title Christoph Maser created an issue Puppet / PUP-8126 puppet module install --module_repository broken ion 5.3.3 Issue Type: Bug Assignee: Unassigned Created: 2017/11/07 6:43 AM Priority: Normal Reporter: Christoph Maser After an upgrade to 5.3.3 puppet module install --module_repository does not work anymore as documented at https://puppet.com/docs/puppet/5.3/modules_installing.html#installing-from-another-module-repository puppet --version 5.3.2 puppet module install --module_repository http://myforge.local.lan/ puppetlabs/stdlib
Jira (PUP-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8065 puppet acceptance test server_list_setting.rb fails on AIX and Solaris Change By: Geoff Nichols Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title Geoff Nichols commented on PUP-8065 Re: puppet acceptance test server_list_setting.rb fails on AIX and Solaris PR#33 merged to libwhereami#master at https://github.com/puppetlabs/libwhereami/pull/33. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8065) puppet acceptance test server_list_setting.rb fails on AIX and Solaris
Title: Message Title Casey Williams commented on PUP-8065 Re: puppet acceptance test server_list_setting.rb fails on AIX and Solaris We merged a PR I thought would fix this before my ad-hoc build had finished yesterday afternoon, but the build failed - there's a new PR up that has actually passed ad-hoc suite tests for solaris 11 at least (AIX example pending) and works for me in a manual build on solaris 10. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8123) Upper Case in class names is not working correctly
Title: Message Title Martijn Pepping commented on PUP-8123 Re: Upper Case in class names is not working correctly Henrik Lindberg, Martin Ewings, can confirm that the issue is limited to the filename. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
