Jira (PUP-9358) Setting Windows group gid fails on second run
Title: Message Title Erick Banks updated an issue Puppet / PUP-9358 Setting Windows group gid fails on second run Change By: Erick Banks Acceptance Criteria: Report an error when the user tries to set a gid initially.Unit testCode change Story Points: 1 Team: Windows Sprint: Windows Hopper 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
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Erick Banks updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Erick Banks Story Points: 1 Sprint: Windows Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Henrik Lindberg commented on PUP-9359 Re: PUP-9294 fails to load valid 3.x function when it contains call to constant added a blocks link for now Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Erick Banks updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Erick Banks Acceptance Criteria: Patched back to 5.5.Manual testing (recommend Functional Review).Work involved: Code (change), maybe docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6429) Provide a way to install SSL certs on Windows machines
Title: Message Title Ethan Brown commented on PUP-6429 Re: Provide a way to install SSL certs on Windows machines At this time, a fully supported module for this functionality is not on our radar. That said, the CertificateDsc resource at https://github.com/PowerShell/CertificateDsc can be used in conjunction with the fully supported dsc_lite module OR an older version of the xCertificate resource is vendored into the fully supported dsc module (details at https://github.com/puppetlabs/puppetlabs-dsc/blob/1.7.0/types.md) As a result, closing this. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Josh Cooper assigned an issue to Henrik Lindberg Puppet / PUP-9359 PUP-9294 fails to load valid 3.x function when it contains call to constant Change By: Josh Cooper Assignee: Josh Cooper Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Josh Cooper commented on PUP-9359 Re: PUP-9294 fails to load valid 3.x function when it contains call to constant Since PUP-9294 was reverted, I think we should close this ticket, and address the "calling a constant" issue there. 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-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith commented on BOLT-459 Re: Reboot a target and wait for it to become available. Yes. Have a few fixes for a Z release. 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-459) Reboot a target and wait for it to become available.
Title: Message Title Dylan Ratcliffe commented on BOLT-459 Re: Reboot a target and wait for it to become available. Michael Smith The version on the forge documents a plan called reboot::wait but then go on to give an example of the reboot plan. Is this a typo? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9348) Prepare JIRA for release (Puppet Platform 6.1.0)
Title: Message Title Kenn Hussey commented on PUP-9348 Re: Prepare JIRA for release (Puppet Platform 6.1.0) Fixed in puppet-agent 6.1.0 https://tickets.puppetlabs.com/issues/?filter=32434 Fixed in Puppet Platform 6.1.0 https://tickets.puppetlabs.com/issues/?filter=32435 Introduced in puppet-agent 6.1.0 https://tickets.puppetlabs.com/issues/?filter=32436 Introduced in Puppet Platform 6.1.0 https://tickets.puppetlabs.com/issues/?filter=32437 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-1027) Bolt task show should expose how the modulepath was configured
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1027 Bolt task show should expose how the modulepath was configured Issue Type: New Feature Assignee: Unassigned Created: 2018/12/11 1:34 PM Priority: Normal Reporter: Alex Dreyer bolt task show is often used to understand why or why not a specific task is findable. As such it should expose what the module path is and how it was determined. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: Kenn Hussey Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9359 PUP-9294 fails to load valid 3.x function when it contains call to constant Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title David Mallon commented on PUP-9356 Re: `puppet device` does not load local plugins for --apply --facts and --resource cheers Kenn Hussey 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-1026) Bolt package should include hiera-eyaml
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1026 Bolt package should include hiera-eyaml Issue Type: New Feature Assignee: Unassigned Created: 2018/12/11 1:07 PM Priority: Normal Reporter: Alex Dreyer s/t Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9359 PUP-9294 fails to load valid 3.x function when it contains call to constant Change By: Henrik Lindberg Fix Version/s: PUP 6.1.0 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-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title Alex Dreyer commented on BOLT-997 Re: puppet_agent::install doesn't match on RedhatEnterpriseServer platform There is a related issue with debian. The shell task and facter task return incompatible version strings. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Henrik Lindberg assigned an issue to Josh Cooper Puppet / PUP-9359 PUP-9294 fails to load valid 3.x function when it contains call to constant Change By: Henrik Lindberg Assignee: Henrik Lindberg Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-1025) Documentation for hiera-config is missing
Title: Message Title Nick Maludy created an issue Puppet Task Runner / BOLT-1025 Documentation for hiera-config is missing Issue Type: Improvement Assignee: Unassigned Components: DOCS Created: 2018/12/11 12:54 PM Priority: Normal Reporter: Nick Maludy In the documentation for hiera in apply() blocks it mentions a config option https://puppet.com/docs/bolt/1.x/applying_manifest_blocks.html#concept-4446 However, this config option is not documented in the configuration documentation here: https://puppet.com/docs/bolt/1.x/bolt_configuration_options.html There may be other missing options, but this is the one i found first Add Comment
Jira (PUP-9359) PUP-9294 fails to load valid 3.x function when it contains call to constant
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9359 PUP-9294 fails to load valid 3.x function when it contains call to constant Issue Type: Bug Assignee: Henrik Lindberg Created: 2018/12/11 12:42 PM Fix Versions: PUP 6.0.5 Priority: Blocker Reporter: Henrik Lindberg In PUP-9294 new checking for illegal constructs in 3.x functions was introduced. Before release it was found that it crashes if the 3.x function contains a call to a constant. The one that was detected contained the following: Float(a_string) The logic added in PUP-9294 was not expecting calls to constants and would produce a "nil" function name thus crashing when validating the loaded 3.x function.
Jira (PUP-9358) Setting Windows group gid fails on second run
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-9358
Setting Windows group gid fails on second run
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/12/11 12:16 PM
Labels:
customer0
Priority:
Normal
Reporter:
Daniel Parks
Puppet Version: 6.0.2 Puppet Server Version: 2019.0.0 OS Name/Version: Windows Server 2012 R2 group { gid => 1000 } works fine when creating the group, but fails on the second run.
PS C:\Program Files\Puppet Labs> .\Puppet\bin\puppet.bat resource group foobar ensure=present gid=1000
Notice: /Group[foobar]/ensure: created
group { 'foobar':
ensure => 'present',
gid=> 'S-1-5-21-3100550808-3956625304-3008681921-1010',
Jira (PUP-9357) Noop exec debug logging should include the command
Title: Message Title
Chris Roddy updated an issue
Puppet / PUP-9357
Noop exec debug logging should include the command
Change By:
Chris Roddy
When running in noop mode, debug logging for exec resources includes e.g. the unless and onlyif commands, but it does not log the command that would be run, instead merely logging that it has not yet been run and should have been. Because an exec's command is frequently assembled using variable interpolation (and therefore can't be just read from the manifest conclusively), and because the resource will often have a custom title, users running with --noop --debug would likely benefit from seeing the command itself in debug output.There are other ways of getting this information, so it's not a big problem, but it would be a nice thing to have. {{ % /opt/puppetlabs/puppet/bin/puppet apply --noop --debug -e "exec { 'example': command => '/bin/true', unless => '/bin/false', }"--- 8< ---Info: Applying configuration version '1544556833'Debug: Exec[example](provider=posix): Executing check '/bin/false'Debug: Executing: '/bin/false'Notice: /Stage[main]/Main/Exec[example]/returns: current_value 'notrun', should be ['0'] (noop)Debug: /Stage[main]/Main/Exec[example]: The container Class[Main] will propagate my refresh eventNotice: Class[Main]: Would have triggered 'refresh' from 1 eventDebug: Class[Main]: The container Stage[main] will propagate my refresh eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventDebug: Finishing transaction 47213377716240Debug: Storing stateDebug: Pruned old state cache entries in 0.00 secondsDebug: Stored state in 0.01 secondsNotice: Applied catalog in 0.10 seconds--- 8< --- }}
Add Comment
Jira (PUP-9357) Noop exec debug logging should include the command
Title: Message Title
Chris Roddy created an issue
Puppet / PUP-9357
Noop exec debug logging should include the command
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/12/11 11:37 AM
Priority:
Normal
Reporter:
Chris Roddy
When running in noop mode, debug logging for exec resources includes e.g. the unless and onlyif commands, but it does not log the command that would be run, instead merely logging that it has not yet been run and should have been. Because an exec's command is frequently assembled using variable interpolation (and therefore can't be just read from the manifest conclusively), and because the resource will often have a custom title, users running with --noop --debug would likely benefit from seeing the command itself in debug output. There are other ways of getting this information, so it's not a big problem, but it would be a nice thing to have. ```% /opt/puppetlabs/puppet/bin/puppet apply --noop --debug -e "exec { 'example': command => '/bin/true', unless => '/bin/false', } " — 8< — Info: Applying configuration version '1544556833' Debug: Exec[example](provider=posix): Executing check '/bin/false' Debug: Executing: '/bin/false' Notice: /Stage[main]/Main/Exec[example]/returns: current_value 'notrun', should be ['0'] (noop) Debug: /Stage[main]/Main/Exec[example]: The container Class[Main] will propagate my refresh event Notice: Class[Main]: Would have triggered 'refresh' from 1 event Debug: Class[Main]: The container Stage[main] will propagate my refresh event Notice: Stage[main]: Would have triggered 'refresh' from 1 event Debug: Finishing transaction 47213377716240 Debug: Storing state Debug: Pruned old state cache entries in 0.00 seconds Debug: Stored state in 0.01 seconds Notice: Applied catalog in 0.10 seconds — 8< —
Jira (PUP-9357) Noop exec debug logging should include the command
Title: Message Title
Chris Roddy updated an issue
Puppet / PUP-9357
Noop exec debug logging should include the command
Change By:
Chris Roddy
When running in noop mode, debug logging for exec resources includes e.g. the unless and onlyif commands, but it does not log the command that would be run, instead merely logging that it has not yet been run and should have been. Because an exec's command is frequently assembled using variable interpolation (and therefore can't be just read from the manifest conclusively), and because the resource will often have a custom title, users running with --noop --debug would likely benefit from seeing the command itself in debug output.There are other ways of getting this information, so it's not a big problem, but it would be a nice thing to have. ``` {{ % /opt/puppetlabs/puppet/bin/puppet apply --noop --debug -e "exec { 'example': command => '/bin/true', unless => '/bin/false', }"--- 8< ---Info: Applying configuration version '1544556833'Debug: Exec[example](provider=posix): Executing check '/bin/false'Debug: Executing: '/bin/false'Notice: /Stage[main]/Main/Exec[example]/returns: current_value 'notrun', should be ['0'] (noop)Debug: /Stage[main]/Main/Exec[example]: The container Class[Main] will propagate my refresh eventNotice: Class[Main]: Would have triggered 'refresh' from 1 eventDebug: Class[Main]: The container Stage[main] will propagate my refresh eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventDebug: Finishing transaction 47213377716240Debug: Storing stateDebug: Pruned old state cache entries in 0.00 secondsDebug: Stored state in 0.01 secondsNotice: Applied catalog in 0.10 seconds--- 8< --- ``` }}
Add Comment
Jira (PUP-9357) Noop exec debug logging should include the command
Title: Message Title
Chris Roddy updated an issue
Puppet / PUP-9357
Noop exec debug logging should include the command
Change By:
Chris Roddy
When running in noop mode, debug logging for exec resources includes e.g. the unless and onlyif commands, but it does not log the command that would be run, instead merely logging that it has not yet been run and should have been. Because an exec's command is frequently assembled using variable interpolation (and therefore can't be just read from the manifest conclusively), and because the resource will often have a custom title, users running with --noop --debug would likely benefit from seeing the command itself in debug output.There are other ways of getting this information, so it's not a big problem, but it would be a nice thing to have.```% /opt/puppetlabs/puppet/bin/puppet apply --noop --debug -e "exec { 'example': command => '/bin/true', unless => '/bin/false', }"--- 8< ---Info: Applying configuration version '1544556833'Debug: Exec[example](provider=posix): Executing check '/bin/false'Debug: Executing: '/bin/false'Notice: /Stage[main]/Main/Exec[example]/returns: current_value 'notrun', should be ['0'] (noop)Debug: /Stage[main]/Main/Exec[example]: The container Class[Main] will propagate my refresh eventNotice: Class[Main]: Would have triggered 'refresh' from 1 eventDebug: Class[Main]: The container Stage[main] will propagate my refresh eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventDebug: Finishing transaction 47213377716240Debug: Storing stateDebug: Pruned old state cache entries in 0.00 secondsDebug: Stored state in 0.01 secondsNotice: Applied catalog in 0.10 seconds--- 8< --- ```
Add Comment
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title Kenn Hussey commented on PUP-9356 Re: `puppet device` does not load local plugins for --apply --facts and --resource David Mallon just putting the right target fix versions on this ticket, which I've just done. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: Kenn Hussey Fix Version/s: PUP 6.0.5 Fix Version/s: PUP 5.5.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: Kenn Hussey Affects Version/s: PUP 5.5.9 Affects Version/s: PUP 6.0.5 Affects Version/s: PUP 5.5.8 Affects Version/s: PUP 6.0.4 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
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Josh Cooper assigned an issue to Henrik Lindberg Puppet / PUP-9294 Raise Error when a legacy function illegally defines methods Change By: Josh Cooper Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Josh Cooper commented on PUP-9294 Re: Raise Error when a legacy function illegally defines methods We're seeing failures in PEZ. Submitted a PR to revert this. /cc Jean Bond 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-459) Reboot a target and wait for it to become available.
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Melissa Amos Labels: DOCS docs_reviewed 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-459) Reboot a target and wait for it to become available.
Title: Message Title Melissa Amos commented on BOLT-459 Re: Reboot a target and wait for it to become available. Docs update (version number TBD): http://docs-internal.puppet.com/docs/bolt/dev/bolt_new_features.html#reboot-module-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-1024) Cannot pass the result of running a task to another task.
Title: Message Title Michael Smith commented on BOLT-1024 Re: Cannot pass the result of running a task to another task. Additionally, what gets printed when you serialize a Result doesn't really reflect what and how you access the content. Makes it less discoverable. 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-608) Support local transport on windows
Title: Message Title Michael Smith commented on BOLT-608 Re: Support local transport on windows Didn't correctly set transport features for Windows (tries to run shell features on Windows, not powershell). 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-1024) Cannot pass the result of running a task to another task.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1024
Cannot pass the result of running a task to another task.
Change By:
Alex Dreyer
h4. ProblemFor reporting it's useful to pass the {{ResultSet}} from one task as an input to another. However since {{ResultSet}} is not {{Data}} this fails. h4. QuestionsShould we expose a ".to_data" method on the Bolt puppet types that users can call for this use case?Should we just handle more puppet types especially the bolt ones in {{run_task}}?h4. WorkaroundLoop over the ResultSet to grab data{noformat}$ data_result = $ result.map |$result| { { target => $result.target.name, value => $result.value } }{noformat}
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
Jira (BOLT-1024) Cannot pass the result of running a task to another task.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1024
Cannot pass the result of running a task to another task.
Change By:
Alex Dreyer
For reporting it's useful to pass the {{ResultSet}} from one task as an input to another. However since {{ResultSet}} is not {{Data}} this fails. Should we expose a ".to_data" method on the Bolt puppet types that users can call for this use case?Should we just handle more puppet types especially the bolt ones in {{run_task}}?h4. WorkaroundLoop over the ResultSet to grab data{{ noformat}} $result.map |$result| { { target => $result.target.name, value => $result.value }} {{noformat}}
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
Jira (BOLT-1024) Cannot pass the result of running a task to another task.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1024
Cannot pass the result of running a task to another task.
Change By:
Alex Dreyer
h4. ProblemFor reporting it's useful to pass the {{ResultSet}} from one task as an input to another. However since {{ResultSet}} is not {{Data}} this fails. h4. QuestionsShould we expose a ".to_data" method on the Bolt puppet types that users can call for this use case?Should we just handle more puppet types especially the bolt ones in {{run_task}}?h4. WorkaroundLoop over the ResultSet to grab data{ { noformat} } $result.map |$result| { { target => $result.target.name, value => $result.value } }{ { noformat} }
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
Jira (BOLT-1024) Cannot pass the result of running a task to another task.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1024
Cannot pass the result of running a task to another task.
Change By:
Alex Dreyer
h4. Problem For reporting it's useful to pass the {{ResultSet}} from one task as an input to another. However since {{ResultSet}} is not {{Data}} this fails. h4. Questions Should we expose a ".to_data" method on the Bolt puppet types that users can call for this use case?Should we just handle more puppet types especially the bolt ones in {{run_task}}?h4. WorkaroundLoop over the ResultSet to grab data{{noformat}}$result.map |$result| { { target => $result.target.name, value => $result.value } }{{noformat}}
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
Jira (BOLT-1006) Add top-level comidi route for bolt-server
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-1006 Add top-level comidi route for bolt-server Change By: Michael Smith Assignee: Michael Smith 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-1024) Cannot pass the result of running a task to another task.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1024
Cannot pass the result of running a task to another task.
Change By:
Alex Dreyer
For reporting it's useful to pass the {{ResultSet}} from one task as an input to another. However since {{ResultSet}} is not {{Data}} this fails. Should we expose a ".to_data" method on the Bolt puppet types that users can call for this use case?Should we just handle more puppet types especially the bolt ones in {{run_task}}? h4. WorkaroundLoop over the ResultSet to grab data{{$result.map |$result| { { target => $result.target.name, value => $result.value }}
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
Jira (BOLT-608) Support local transport on windows
Title: Message Title Michael Smith assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-608 Support local transport on windows Change By: Michael Smith Assignee: Michael Smith Cas Donoghue 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-1024) Cannot pass the result of running a task to another task.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1024 Cannot pass the result of running a task to another task. Issue Type: New Feature Assignee: Unassigned Created: 2018/12/11 10:32 AM Priority: Normal Reporter: Alex Dreyer For reporting it's useful to pass the ResultSet from one task as an input to another. However since ResultSet is not Data this fails. Should we expose a ".to_data" method on the Bolt puppet types that users can call for this use case? Should we just handle more puppet types especially the bolt ones in run_task? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-969) bolt-server clears its tmpdir during cache purging
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-969 bolt-server clears its tmpdir during cache purging Change By: Cas Donoghue Release Notes Summary: When `pe-bolt-server` purges the task cache directory the temporary location where task downloads are staged is preserved. Previously the staging directory was deleted as part of the purge which resulted in task download errors. 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 (PDB-4215) Switch pdb-version back to reading version file
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4215 Switch pdb-version back to reading version file Issue Type: Bug Assignee: Unassigned Created: 2018/12/11 10:20 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PUP-9255) PAL - add the ability to evaluate logic in a nested local scope
Title: Message Title Henrik Lindberg commented on PUP-9255 Re: PAL - add the ability to evaluate logic in a nested local scope This is all Ruby API, a user would need to read the documentation in the source for the PAL classes. Here is an example where it is used - inside the eval function: https://github.com/puppetlabs/puppet/blob/d0b3a7fb1e4f531747b31f439df308b30534a65a/lib/puppet/functions/eval.rb#L45 I blogged about PAL (https://puppet-on-the-edge.blogspot.com/2018/10/puppet-pal-wants-to-be-your-friend.html) , and will add the in_local_scope thing to it when the PR is merged. There is no hurry to document PAL since I think there are quite a number of things to add to it to make it feature complete - for now it serves its purpose (mainly) for Bolt and as an API we use internally. 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-608) Support local transport on windows
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-608 Support local transport on windows Change By: Michael Smith Assignee: Cas Donoghue Michael Smith 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
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases Change By: Michael Smith Labels: beginner help_wanted 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
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases Change By: Michael Smith Labels: help_wanted 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
Title: Message Title Michael Smith commented on BOLT-1022 Re: Allow for hyphens in aliases I think we can update both aliases and group names to allow 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-1022) Allow for hyphens in aliases
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1022 Allow for hyphens in aliases Change By: Michael Smith 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-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Michael Smith Release Notes Summary: Bolt now ships with the reboot module to provide a reboot plan that reboots targets and waits for them to become available. 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-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith commented on BOLT-459 Re: Reboot a target and wait for it to become available. Yeah, everything needed is in the plan README. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9254) Agent Functions - add eval() function
Title: Message Title Eric Thompson updated an issue Puppet / PUP-9254 Agent Functions - add eval() function Change By: Eric Thompson Fix Version/s: PUP 6.1.0 Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9254) Agent Functions - add eval() function
Title: Message Title Henrik Lindberg commented on PUP-9254 Re: Agent Functions - add eval() function Jean Bond sure thing... will write that 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-943) Target object should have clear, documented API
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-943
Target object should have clear, documented API
Change By:
Alex Dreyer
Currently the data type {{Target}} accepts a URI, and an options hash. What works in that options hash is undocumented. I've primarily gotten extra options {{ssl}} and {{host-key-check}} to work, but others I wanted to use didn't:- user- password- protocol- portWe should make these work as additional options (and document them).Notes/QuestionsAre all nodes that get mentioned part of the "all" group. Hyp: no, nodes not added are not part of the group.Targets are singletons by their name.How should update functions handle a target spec/string/array of targets? It should accept an array of targets(Later work). add notes to ticket.Problems with options: - options set on a Target instance are not saved on the singleton- get_targets is the only way to get targets Target.new is deprecated- get_target is new function to get a single target.- support set config/options function for a target will set same config schema as inventoryThere is no way to override values in the uri. That is out of scope.WORK:- allow config in inventory to be updated with puppet functions like vars and facts.- add new get_target function that will get a single target or error.- deprecate creating target objects without get_targets. - Targets should always have a reference back to the inventory.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4214) --data-urlencode 'pretty=true' does not work
Title: Message Title
Austin Blatt commented on PDB-4214
Re: --data-urlencode 'pretty=true' does not work
The error you're seeing is because it is getting the wrong Content-Type header, so you should set that with the curl argument -H 'Content-Type:application/json'. After that there's at least something wrong with our docs (and maybe PuppetDB), I had to change the --data-urlencode 'pretty=true' argument to its json form. So I believe the following query will work for you
[puppet]$ curl -X POST https://puppetdb.example.com:8081/pdb/query/v4/nodes \
--tlsv1 \
--cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem \
--cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem \
--key /etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem \
-H 'Content-Type:application/json' \
-d '{"pretty":true}'
Add Comment
Jira (BOLT-943) Target object should have clear, documented API
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-943
Target object should have clear, documented API
Change By:
Alex Dreyer
Currently the data type {{Target}} accepts a URI, and an options hash. What works in that options hash is undocumented. I've primarily gotten extra options {{ssl}} and {{host-key-check}} to work, but others I wanted to use didn't:- user- password- protocol- portWe should make these work as additional options (and document them).Notes/QuestionsAre all nodes that get mentioned part of the "all" group. Hyp: no, nodes not added are not part of the group.Targets are singletons by their name.How should update functions handle a target spec/string/array of targets? It should accept an array of targets(Later work). add notes to ticket.Problems with options: - options set on a Target instance are not saved on the singleton- get_targets is the only way to get targets Target.new is deprecated- get_target is new function to get a single target.- support set config/options function for a target will set same config schema as inventoryThere is no way to override values in the uri. That is out of scope. WORK:- allow config in inventory to be updated with puppet functions like vars and facts.- add new get_target function that will get a single target or error.- deprecate creating target objects without get_targets.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-943) Target object should have clear, documented API
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-943
Target object should have clear, documented API
Change By:
Alex Dreyer
Currently the data type {{Target}} accepts a URI, and an options hash. What works in that options hash is undocumented. I've primarily gotten extra options {{ssl}} and {{host-key-check}} to work, but others I wanted to use didn't:- user- password- protocol- portWe should make these work as additional options (and document them).Notes/QuestionsAre all nodes that get mentioned part of the "all" group. Hyp: no, nodes not added are not part of the group.Targets are singletons by their name.How should update functions handle a target spec/string/array of targets? It should accept an array of targets(Later work). add notes to ticket. Problems with options: - options set on a Target instance are not saved on the singleton- get_targets is the only way to get targets Target.new is deprecated- get_target is new function to get a single target. - support set config/options function for a target will set same config schema as inventoryThere is no way to override values in the uri. That is out of scope.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-943) Target object should have clear, documented API
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-943
Target object should have clear, documented API
Change By:
Alex Dreyer
Currently the data type {{Target}} accepts a URI, and an options hash. What works in that options hash is undocumented. I've primarily gotten extra options {{ssl}} and {{host-key-check}} to work, but others I wanted to use didn't:- user- password- protocol- portWe should make these work as additional options (and document them). Notes/QuestionsAre all nodes that get mentioned part of the "all" group. Hyp: no, nodes not added are not part of the group.Targets are singletons by their name.How should update functions handle a target spec/string/array of targets? It should accept an array of targets(Later work).Problems with options: - options set on a Target instance are not saved on the singleton- get_targets is the only way to get targets Target.new is deprecated- get_target is new function to get a single target.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9311) Document auth_membership as being Solaris specific
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9311 Document auth_membership as being Solaris specific This affects the autogenerated type reference, but I don't think it needs release notes. Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) Document auth_membership as being Solaris specific
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9311 Document auth_membership as being Solaris specific Change By: Josh Cooper Summary: User resource doesn't remove user from windows group Document auth_membership as being Solaris specific Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9311 User resource doesn't remove user from windows group Change By: Josh Cooper Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9311) User resource doesn't remove user from windows group
Title: Message Title Josh Cooper commented on PUP-9311 Re: User resource doesn't remove user from windows group Merged to master in https://github.com/puppetlabs/puppet/commit/a8d4984c2cfc8c0974afafa5be77d4c688c6a883 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2
Title: Message Title Rick Sherman commented on PUP-9047 Re: puppet device --apply fails to apply catalog to unregistered targets pt. 2 David Schmitt Possibly. I hit it again in 6.0.4, but not sure what fixes were merged up from 5.5.4+ to 6.0.x Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2
Title: Message Title David Schmitt commented on PUP-9047 Re: puppet device --apply fails to apply catalog to unregistered targets pt. 2 In https://github.com/puppetlabs/puppet-resource_api/pull/145 I've removed the workaround in the Resource API tests for this issue, and in the travis run only 5.5.3 failed, so maybe this has been fixed in 5.5.4? 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-1021) python_task_helper still appears to succeed when encountering an error
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1021 python_task_helper still appears to succeed when encountering an error Change By: Melissa Amos Labels: DOCS docs_reviewed 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-1018) Docker transport does not implement connected?
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1018 Docker transport does not implement connected? Change By: Melissa Amos Labels: DOCS docs_reviewed 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-459) Reboot a target and wait for it to become available.
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Melissa Amos Labels: 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-1021) python_task_helper still appears to succeed when encountering an error
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1021 python_task_helper still appears to succeed when encountering an error Change By: Melissa Amos Labels: docs_reviewed 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-1021) python_task_helper still appears to succeed when encountering an error
Title: Message Title Melissa Amos commented on BOLT-1021 Re: python_task_helper still appears to succeed when encountering an error Docs update (version number TBD): http://docs-internal.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#python-task-helper-didn-t-generate-appropriate-errors 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-1018) Docker transport does not implement connected?
Title: Message Title Melissa Amos commented on BOLT-1018 Re: Docker transport does not implement connected? Docs update (version number TBD): http://docs-internal.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#wait-until-available-function-didn-t-work-with-docker-transport 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 Melissa Amos updated an issue Puppet Task Runner / BOLT-815 Mark bolt_shim file content arguments as sensitive Change By: Melissa Amos Labels: DOCS docs_reviewed 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 Melissa Amos commented on BOLT-815 Re: Mark bolt_shim file content arguments as sensitive Docs update: http://docs-internal.puppet.com/docs/bolt/dev/bolt_new_features.html#bolt-shim-module-contents-marked-as-sensitive 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-459) Reboot a target and wait for it to become available.
Title: Message Title Melissa Amos commented on BOLT-459 Re: Reboot a target and wait for it to become available. Please provide a release note summary. Also, I don't see any pre-docs changes for this; is all relevant documentation in the plan readme? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title David Mallon commented on PUP-9356 Re: `puppet device` does not load local plugins for --apply --facts and --resource Kenn Hussey/Kenn Hussey - this is one we will want to get in to the upcoming puppet release - the PR will be merged before EOD Wednesday. Is there anything else we need to do to make sure it is folded into that release? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title David Schmitt updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: David Schmitt The changes in PUP-8766 (https://github.com/puppetlabs/puppet/pull/7242) removed plugin loading from a local environment for `puppet device`, even in the cases where local content is supposed to be used. The issue was detected in Resource API acceptance testing yesterday after the merge-up from 5.5.x to 6.0.x. The fix should be trivially mergeable to 6.0.x and beyond. 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
Jira (PUP-9356) {brief summary of issue}
Title: Message Title
David Schmitt created an issue
Puppet / PUP-9356
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 5.5.9, PUP 6.0.5
Assignee:
David Schmitt
Created:
2018/12/11 3:22 AM
Priority:
Blocker
Reporter:
David Schmitt
The changes in PUP-8766 (https://github.com/puppetlabs/puppet/pull/7242) removed plugin loading from a local environment for `puppet device`, even in the cases where local content is supposed to be used.
Add Comment
This message was sent by Atlassian
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title David Schmitt updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: David Schmitt Team: Network Automation Method Found: Needs Assessment Automated Test 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.
