Jira (PUP-6476) Add Hocon support to Puppet
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6476 Add Hocon support to Puppet Change By: Chris Price Assignee: Chris Price 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price assigned an issue to Chris Price Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Chris Price Assignee: Chris Price 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Henrik Lindberg commented on PUP-6291 Re: Add 'abs' support to Numeric.new Merged to master at: 4cdb8a9 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-6005) Specify the ordering used for directory based main manifest
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6005 Specify the ordering used for directory based main manifest 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 (PDB-2777) Make sure stockpile tests have some coverage of the "no metadata" case
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2777 Make sure stockpile tests have some coverage of the "no metadata" case 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 (PDOC-91) Strings should be able to document an environment
Title: Message Title William Hopper commented on PDOC-91 Re: Strings should be able to document an environment Also todo: figure out if docs needs this or if this is a 'nice to have'. If the latter, it probably doesn't belong in this epic. 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-90) Strings should be able to document a single, specific module
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-90 Strings should be able to document a single, specific module Change By: William Hopper Team: Puppet Developer Support 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-91) Strings should be able to document an environment
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-91 Strings should be able to document an environment Change By: William Hopper Henrik's description of the use case:Document an environment (i.e. layout as when compiling) to generate browseable docs for what is installed in an env. In this mode I can imagine wanting to skip certain modules, or regenerating one or a list of them (not sure how that plays with yard's web server and regeneration though). I believe at present, Strings will do this but only when using the webserver code path. We want to make this possible without having to also spin up the 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-4889) Direct Puppet Initiative
Title: Message Title Ryan Coleman commented on PUP-4889 Re: Direct Puppet Initiative Eric Sorenson, Kenn Hussey, I don't think we need this epic to remain open. Are there particular items in here that are going to be worked on by the Puppet Developer Support team? In the static compiler, we've shipped what we needed for the first revision of direct puppet and any outstanding items aren't covered here. 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-90) Strings should be able to document a single, specific module
Title: Message Title William Hopper commented on PDOC-90 Re: Strings should be able to document a single, specific module Henrik Lindberg whoops, I wrote this as I was running out the door . We actually talked about both of those modes of operation with Peter. This ticket is meant to track the second, 'single module' use case. I just filed PDOC-91 to track the case of documenting an 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 (PDOC-91) Strings should be able to document an environment
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-91 Strings should be able to document an environment Issue Type: Improvement Assignee: Unassigned Created: 2016/09/13 9:59 AM Priority: Normal Reporter: William Hopper Henrik's description of the use case: Document an environment (i.e. layout as when compiling) to generate browseable docs for what is installed in an env. In this mode I can imagine wanting to skip certain modules, or regenerating one or a list of them (not sure how that plays with yard's web server and regeneration though). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-92) Rename the puppetlabs-strings repo to puppet-strings
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-92 Rename the puppetlabs-strings repo to puppet-strings Issue Type: Task Assignee: Unassigned Created: 2016/09/13 10:17 AM Priority: Normal Reporter: William Hopper Strings is not a puppet module and should not be named as such. GitHub will indefinitely redirect from the old repo name to the new one, so we won't break anyone by doing this. Some references will need to be updated in internal docs, however. We'll need to track these down and make note of them. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Eric Sorenson assigned an issue to Kylo Ginsberg Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Eric Sorenson Assignee: Kylo Ginsberg 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Eric Sorenson commented on PUP-776 Re: Deprecate non-UTF-8 encodings for textual content I'm triaging old bugs and came across this one. Kylo Ginsberg can you determine if this is still a valid problem given all the work we've done on i18n lately? 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-93) Search box overlaps list items below on lefthand fulldoc navigator
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-93 Search box overlaps list items below on lefthand fulldoc navigator Issue Type: Bug Assignee: Unassigned Created: 2016/09/13 10:20 AM Priority: Normal Reporter: William Hopper Currently, the search box specified in the fulldoc template overlaps with the first function / class / etc item in the list below. We'll need to figure out how to overwrite YARD's default CSS for that box. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-661) Remove broken macauthorization provider from core types
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-661 Remove broken macauthorization provider from core types Change By: Eric Sorenson Team: Agent & Platform Support 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title Eric Sorenson commented on PUP-911 Re: Puppet silent about inability to acquire pidlock I'm triaging old bugs and came across this one. Assigning to Agent & Platform for further investigation. 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-266) Allow puppet to manage owner & group file settings
Title: Message Title Eric Sorenson commented on PUP-266 Re: Allow puppet to manage owner & group file settings Triaging old tickets - Ethan Brown can you give this a quick once-over and see if it's still valid? 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-266) Allow puppet to manage owner & group file settings
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-266 Allow puppet to manage owner & group file settings Change By: Eric Sorenson Team: Agent & Platform Support 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-266) Allow puppet to manage owner & group file settings
Title: Message Title Eric Sorenson assigned an issue to Ethan Brown Puppet / PUP-266 Allow puppet to manage owner & group file settings Change By: Eric Sorenson Assignee: Ethan Brown 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-147) Add validation to the ZFS type
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-147 Add validation to the ZFS type Change By: Eric Sorenson Team: Agent & Platform Support 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-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-41 Puppet returns different result non-existent services on EL and Debian Change By: Eric Sorenson Team: Agent & Platform Support 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-677) user type accepts numeric usernames, but ssh_authorized_key does not
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-677 user type accepts numeric usernames, but ssh_authorized_key does not Change By: Eric Sorenson Team: Agent & Platform Support 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-677) user type accepts numeric usernames, but ssh_authorized_key does not
Title: Message Title Eric Sorenson commented on PUP-677 Re: user type accepts numeric usernames, but ssh_authorized_key does not I'm triaging old bugs and came across this one. Joseph M Siegmann was this problem, in fact, a deal-breaker for your use of Puppet? IMO numeric userids should be supported and it'd be nice to fix this. 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-745) Windows does not support :links :follow on symlinks
Title: Message Title Eric Sorenson commented on PUP-745 Re: Windows does not support :links :follow on symlinks I'm triaging old bugs and came across this one. Ethan Brown is this still an issue? 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-718) Allow for disabling certain facts within Facter
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Glenn Sarti Assignee: Glenn Sarti 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-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title
Tim Purkerson created an issue
Puppet / PUP-6699
Leading zero with cron resource is not handled as expected.
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Unassigned
Components:
Language
Created:
2016/09/13 11:30 AM
Priority:
Normal
Reporter:
Tim Purkerson
Having a leading zero in the cron resource doesn't work as expected. It will either create a duplicate crontab entry or it is simply ignored.
For example:
class crontest { cron { '/usr/local/bin/crontest.sh': ensure => 'present', command => '/usr/local/bin/crontest.sh', hour => ['06'], minute => ['30'], target => 'root', user => 'root', }
}
[root@pe-201621-master manifests]# crontab -l
Puppet Name: /usr/local/bin/crontest.sh 30 6 * * * /usr/local/bin/crontest.sh
If your crontab entry already has a "non-Puppet" entry with a leading zero, it doesn't match it and creates a duplicate. For example:
Jira (PUP-147) Add validation to the ZFS type
Title: Message Title Eric Sorenson commented on PUP-147 Re: Add validation to the ZFS type Sending to Agent team board for triage - I *think* we added some zfs improvements which covered this, but can't be sure. 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Eric Sorenson Team: Engineering "Pool" 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-661) Remove broken macauthorization provider from core types
Title: Message Title Eric Sorenson assigned an issue to Geoff Nichols Puppet / PUP-661 Remove broken macauthorization provider from core types Change By: Eric Sorenson Assignee: Geoff Nichols 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-661) Remove broken macauthorization provider from core types
Title: Message Title Eric Sorenson commented on PUP-661 Re: Remove broken macauthorization provider from core types Assigning to Agent & platform for Mac OS X work. 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-745) Windows does not support :links :follow on symlinks
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-745 Windows does not support :links :follow on symlinks Change By: Eric Sorenson Team: Agent & Platform Support 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Eric Sorenson Team: Agent & Platform Support 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Eric Sorenson Team: Engineering "Pool" Workflow Connections 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Eric Sorenson commented on PUP-776 Re: Deprecate non-UTF-8 encodings for textual content Christopher Zappala this is part of your remit as part of Workflow Connections 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Eric Sorenson assigned an issue to Christopher Zappala Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Eric Sorenson Assignee: Christopher Zappala 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Chris Price commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Henrik Lindberg isn't it also the case that in Puppet 3, ruby functions would be env-isolated as long as you didn't do anything fancy like define a ruby class or method inside your puppet function definition? (I know that's not a complete or acceptable solution, but since we seem to be enumerating the actual state of the issue here...) 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Zee Alexander commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Henrik Lindberg so, what's the current state of issues with environment isolation and ruby extensions to Puppet? In architect we're still warning people about this in general, so I'd like to correct the record if possible. 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-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: Henrik Lindberg Affects Version/s: PE Everett Affects Version/s: PUP 4.8.0 Component/s: MEEP Key: PE PUP - 17451 6701 Project: Puppet Enterprise [Internal] 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
Jira (PUP-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg PUP-6680 introduced a regression as it does not handle boolean values and instead turns them into strings. This means that a Boolean false, turns into the truthy string "false" - which is really, really bad. Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: Henrik Lindberg Assignee: Henrik Lindberg Story Points: 1 Release Notes Summary: Bug introduced before release. Team: Organizational Scale Puppet Developer Support Sprint: Int APS 2016-09-21 Release Notes: Not Needed Fix Version/s: PUP 4.8.0 Add Comment
Jira (PUP-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Zee Alexander commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Eric Sorenson orly? If I write a function in Ruby, using the most up-to-date method calls and whatnot, it will successfully be segregated by environment with multiple versions of the same Ruby function? 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-718) Allow for disabling certain facts within Facter
Title: Message Title Glenn Sarti commented on FACT-718 Re: Allow for disabling certain facts within Facter PR Review: Adhoc build started at; https://jenkins.puppetlabs.com/view/puppet-agent/view/ad%20hoc/job/platform_puppet-agent_init-van-int_suite-manual-ad-hoc/324/ 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Henrik Lindberg commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Zee Alexander yes, if you use the 4.x function API, and 4.6.2 or later. In earlier versions there are problems with functions written in the puppet language under some conditions (addressed in 4.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-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Henrik Lindberg Component/s: Language Component/s: Types and Providers 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Henrik Lindberg Team: Engineering "Pool" Puppet Developer Support 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Henrik Lindberg Sprint: EP PDS 2016- 09 10 - 21 05 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-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6699
Leading zero with cron resource is not handled as expected.
Change By:
Henrik Lindberg
Having a leading zero in the cron resource doesn't work as expected. It will either create a duplicate crontab entry or it is simply ignored.For example: {code:puppet} class crontest { cron { '/usr/local/bin/crontest.sh':ensure => 'present',command => '/usr/local/bin/crontest.sh',hour => ['06'],minute => ['30'],target => 'root',user => 'root', }} {code} {code} [root@pe-201621-master manifests]# crontab -l# Puppet Name: /usr/local/bin/crontest.sh30 6 * * * /usr/local/bin/crontest.sh {code} If your crontab entry already has a "non-Puppet" entry with a leading zero, it doesn't match it and creates a duplicate. For example: {code} [root@pe-201621-master manifests]# crontab -l30 06 * * * /usr/local/bin/crontest.sh {code} becomes... {code} [root@pe-201621-master manifests]# crontab -l30 06 * * * /usr/local/bin/crontest.sh# Puppet Name: /usr/local/bin/crontest.sh30 6 * * * /usr/local/bin/crontest.sh {code}
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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Kylo Ginsberg Assignee: Kylo Ginsberg 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-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Henrik Lindberg Team: Agent & Platform Support 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-3051) Stop using activemq in the benchmark tool
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3051 Stop using activemq in the benchmark tool Issue Type: Improvement Assignee: Unassigned Created: 2016/09/13 1:59 PM Priority: Normal Reporter: 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
Jira (PUP-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Kylo Ginsberg commented on PUP-776 Re: Deprecate non-UTF-8 encodings for textual content Seems legit to me, and in the right epic. I marked it as accepted and unassigned myself. TBD is Andy's comment above about whether this should block on the Binary solution. 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-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols assigned an issue to Kylo Ginsberg Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Assignee: Geoff Nichols Kylo Ginsberg 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-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Assignee: Geoff Nichols 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Henrik Lindberg commented on PUP-6291 Re: Add 'abs' support to Numeric.new Just realized that an update to the documentation in new is also 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-5834) Handle extended data in the catalog
Title: Message Title Henrik Lindberg commented on PUP-5834 Re: Handle extended data in the catalog A couple of questions regarding the description: "each json property is an object" - how is that different from today's 'parameters'? There is no differentiation between a hash and an object "the scheme should reflect that" - what "scheme" is referenced here? The catalog schema? The json schema right about where it says that. The problem is that the json schema does not say if the objects are objects or hashes. There is no way to state that. "ext_properties encoding" - what is that? How things are encoded in an ext_property - whatever is decided (when this was written we did not have Pcore or Pcore serialization). given that the serialization must be capable of handling all conceivable types, what additional support is needed there to manage `ext_parameters`? Could we turn this around and make `ext_parameters` reuse the JSON format used by the serialization? It has the advantage of being extensible using the new Object type. Yes we could, the format inside of the ext_parameter is not important. The idea here is to make it possible to wire new data types to agents that know about them without blowing up tools that are unaware of their existence. Also, that the changes required are not too extensive (thus making it feasible to do them with reasonable effort and without disturbing too much of the agent's code base). There are other options: Make the entire catalog be a pcore serialization - boom, no weird "ext_parameters". This is in line with the epic "remove PSON". The downside is that everything in the toolchain must be able to handle the format which makes this into a very Big Bang. Move the ext_parameters from being inside a resource, as instead
Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title Henrik Lindberg commented on PDOC-60 Re: Strings skips docs for the log message functions Priority: This must be done in order to be able to replace the existing way of extracting the documentation. If not done there would be no documentation for the log functions on the docs site unless added manually. There are many different ways to solve this problem. A simple unroll is worth testing as it may be all that is 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-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren commented on PUP-5834 Re: Handle extended data in the catalog A couple of questions regarding the description: "each json property is an object" - how is that different from today's 'parameters'? "the scheme should reflect that" - what "scheme" is referenced here? The catalog schema? "ext_properties encoding" - what is that? given that the serialization must be capable of handling all conceivable types, what additional support is needed there to manage `ext_parameters`? Could we turn this around and make `ext_parameters` reuse the JSON format used by the serialization? It has the advantage of being extensible using the new Object type. 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-86) Make Markdown the default format
Title: Message Title Henrik Lindberg commented on PDOC-86 Re: Make Markdown the default format This is marked "ready for merge", but there is no link to a PR, and there seems to be no PR for this ticket in the repository ?!? 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-3050) Implementation
Title: Message Title Karel Brezina created an issue PuppetDB / PDB-3050 Implementation Issue Type: Sub-task Assignee: Karel Brezina Components: PuppetDB Created: 2016/09/13 3:29 AM Priority: Normal Reporter: Karel Brezina 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
Jira (PUP-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren commented on PUP-5834 Re: Handle extended data in the catalog I know that I've asked this before, but what is in place on the agent side and how is that subset managed? 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-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren commented on PUP-5834 Re: Handle extended data in the catalog I think it would be relatively easy to keep the ext_parameters inside a resource and still achieve efficient tabulation. It should just be a matter of using one single deserializer instance for all such serializations within a catalog. I will investigate this. I assume that during deserialization, all parameter values found in a catalog that are not of type Data (as described in the spec after the last update), will be serialized as ext_parameters automatically. 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-5834) Handle extended data in the catalog
Title: Message Title Henrik Lindberg commented on PUP-5834 Re: Handle extended data in the catalog The agent side certainly has all of the code in place that is in puppet. It also gets everything that the master decides to "plugin sync" to the agent. The plugin synced things ends up in the file system in a different structure than when it is in the layout used on the master. The agent is still using an Environment, but of a different implementation kind (IIRC RemoteEnvironment). There are probably issues with 4.x loaders and the smart-paths as they may be different. Also probable issues related to env object being different, as well as there being no Scope, and no Compiler. Thinking ahead, there is a desire to later be able to support things like "agent side functions" - which is worth taking into consideration when designing how to deal with loaders on the agent side (even if not part of this ticket per se). Code-wise, there is no clear delineation between agent and master code except that things under "puppet/parser" is thought to be master side only. The rest is open ended... 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-5834) Handle extended data in the catalog
Title: Message Title Henrik Lindberg commented on PUP-5834 Re: Handle extended data in the catalog The investigation will tell how easy it is - it basically reads the entire thing, then uses "from_data_hash" to create instances. That data hash could include the ext_parameters in already instantiated form. Currently the object itself does its own post processing (changing a string "environment" to a reference to an instance of Environment, and similar actions). It is desirable that all such actions are done outside of the objects being deserialized. Using (a corrected) definition of the Data type to determine how something is serialized seems fine. That should cover all nested structures as well. We have some data types that are actually references and that are encoded in string format - they may be instances of Resource now that serialize to a string representation of the reference to that resource. Thus the CatalogEntry types needs some special rule as they are not Data. 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-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Andres Nunez assigned an issue to Steve Quin PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Andres Nunez Assignee: Karel Brezina Steve Quin 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-6291) Add 'abs' support to Numeric.new
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-6484) Productize 'lookup'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6484 Productize 'lookup' Change By: Kylo Ginsberg Summary: Productize Puppet ' lookup ' 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-6484) Productize Puppet lookup
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6484 Productize Puppet lookup Change By: Kylo Ginsberg Epic Name: Productize Puppet Lookup 'lookup' 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title Henrik Lindberg commented on HI-537 Re: Default value doesn't work correctly with an alias I don't think changing the signature is an option as the API is not well specified and there are many implementations of hiera backends that could potentially break, or that would do the wrong thing. The only real working solution I can think of is to add the aliasing capability to "lookup_options". Such an option would in contrast to the alias interpolation function be a real alias in that it can treat a lookup of one key as a true lookup of another key. That in turn enables preserving the data type and would make aliasing of hashes and arrays possible as well as solving this particular use case (I think). With this feature, a lookup for say "x" aliased to "y" would simply never search for "x" among the data and instead return the "y". The implementation would need to handle chains of aliases, as well as circular aliases. The problem with trying to fix this for the interpolation function and interpreting certain kinds of interpolation results as something special (not found vs. empty string) would result in something that is hard to maintain as it relies on too many special cases. 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-6484) Productize Puppet lookup
Title: Message Title Henrik Lindberg commented on PUP-6484 Re: Productize Puppet lookup While "Productie Puppet Lookup" is the actual name, using that as the "Epic Name", makes the label that shows up everywhere read "Productize Puppet..." It would be best if we could have "Lookup" as the first word. 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-90) Strings should be able to document a single, specific module
Title: Message Title Henrik Lindberg updated an issue Puppet Strings / PDOC-90 Strings should be able to document a single, specific module Change By: Henrik Lindberg Issue Type: Bug Improvement 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-90) Strings should be able to document a single, specific module
Title: Message Title Henrik Lindberg commented on PDOC-90 Re: Strings should be able to document a single, specific module I think there are two fundamental modes of operation: Document an environment (i.e. layout as when compiling) to generate browseable docs for what is installed in an env. In this mode I can imagine wanting to skip certain modules, or regenerating one or a list of them (not sure how that plays with yard's web server and regeneration though). Document a single module - for this, the module is typically not installed in an environment (there is no env, no real modulepath, etc.). Difficult things here are handling references to things in other modules (OTOH, Strings currently does not do much processing of references). Which of the use cases is it this ticket is intended for? 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-87) Ensure our internal functions, types, and providers are documented in a way that's compatible with strings
Title: Message Title Henrik Lindberg commented on PDOC-87 Re: Ensure our internal functions, types, and providers are documented in a way that's compatible with strings Because we have not been using Strings to generate the documentation for functions in puppet we ended up using a pattern where the documentation for 4.x functions are kept in 3.x stubs. In order to reduce the burden of maintaining two copies of the documentation many of the 4.x functions simply have "documentation maintained in 3.x stub" as their documentation. In order to really fix this, all of the 3.x stubs needs to be copied over to the 4.x (actual) implementation of the function. When doing so, the text needs to be edited from the "free form, I hope this works" to yard/markdown. Some 4.x functions are documented in both the 3.x stub as well as in the 4.x implementation. For those there is no guarantee that the two copies have not drifted apart. A manual review must be done because the formats are different (side by side viewing in an editor kind of works). When this is done, the 3.x stubs can be deleted. 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-2782) Yumrepo target attribute does not work
Title: Message Title
Jonathan Gazeley commented on PUP-2782
Re: Yumrepo target attribute does not work
I'm working on a manifest that manages the stock yum.repos.d definitions from CentOS and can override some settings. This is tested and working on CentOS 7 but produces different behaviour on CentOS 6. Both platforms are running Puppet 3.8.7
yumrepo { 'CentOS-Base':
name => 'base',
target => '/etc/yum.repos.d/CentOS-Base.repo',
baseurl=> $baseurl,
mirrorlist => $mirrorlist,
descr => 'CentOS-$releasever - Base',
enabled=> $enabled,
gpgcheck => '1',
gpgkey => "file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-${::repo_centos::releasever}",
}
Jira (PDOC-88) Create a plan for ensuring strings support going forward
Title: Message Title Henrik Lindberg commented on PDOC-88 Re: Create a plan for ensuring strings support going forward We may need a test matrix of puppet versions as well. 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-5831) Add a Binary type and runtime object
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5831 Add a Binary type and runtime object Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
