Jira (PUP-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title Josh Cooper commented on PUP-7302 Re: Puppet HTTP Node API: make fact_merge optional Are you sure that that patch addresses what's described on this ticket? Yep, we are modifying puppet so that the compile master always uses the facts that the agent submitted with the catalog request, since those are the "correct" facts for that point in time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7618) PSON -> JSON Testing
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7618
PSON -> JSON Testing
Change By:
Josh Cooper
In Puppet 5 we will be switching from using PSON by default to JSON. This requires that various interactions are validated to work as we expect them to. Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]{code}Agent <- Server <- Database node info catalog file meta data Agent -> Server -> Database facts facts reports catalogreports v5 v5 v5A: json (covered in CI)B: fallback to pson catalog only (with binary data) (needs beaker testing)C: --preferred serialization format=pson on Agent (needs beaker testing)F: cahched cached cat -> Always send json with escaped characters (needs beaker testing) v3/4 v5 v5D: pson ( leavrage PR covered in PE upgrade testing ? )F: cahched cached cat -> Always send json with escaped characters Manualv5 v4 v4E: pson (expected graceful failure early) F: cahched cached cat -> Always send json with escaped characters (ka-boom!! Acceptable?){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7617) Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7617 Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml Change By: Josh Cooper Fix Version/s: PUP 4.10.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7618) PSON -> JSON Testing
Title: Message Title Stan Duffy created an issue Puppet / PUP-7618 PSON -> JSON Testing Issue Type: Task Assignee: Stan Duffy Created: 2017/06/02 3:02 PM Environment: Puppet Agent 5 Priority: Normal Reporter: Stan Duffy In Puppet 5 we will be switching from using PSON by default to JSON. This requires that various interactions are validated to work as we expect them to. Here are the rough notes put together but John Duarte and myself based on a meeting we had with Josh Cooper Agent <- Server <- Database node info catalog
Jira (PUP-7617) Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7617 Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7617) Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7617 Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml Change By: Maggie Dreyer Sprint: Agent Triage 2017-06-14 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7617) Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7617 Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml Change By: Maggie Dreyer Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax What do you think we should do in the case where an auth rule doesn't have any allow or deny directives? I went ahead and worked up an implementation which treats the absence of any security directives as though allow * were implicitly specified. I was thinking that through the PR discussion, we can hack through whether we think that's the right approach or not. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7617) Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml
Title: Message Title Adam Bottchen created an issue Puppet / PUP-7617 Leftover /opt/puppet contents cause upgrades to fail on locale/config.yaml Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/06/02 2:25 PM Labels: maintenance triage Priority: Normal Reporter: Adam Bottchen If there happens to be any leftover files from older PE installations, it will cause the PE 2017.2.1 installation to fail because Puppet will end up pulling the wrong locale path: 2017-05-29 14:42:51,320 Running command: /opt/puppetlabs/puppet/bin/puppet infrastructure configure --detailed-exitcodes --modulepath /opt/puppetlabs/server/data/enterprise/modules
Jira (PUP-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7616 Fix broken implementation of Property#change_to_s method Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/06/02 2:23 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Thomas Hallgren The method Puppet::Property#change_to_s, which is used when constructing the message of an event, is broken. It calls the methods #is_to_s and #should_to_s to convert values to their string form and then calls #format_value_for_display to convert that string again. Sometimes this almost works since the default implementation of the method #is_to_s just returns it's argument untouched (the documentation states that it produces a "pretty printing string", but it doesn't) so that two wrongs ends up as one right. The default for #should_to_s will however always convert its argument using default ruby string conversion (it converts to an array and joins with space). This should be fixed so that the #change_to_s just calls #is_to_s and #should_to_s and the default implementation them then calls #format_value_for_display.
Jira (PDB-3545) Add report_id join condition to latest-report-query
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3545 Add report_id join condition to latest-report-query Change By: Russell Mull Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3545) Add report_id join condition to latest-report-query
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3545 Add report_id join condition to latest-report-query Issue Type: Bug Assignee: Unassigned Created: 2017/06/02 1:05 PM Fix Versions: PDB 4.2.3.4, PDB 4.4.1, PDB 5.0.0 Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You
Jira (PUP-3940) Puppet requests should include "real" MIME types
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3940 Puppet requests should include "real" MIME types Change By: Josh Cooper Component/s: Networking Services Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3940) Puppet requests should include "real" MIME types
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3940 Puppet requests should include "real" MIME types Change By: Josh Cooper Release Notes Summary: Puppet will now send proper MIME content types, e.g. application/json, instead of format names, e.g. json, in its Accept header when making HTTP requests. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3940) Puppet requests should include "real" MIME types
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3940 Puppet requests should include "real" MIME types Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1588) Building with openssl 1.1.0 fails
Title: Message Title Michael Smith commented on FACT-1588 Re: Building with openssl 1.1.0 fails This might be as simple as making the scoped_bio constructor take a const value. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7608) Lookup unique merge doesn't deduplicate with a single layer
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-7608 Lookup unique merge doesn't deduplicate with a single layer Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title Eric Delaney updated an issue Puppet / PUP-5479 segfault with augeas type when changes attribute is too long Change By: Eric Delaney QA Risk Assessment Reason: real problem fixed and tested in Augeas code QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3529) Report insertion should determine the latest_report_id without recalculating the latest report from the reports table
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3529 Report insertion should determine the latest_report_id without recalculating the latest report from the reports table Change By: Nick Walker Affects Version/s: PDB 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1646) Update Add tests and TestRail ID's for specific facts tests
Title: Message Title Eric Delaney updated an issue Facter / FACT-1646 Update Add tests and TestRail ID's for specific facts tests Change By: Eric Delaney QA Risk Assessment Reason: Updating and adding tests QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3544) Fact Updating appears slower with Fact Reduplication
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3544 Fact Updating appears slower with Fact Reduplication Change By: Nick Walker Summary: Fact Updating is appears slower with Fact Reduplication Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7579) Tags do not support UTF-8 characters
Title: Message Title Josh Cooper commented on PUP-7579 Re: Tags do not support UTF-8 characters Ethan Brown We also need to update the API docs in https://github.com/puppetlabs/puppet/blob/master/api/schemas/catalog.json#L7-L14 and https://github.com/puppetlabs/puppet/blob/master/api/schemas/catalog.json#L61-L68 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7615) puppet command leaks module command issues.
Title: Message Title Henrik Lindberg assigned an issue to Adam Buxton Puppet / PUP-7615 puppet command leaks module command issues. Change By: Henrik Lindberg Assignee: Adam Buxton Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7615) puppet command leaks module command issues.
Title: Message Title Henrik Lindberg commented on PUP-7615 Re: puppet command leaks module command issues. The report is a bit cryptic, but I am taking a guess at what is going on here: When puppet runs, it looks for the application to run (for example "puppet facts"), in order to search it needs an environment to search in (by default "production"), since it is possible to ship applications in modules on the module path puppet loads the modules on the environment's module path. When doing so, it needs to understand things about the modules and it is therefore loading metadata.json. Some of the modules seem to have faulty metadata.json. Cause of action here: fix the broken modules (recommended) do not have those modules in the default environment (production) run commands in a different environment Adam Buxton - a couple of questions: what is it you are expecting someone to fix? which version of Puppet is this for? Have the issues with faulty metadata.json been brought to the attention of the maintainers of the respective module? anything that I misunderstood ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3525) Ensure pe-puppetdb-extensions is triggered on travis for every puppetdb change
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3525 Ensure pe-puppetdb-extensions is triggered on travis for every puppetdb change Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title Nacho Barrientos commented on PUP-7302 Re: Puppet HTTP Node API: make fact_merge optional Hi Josh Cooper. Are you sure that that patch addresses what's described on this ticket? I have not read the patch itself, but the description of the MR does not seem to cover this issue. Will that patch prevent puppetserver from requesting facts from PDB when a request to /node is done? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7174) Add a 'call' function to Puppet built-in functions
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7174 Add a 'call' function to Puppet built-in functions Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7174) Add a 'call' function to Puppet built-in functions
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7174
Add a 'call' function to Puppet built-in functions
Change By:
Henrik Lindberg
Story Points:
1
Release Notes Summary:
The function {{call(name, args...)}} has been added to allow calling a function by name.
Sprint:
Agent 2017-06-14
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7174) Add a 'call' function to Puppet built-in functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7174 Add a 'call' function to Puppet built-in functions Change By: Henrik Lindberg Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7174) Add a 'call' function to Puppet built-in functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7174 Add a 'call' function to Puppet built-in functions Change By: Henrik Lindberg Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7174) Add a 'call' function to Puppet built-in functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7174 Add a 'call' function to Puppet built-in functions Change By: Henrik Lindberg Component/s: Functions Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7608) Lookup unique merge doesn't deduplicate with a single layer
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7608
Lookup unique merge doesn't deduplicate with a single layer
Change By:
Henrik Lindberg
Release Notes Summary:
When performing a lookup with merge strategy {{unique}} on an array value, the array could contain end up containing duplicates if it was never merged with another array during the lookup. This is now changed so that the result for a lookup with {{unique}} merge always results in a unique set of values.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7615) puppet command leaks module command issues.
Title: Message Title
Adam Buxton created an issue
Puppet / PUP-7615
puppet command leaks module command issues.
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/06/02 2:02 AM
Priority:
Normal
Reporter:
Adam Buxton
when invoking $ puppet facts (and various utils) Warning: vosp_wls has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at '], "data_provider": null } ' Warning: wls_helpers has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at ' {"name":"puppetlabs-lvm","version_requirement":">= 0.7.0"}
], "data_provider": null } ' Warning: vosp_wls has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at '], "data_provider": null } ' Warning: wls_helpers has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at ' {"name":"puppetlabs-lvm","version_requirement":">= 0.7.0"}
], "data_provider": null } '
These appear to be bleed from what I would expect in puppet module list can or should these be quashed in other utilities.
Add Comment
Jira (PUP-7614) 'puppet help' does not provide entries for job, access or app
Title: Message Title Adam Buxton created an issue Puppet / PUP-7614 'puppet help' does not provide entries for job, access or app Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2017/06/02 1:58 AM Priority: Normal Reporter: Adam Buxton $puppet --help generates the following list Usage: puppet [options] [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally ca Local Puppet Certificate Authority management. catalog Compile, save, view, and convert catalogs. cert Manage certificates and requests certificate Provide access to the CA for certificate management. certificate_request Manage certificate requests. certificate_revocation_list Manage the list of revoked certificates. config Interact with Puppet's settings. describe Display help about resource types device Manage remote network devices doc Generate Puppet references enterprise Commands to facilitate support of Puppet Enterprise. epp Interact directly with the EPP template parser/renderer. facts Retrieve and store facts. file Retrieve and store files in a filebucket filebucket Store and retrieve files in a filebucket generate Generates Puppet code from Ruby definitions. help Display Puppet help. inspect Send an inspection report key Create, save, and remove certificate keys. license lookup Data in modules lookup function man Display Puppet manual pages. master The puppet master daemon module Creates, installs and searches for modules on the Puppet Forge. node View and manage node definitions. parser Interact directly with the parser. plugin
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jo Rhett commented on PUP-5206 Re: Puppet filebucket --local uses $bucketdir instead of $clientbucketdir diffing to grasp the changes made by a puppet run is very common and necessary. In large templates it is not always possible to recreate exactly what the output would be, or more specifically, why it wasn't what was expected without having a reference to the generated output. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
