Jira (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Lindsey Smith commented on PDOC-161 Re: As a developer I want to programmatically retrieve the name and short description from a puppet class Hailee Kenney, William Hopper, Peter Huene: any reasons why the proposed solution isn't the way to go? 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Abir Majumdar updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Abir Majumdar Use Case:Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s).The Issue: You can get the name from puppet-strings , but puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal.Proposed Solution:Create a new puppet-strings-specific YARD tag (similar to puppet.type.param) for storing a short description with a limit of 50-80 characters. This field should show up in the JSON output. Optionally the field can show up in the HTML. 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Abir Majumdar updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Abir Majumdar Use Case:Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s).The Issue: puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal.Proposed Solution:Create a new puppet-strings-specific YARD tag (similar to puppet.type.param) for storing a short description with a limit of 50-80 characters. This field should show up in the JSON output. Optionally the field can show up in the HTML. 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Abir Majumdar updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Abir Majumdar Use Case:Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s).The Issue: puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal.Proposed Solution:Create a new puppet-strings-specific YARD tag (similar to puppet.type.param) for storing a short description with a limit of 50-80 characters. This field should show up in the HTML and the JSON 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.
Jira (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Abir Majumdar updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Abir Majumdar Summary: As a developer I want to programmatically retrieve the name and short description from a puppet file. class 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 (PDOC-161) As a developer I want to retrieve the name and description from a puppet file.
Title: Message Title Abir Majumdar commented on PDOC-161 Re: As a developer I want to retrieve the name and description from a puppet file. There's some additional discussion about this in the following Google Group thread: https://groups.google.com/a/puppet.com/forum/#!topic/cs-architecture/svLAQDD4x4s 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 (PDOC-161) As a developer I want to retrieve the name and description from a puppet file.
Title: Message Title Abir Majumdar created an issue Puppet Strings / PDOC-161 As a developer I want to retrieve the name and description from a puppet file. Issue Type: Improvement Assignee: Unassigned Created: 2017/02/17 3:34 PM Priority: Normal Reporter: Abir Majumdar Use Case: Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s). The Issue: puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal. Proposed Solution: Create a new puppet-strings-specific YARD tag (similar to puppet.type.param) for storing a short description with a limit of 50-80 characters. This field should show up in the HTML and the JSON output. Add Comment
Jira (FACT-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1569 Add Ubuntu 16.10 to Ubuntu facts acceptance test Change By: Maggie Dreyer Fix Version/s: FACT 3.6.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 (FACT-1541) Facter does not compile with icedtea JDK
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1541 Facter does not compile with icedtea JDK Change By: Maggie Dreyer Fix Version/s: FACT 3.6.z 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-1541) Facter does not compile with icedtea JDK
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1541 Facter does not compile with icedtea JDK Change By: Maggie Dreyer Fix Version/s: FACT 3.6.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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-7221 puppet type schedule: weekday parameters: integers not allowed Change By: Jorie Tappa Assignee: Nicholas Fagerlund Jorie Tappa 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-6372) Puppet::Transaction#failed? is unused - remove it
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6372 Puppet::Transaction#failed? is unused - remove it Change By: Moses Mendoza Team: Agent & Platform 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-6372) Puppet::Transaction#failed? is unused - remove it
Title: Message Title Moses Mendoza commented on PUP-6372 Re: Puppet::Transaction#failed? is unused - remove it merged to master at https://github.com/puppetlabs/puppet/commit/582dec833153b520a2660f46fe35763f2bb2cbbf 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-6372) Puppet::Transaction#failed? is unused - remove it
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6372 Puppet::Transaction#failed? is unused - remove it Change By: Moses Mendoza Sprint: AP 2017-02-22 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-6372) Puppet::Transaction#failed? is unused - remove it
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6372 Puppet::Transaction#failed? is unused - remove it Change By: Moses Mendoza 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-7214) PUP-6663 causes a regression of PUP-535
Title: Message Title Moses Mendoza commented on PUP-7214 Re: PUP-6663 causes a regression of PUP-535 merged to master at https://github.com/puppetlabs/puppet/commit/1f31c4291d185e47fbc413c4bff7e6273439960f 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-7231) Facts always one run behind when using storeconfigs and PuppetDB
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7231 Facts always one run behind when using storeconfigs and PuppetDB Change By: Moses Mendoza Priority: Normal Major 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-7231) Facts always one run behind when using storeconfigs and PuppetDB
Title: Message Title Moses Mendoza moved an issue Puppet / PUP-7231 Facts always one run behind when using storeconfigs and PuppetDB Change By: Moses Mendoza Affects Version/s: SERVER 2.7.2 Component/s: Puppet Server Key: SERVER PUP - 1729 7231 Project: Puppet Server 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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Moses Mendoza commented on PUP-7221 Re: puppet type schedule: weekday parameters: integers not allowed I think the immediate change is to update the docs to accurately reflect the existing state of affairs, but we should separately consider extending the parameter definition to allow integer types. 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-7134) Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files
Title: Message Title Moses Mendoza commented on PUP-7134 Re: Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files merged to master at https://github.com/puppetlabs/puppet/commit/b440c9c0909065ae7d33c4aaeaa00fe57817ee2f 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-7214) PUP-6663 causes a regression of PUP-535
Title: Message Title Michael Smith updated an issue Puppet / PUP-7214 PUP-6663 causes a regression of PUP-535 Change By: Michael Smith 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Susan McNerney updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Susan McNerney Labels: LTS-Triage 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-7229) Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7229
Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Change By:
Henrik Lindberg
Basically, `hiera_hash` and `hiera_array` with deep merge (using a global hiera.yaml FWIW) stopped working correctly on our puppetserver when the puppet-agent package was upgraded. I know we're using some deprecated patterns, but the breakage in the minor version update was unexpected.Please see https://gist.github.com/kpaulisse/b8a8f854988032eceae3e53f242d6309 for simple steps to reproduce. This also manifests itself in a number of other odd ways, such as `hiera_include` taking several seconds on the newer version. {code} {{-WORKING-#ii puppet-agent 1.8.3-1jessieamd64The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.#ii puppetserver 2.7.2-1puppetlabs1 all Puppet Labs puppetserverNotice: /Stage[main]/Main/Node[default]/Notify[{ "middle": {"groups": { "foo": {"gid": 500 }},"users": { "kevin": {"uid": 500 }} }}]/message: current_value absent, should be { "middle": {"groups": { "foo": {"gid": 500 }},"users": { "kevin": {"uid": 500 }} }} (noop) {code} {code} -NOT WORKING-#ii puppet-agent 1.9.1-1jessieamd64The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.#ii puppetserver 2.7.2-1puppetlabs1 all Puppet Labs puppetserverNotice: /Stage[main]/Main/Node[default]/Notify[{ "middle": {"users": { "kevin": {"uid": 500 }} }}]/message: current_value absent, should be { "middle": {"users": { "kevin": {"uid": 500 }} }} (noop)}} {code}
Add Comment
Jira (PUP-7230) acceptance: hiera5 eyaml backend and deep merges
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-7230 acceptance: hiera5 eyaml backend and deep merges Change By: Eric Thompson Assignee: Eric Sorenson 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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Jorie Tappa commented on PUP-7221 Re: puppet type schedule: weekday parameters: integers not allowed Hi Moses Mendoza, what's the verdict here, should the code be updated to allow numbers for weekdays, or the documentation be updated to reflect that it's not allowed? 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-7230) acceptance: hiera5 eyaml backend and deep merges
Title: Message Title Eric Thompson created an issue Puppet / PUP-7230 acceptance: hiera5 eyaml backend and deep merges Issue Type: Sub-task Assignee: Eric Sorenson Components: QA Created: 2017/02/17 10:54 AM Priority: Normal Reporter: Eric Thompson 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
Jira (PUP-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Eric Thompson QA Risk Assessment Reason: high user priority; possible regressions 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-7227) Add "reference" kind to the Pcore Object Attribute
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7227 Add "reference" kind to the Pcore Object Attribute Change By: Henrik Lindberg Release Notes Summary: internal concern Release Notes: Not Needed 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-7216) hiera_hash doesn't use deeper merge
Title: Message Title Susan McNerney updated an issue Puppet / PUP-7216 hiera_hash doesn't use deeper merge Change By: Susan McNerney Labels: flanders-ss 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-7191) Puppet errors when managing non-existent service on AIX
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7191 Puppet errors when managing non-existent service on AIX Change By: Moses Mendoza 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-7191) Puppet errors when managing non-existent service on AIX
Title: Message Title Moses Mendoza commented on PUP-7191 Re: Puppet errors when managing non-existent service on AIX merged to master at https://github.com/puppetlabs/puppet/commit/67d7b52a118a54233a693732a3a25b3a05575a4c 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-7228) exec command fails if command is single word with trailing newline
Title: Message Title Moses Mendoza commented on PUP-7228 Re: exec command fails if command is single word with trailing newline thanks for filing otheus 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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Moses Mendoza commented on PUP-7221 Re: puppet type schedule: weekday parameters: integers not allowed thanks for filing otheus 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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Moses Mendoza commented on PUP-7221 Re: puppet type schedule: weekday parameters: integers not allowed cc Jorie Tappa 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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7221 puppet type schedule: weekday parameters: integers not allowed Change By: Moses Mendoza Team: Agent & Platform 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-7221) puppet type schedule: weekday parameters: integers not allowed
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7221 puppet type schedule: weekday parameters: integers not allowed Change By: Moses Mendoza Sprint: AP Grooming 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-1571) Add "is_virtual" fact for AIX
Title: Message Title Moses Mendoza commented on FACT-1571 Re: Add "is_virtual" fact for AIX Ah thanks Scott Pruzinsky. I had no idea AIX was commonly run on bare-metal outside an lpar environment. 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-7214) PUP-6663 causes a regression of PUP-535
Title: Message Title
Michael Smith commented on PUP-7214
Re: PUP-6663 causes a regression of PUP-535
I'm curious where the quote is added. When I try to do something like
rpm -qa --qf "%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\\n"
I don't see any quoting.
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-7228) exec command fails if command is single word with trailing newline
Title: Message Title Michael Smith updated an issue Puppet / PUP-7228 exec command fails if command is single word with trailing newline Change By: Michael Smith 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 (FACT-1572) how to call the Product Name in the Puppet Board.
Title: Message Title Michael Smith commented on FACT-1572 Re: how to call the Product Name in the Puppet Board. I believe what you're looking for is https://docs.puppet.com/facter/3.6/core_facts.html#productname, which is still present in Facter. If Puppet Board is unable to to query that for some reason, I'd take that up as an Issue with Puppet Board. Closing this ticket, as it does not appear to be an issue with Facter. 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-3219) Deleting from reports spends most of the time enforcing a constraint on certnames
Title: Message Title Nick Walker commented on PDB-3219 Re: Deleting from reports spends most of the time enforcing a constraint on certnames This issue is resolved by the index added in PDB-3053 . 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-7229) Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Title: Message Title Thomas Hallgren commented on PUP-7229 Re: Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays lindsey.smith, looking more closely at this, I think I was wrong. This is not resolved in 4.9.2. Kevin Paulisse assumption is correct so the fix is in 4.9.3. Sorry for the confusion. 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-7229) Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Title: Message Title Lindsey Smith commented on PUP-7229 Re: Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays I missed to your earlier response, but it may be worth retesting with 4.9.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-7229) Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Title: Message Title Lindsey Smith commented on PUP-7229 Re: Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays We believe that is resolved in Puppet 4.9.2. I'm trying to find the specific ticket and it should be in this set: https://docs.puppet.com/puppet/4.9/release_notes.html#bug-fixes 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-7229) Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Title: Message Title Kevin Paulisse commented on PUP-7229 Re: Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays Probably a duplicate of https://tickets.puppetlabs.com/browse/PUP-7216 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-7229) Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Title: Message Title
Kevin Paulisse created an issue
Puppet / PUP-7229
Backward-incompatible change from 4.8 and 4.9: deep merged hiera hashes and arrays
Issue Type:
Bug
Affects Versions:
PUP 4.9.1
Assignee:
Unassigned
Created:
2017/02/17 6:16 AM
Priority:
Normal
Reporter:
Kevin Paulisse
Basically, `hiera_hash` and `hiera_array` with deep merge (using a global hiera.yaml FWIW) stopped working correctly on our puppetserver when the puppet-agent package was upgraded. I know we're using some deprecated patterns, but the breakage in the minor version update was unexpected.
Please see https://gist.github.com/kpaulisse/b8a8f854988032eceae3e53f242d6309 for simple steps to reproduce. This also manifests itself in a number of other odd ways, such as `hiera_include` taking several seconds on the newer version.
{{- WORKING - #ii puppet-agent 1.8.3-1jessie amd64 The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. #ii puppetserver 2.7.2-1puppetlabs1 all Puppet Labs puppetserver
Notice: /Stage[main]/Main/Node[default]/Notify[{ "middle": { "groups": { "foo": { "gid": 500 }
}, "users": { "kevin": { "uid": 500 }
} } }]/message: current_value absent, should be { "middle": { "groups": { "foo": { "gid": 500 }
}, "users": { "kevin": { "uid": 500 }
} } } (noop)
