Jira (FACT-1864) Facter tests fail with new amazon7 image ami-31394949
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Facter / FACT-1864 Facter tests fail with new amazon7 image ami-31394949 Change By: Josh Cooper Assignee: Branan Riley 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 (FACT-1864) Facter tests fail with new amazon7 image ami-31394949
Title: Message Title Josh Cooper assigned an issue to Unassigned Facter / FACT-1864 Facter tests fail with new amazon7 image ami-31394949 Change By: Josh Cooper Assignee: 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 (PUP-8569) Extract host type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8569 Extract host type/provider into a module Change By: Josh Cooper Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8569) Extract host type/provider into a module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8569 Extract host type/provider into a module Change By: Josh Cooper Assignee: 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 (PUP-8989) puppet apply with --reporturl uses wrong HTTP method POST
Title: Message Title Jesse Reynolds assigned an issue to Jesse Reynolds Closing this as this is presumed-expected behaviour. Puppet master cannot accept a report from puppet apply using the 'http' built-in report processor. Puppet / PUP-8989 puppet apply with --reporturl uses wrong HTTP method POST Change By: Jesse Reynolds Resolution: Won't Do Assignee: Jesse Reynolds Status: Open Closed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Josh Cooper commented on PUP-7407 Re: Add deprecation warning to Puppet::Util.absolute_path? merged to puppet#master in https://github.com/puppetlabs/puppet/commit/ee7cf4d28077be7d1bdbbe934ea012d41d33deff 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-8786) Package module into puppet-agent
Title: Message Title Josh Cooper commented on PUP-8786 Re: Package module into puppet-agent Merged to puppet-agent#master in https://github.com/puppetlabs/puppet-agent/commit/46d02099dd6a669bfeb74cfee9f5daed16f515f1 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-8988) Don't pluginsync vendored modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8988 Don't pluginsync vendored modules Change By: Josh Cooper Currently in puppet#master, we treat vendored modules just like any another module in the environment-specific modulepath, just that they have the least preference.This is desirable to ensure that the version of the type we're compiling for, is the same version that the agent uses during catalog application. This is important to ensure the code in the type (title patterns, munge, validate, auto relations) is consistent to prevent subtle and difficult to reproduce bugs. It would also prevent problems like PUP-2746.However, it causes a few problems: * it will cause additional pluginsync'ing of types and providers * we have to be careful about introducing changes to types that are not compatible with older agents. For example, the yumrepo type now marks the {{password}} and {{proxy_password}} properties as sensitive, but the {{Puppet::Parameter#sensitive}} method is not available in older puppet versions. * it is a departure from how puppet currently worksThis ticket proposes we: * remove the vendored modules from the module path so that they are not pluginsync'ed automatically * add a puppet setting for vendored modulepath * add the path to the autoloader search path with least precedenceThis way vendored types can be autoloaded locally, but we never pluginsync (types/providers/facts/files/etc) from them./cc [~ericsorenson], [~jacob.helwig], [~melissa], [~branan] Add Comment This message was
Jira (PUP-8988) Don't pluginsync vendored modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8988 Don't pluginsync vendored modules Change By: Josh Cooper Currently in puppet#master, we treat vendored modules just like any another module in the environment-specific modulepath, just that they have the least preference.This is desirable to ensure that the version of the type we're compiling for, is the same version that the agent uses during catalog application. This is important to ensure the code in the type (title patterns, munge, validate, auto relations) is consistent to prevent subtle and difficult to reproduce bugs. It would also prevent problems like PUP-2746.However, it causes a few problems: * it will cause additional pluginsync'ing of types and providers * we have to be careful about introducing changes to types that are not compatible with older agents. For example, the yumrepo type now marks the {{password}} and {{proxy_password}} properties as sensitive, but the {{Puppet::Parameter#sensitive}} method is not available in older puppet versions. * it is a departure from how puppet currently worksThis ticket proposes we: * remove the vendored modules from the module path so that they are not pluginsync'ed automatically * add a puppet setting for vendored modulepath * add the path to the autoloader search path with least precedenceThis way vendored types can be autoloaded locally, but we never pluginsync (types/providers/facts/files/etc) from them./cc [~ericsorenson], [~jacob.helwig], [~melissa], [~branan] Add Comment This message was
Jira (PUP-8711) Implement Agent Functions to support secret lookups at catalog application time
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8711 Implement Agent Functions to support secret lookups at catalog application time Change By: Maggie Dreyer Epic Name: Secret Squirrels Agent Functions 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-8988) Don't pluginsync vendored modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8988 Don't pluginsync vendored modules Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8784) Create the CI pipeline
Title: Message Title Josh Cooper commented on PUP-8784 Re: Create the CI pipeline Thanks for the reminder! Created the jobs. 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-673) Pass trusted facts
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-673 Pass trusted facts Change By: Lucy Wyman Assignee: Lucy Wyman 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-672) Pass vars from plan scope at higher precedence
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-672 Pass vars from plan scope at higher precedence Change By: Lucy Wyman Assignee: Lucy Wyman 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-8784) Create the CI pipeline
Title: Message Title Melissa Stone commented on PUP-8784 Re: Create the CI pipeline Merged at https://github.com/puppetlabs/ci-job-configs/commit/738f08006bae49151095ff85f16c885965c0fca4 Josh, I'm leaving this open as a reminder to create the views in jenkins 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-647) Support _noop for apply statements
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-647 Support _noop for apply statements Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-677) Bolt does not serialize complex types as JSON with environment input method
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-677 Bolt does not serialize complex types as JSON with environment input method Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-634) Integration tests for apply functionality
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog 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 (FACT-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.
Title: Message Title Branan Riley assigned an issue to Branan Riley Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Change By: Branan Riley Assignee: Branan Riley 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-8615) sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8615 sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice Change By: Thomas Hallgren Fix Version/s: PUP 5.5.3 Fix Version/s: PUP 5.5.z 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-8606) Module-defined data types are very verbose when displayed
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8606 Module-defined data types are very verbose when displayed Change By: Thomas Hallgren Fix Version/s: PUP 5.5.3 Fix Version/s: PUP 5.5.z 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-8306) Mechanism for syncing local git changes to remote testing host
Title: Message Title Rob Braden updated an issue Puppet / PUP-8306 Mechanism for syncing local git changes to remote testing host Change By: Rob Braden Fix Version/s: PUP 4.10.z Fix Version/s: PUP 5.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-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Rob Braden updated an issue Puppet / PUP-4543 Document how to run AIO puppet acceptance in acceptance_tests.md Change By: Rob Braden Fix Version/s: PUP 5.5.3 Fix Version/s: PUP 5.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-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Rob Braden updated an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages Change By: Rob Braden Fix Version/s: PUP 6.y Fix Version/s: PUP 5.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-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Henrik Lindberg commented on PUP-8969 Re: Sensitive parameters are not redacted from reports / agent output when used in templates In order to support something like this, we need a new data type and rich-data turned on. We cannot send the result of the template directly to the catalog since we only have a choice of sensitive or not for the entire value. The new SensitiveSegments data type will essentially contain an Array of String mixed with instances of Sensitive. A to_s on an SensitiveSegments will render each with to_s and get redacted for all sensitive segments. An unwrap on a SensitiveSegments would unwrap and join all elements. In addition to this, the resource logic needs to be able to handle SensitiveSegments data values and do the right operation unwrap or to_s depending on what it is doing (just like it does today by checking the binary sensitive flag), but it is more difficult as the value cannot just be unwrapped and used, the actual SensitiveSegment instance must be used to keep track of the parts of the string which should be redacted. Further, there must be new features for EPP to allow it to use Sensitive values in the text. It will then produce an instance of SensitiveSegments instead of an instance of String. Doing the same for ERB would be very difficult. It could probable do this when seeing <%= Sensitive('secret') %> - i.e. that all interpolated expressions that evaluate to Sensitive makes it evaluate to the internal array of a SensitiveSegment instead of a String. Another approach would be to make the File resource have features to combine a template with late binding values and know how to deal with both sensitive and encrypted information. It would expand the template on the agent side and now that it should use "redacted" or similar for sensitive/encrypted replacements. The work on Deferred / agent-side-function would help with that. Also complex to achieve. All together this is a substantial amount of work. Ping Eric Sorenson for help with prio. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8988) Don't pluginsync vendored modules
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8988 Don't pluginsync vendored modules Change By: Josh Cooper Assignee: 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 (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Erik Hansen Issue Type: Bug Improvement 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-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen assigned an issue to Unassigned Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Erik Hansen Assignee: Erik Hansen 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-672) Pass vars from plan scope at higher precedence
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-672 Pass vars from plan scope at higher precedence 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-673) Pass trusted facts
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-673 Pass trusted facts 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-673) Pass trusted facts
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-673 Pass trusted facts 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 (PUP-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Kenn Hussey commented on PUP-8305 Re: Git testing should consume the runtime archive rather than install system packages Thanks, Melissa Stone, I removed the flag. Does this issue (as well as PUP-8306) really block PUP-4543 (or should it perhaps be retargeted as well)? 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-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages 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-8776) Extract the code & verify the module
Title: Message Title Josh Cooper commented on PUP-8776 Re: Extract the code & verify the module passed CI in puppet#f0ef0a2409 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-8577) Extract selinux type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8577 Extract selinux type/provider into a module Change By: Josh Cooper Release Notes Summary: The selboolean and selmodule types and providers have been moved to a module: https://forge.puppet.com/puppetlabs/selinux_core, and it is repackaged into puppet-agent 6.0 Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8577) Extract selinux type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8577 Extract selinux type/provider into a module Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8801) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8801 Re: Remove type/provider code from puppet passed CI in puppet#f0ef0a2409 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-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages Change By: Melissa Stone Fix Version/s: PUP 4.10.z 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-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Melissa Stone commented on PUP-8305 Re: Git testing should consume the runtime archive rather than install system packages This work isn't tied to a specific release and should not be a release blocker at all. It's isolated to testing changes. Should I remove the impediment flag? I've also been doing this work with the master branch, rather than anything earlier, so I'll change the fix version accordingly 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-8567) Extract augeas type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8567 Extract augeas type/provider into a module Change By: Josh Cooper Release Notes Summary: The augeas feature, type and provider has been moved to the a module: https://forge.puppet.com/puppetlabs/augeas_core. It is also repackaged in puppet-agent. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8808) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8808 Re: Remove type/provider code from puppet Passed CI in puppet#f0ef0a240975c04cb6e72e28b62c6f7cea71a547 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-8567) Extract augeas type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8567 Extract augeas type/provider into a module Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8573) Extract macdslocal type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8573 Extract macdslocal type/provider into a module Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8573) Extract macdslocal type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8573 Extract macdslocal type/provider into a module Change By: Josh Cooper Release Notes Summary: The computer, macauthorization, and mcx types and providers have been moved to a module: https://forge.puppet.com/puppetlabs/macdslocal_core. It is not being repackaged into puppet-agent for 6.0 Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existent parameter
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existent parameter Change By: Cas Donoghue Release Notes Summary: The PowerShell standard argument handling will only be used for wrapper that prepares arguments effectively ignores any parameters explicitly declared that are specified in PowerShell tasks when input_method is set to powershell the metadata but not in the script . 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-630) PowerShell based tasks throw an error about a non-existent parameter
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existent parameter Change By: Cas Donoghue Summary: PowerShell based tasks throw an error about a non- existant existent parameter 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-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8747 Virtual Collector overrides fail with in 5.x 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-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8747 Virtual Collector overrides fail with in 5.x Change By: Henrik Lindberg Fix Version/s: PUP 5.5.3 Fix Version/s: PUP 5.5.z 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-632) Scope for bolt_compile should be set up
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up 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-672) Pass vars from plan scope at higher precedence
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-672 Pass vars from plan scope at higher precedence 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 (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Casey Williams assigned an issue to Casey Williams Facter / FACT-1865 Amazon Linux 2 is reported as 4 Change By: Casey Williams Assignee: Casey Williams 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-8943) Selmodule thinks foo exists if myfoo is loaded
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8943 Selmodule thinks foo exists if myfoo is loaded Change By: Jacob Helwig Release Notes Summary: The selmodule type is now more strict about checking if a module has already been loaded, and should no longer consider modules such as "bar" and "foobar" to be the same module. 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 (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Ethan Brown commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Given the above resolutions, going to close this as well as PUP-266 as won't fix, since we have alternative means of getting the desired behavior. Furthermore, we don't want any changes as a result of this work to unset the perms laid by down the installer for PA-2019. The only question that remains is what to do for gem workflows running as Administrator? We may have to do something under those circumstances if the directories haven't previously been touched? 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-8606) Module-defined data types are very verbose when displayed
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8606 Module-defined data types are very verbose when displayed 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-8615) sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8615 sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice 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-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8747 Virtual Collector overrides fail with in 5.x 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 (FACT-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. 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-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages 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 (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1865 Amazon Linux 2 is reported as 4 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-8699) puppet device application should support outputting facts
Title: Message Title Kenn Hussey commented on PUP-8699 Re: puppet device application should support outputting facts Thomas Honey please provide release notes for this issue, if needed. Thanks! 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-8943) Selmodule thinks foo exists if myfoo is loaded
Title: Message Title Kenn Hussey commented on PUP-8943 Re: Selmodule thinks foo exists if myfoo is loaded Jacob Helwig please provide release notes for this issue, if needed. Thanks! 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-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Kenn Hussey commented on PUP-8585 Re: puppet device --resource should fail if non-existent target is given Thomas Honey please provide release notes for this issue, if needed. Thanks! 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-8989) puppet apply with --reporturl uses wrong HTTP method POST
Title: Message Title Jesse Reynolds updated an issue Puppet / PUP-8989 puppet apply with --reporturl uses wrong HTTP method POST Change By: Jesse Reynolds *Puppet Version:* 5.5.2*Puppet Server Version:* 5.5.2*OS Name/Version:* CentOS 7.2puppet master accepts reports from agent runs using the PUT method however `puppet apply` uses the POST method which yields a 404 from the puppet master. Steps to reproduce:- PE Monolithic Master installed with 2018.1.2 certname: master.example- Agent running with the same version (ie puppet 5.5.2) certname: agent1.example- Create an empty file b.pp on the Agent (or include a simple resource)- Perform an agent run overriding the reporturl as follows:puppet agent --test --http_debug --reports store,http --reporturl 'https://master.example:8140/puppet/v3/report/agent1.example?environment=production&'- Perform an apply run setting reports to store,http and setting reporturl as follows:puppet apply --http_debug --reports store,http --reporturl 'https://master.example:8140/puppet/v3/report/agent1.example?environment=production&' b.pp*Desired Behavior:* Both the agent and The apply runs run should submit the resulting report to the master for processing successfully .*Actual Behavior:* Only the agent run is able to submit the report to the master for processing. The apply run yields a 404 error from puppetserver. The agent run uses PUT to submit the report, which includes the URL query string however the apply run uses POST which shortens the URL to /agent: PUT /puppet/v3/report/agent1.example?environment=production& HTTP/1.1apply:POST /puppet/v3/report/agent1.example HTTP/1.1 So, it looks as though 'puppet apply' is using an unexpected HTTP method to submit the report to the puppet master. Add Comment
Jira (PUP-8989) puppet apply with --reporturl uses wrong HTTP method POST
Title: Message Title Jesse Reynolds created an issue Puppet / PUP-8989 puppet apply with --reporturl uses wrong HTTP method POST Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Components: Platform Created: 2018/07/09 2:18 AM Priority: Normal Reporter: Jesse Reynolds Puppet Version: 5.5.2 Puppet Server Version: 5.5.2 OS Name/Version: CentOS 7.2 puppet master accepts reports from agent runs using the PUT method however `puppet apply` uses the POST method which yields a 404 from the puppet master. Steps to reproduce: PE Monolithic Master installed with 2018.1.2 certname: master.example Agent running with the same version (ie puppet 5.5.2) certname: agent1.example Create an empty file b.pp on the Agent (or include a simple resource) Perform an agent run overriding the reporturl as follows: puppet agent --test --http_debug --reports store,http --reporturl 'https://master.example:8140/puppet/v3/report/agent1.example?environment=production&' Perform an apply run setting reports to store,http and setting reporturl as follows: puppet apply --http_debug --reports store,http --reporturl 'https://master.example:8140/puppet/v3/report/agent1.example?environment=production&' b.pp Desired Behavior: Both the agent and apply runs should