Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Add Iterable type and runtime object The PR looks good in general. I left a couple of comments regarding bugs. There is a commit that changes the signatures of functions but forgets to mention that. The documentation for each function must be updated to reflect the change behavior and features, I left suggestions on the PR what I think needs to be covered. As I said there, I think it should be brief in each function. Later we need to explain the concept of "Iterable" and "Iterator" on the docs site. Before we are completely done with this, we also need to update the Language Specification. I think we also need to describe the concept of Iterable and Iterator in predocs as the specification will be too terse and not contain enough examples. (We can create additional tickets as needed), but I like to see the bugfixes and function docs updated before we merge. Moving this back to doing. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5648 Add Iterable type and runtime object Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-439) Get pre-suites working for Fedora 23 (i386, x86_64) for Hiera
Title: Message Title Kenn Hussey updated an issue Hiera / HI-439 Get pre-suites working for Fedora 23 (i386, x86_64) for Hiera Change By: Kenn Hussey Fix Version/s: HI 3.0.7 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5142) Get pre-suites working for Fedora 23 (i386, x86_64) for Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5142 Get pre-suites working for Fedora 23 (i386, x86_64) for Puppet Change By: Kenn Hussey Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1194) Get pre-suites working for Fedora 23 (i386, x86_64) for Facter
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1194 Get pre-suites working for Fedora 23 (i386, x86_64) for Facter Change By: Kenn Hussey Fix Version/s: FACT 3.1.5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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 (NPUP-16) Refactor command line options to support commands
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-16 Refactor command line options to support commands Change By: Peter Huene The native compiler needs to support more commands than simply "compiling" a catalog for an environment.When run without commands, the native compiler should output the help showing the available commands.Initially there should be three commands: compile (current behavior), help (display command help), and version (shows the compiler's version information).When run without a command, the native compiler should display a useful help summary with the list of supported commands:{code}$ bin/puppetcppUsage: puppetcpp [options]Compiles Puppet manifests into Puppet catalogs.Commands: compile Compile Puppet manifests into a Puppet catalog help Display help information version Show the version informationRun 'puppetcpp help ' for more information on a command.{code}The compile command should support the same options as before, except for the {{--version}} option which is now handled as a separate command:{code}$ bin/puppetcpp help compileUsage: puppetcpp compile [options] [[manifest] [manifest] ...]Compile Puppet manifests into a Puppet catalog.Options: --code-dir argThe Puppet code directory to use.Defaults to the current platform's codedirectory. --color Forces color output on platforms thatsupport colorized output. -d [ --debug ]Enable debug output. -e [ --environment ] arg (=production)The environment to compile for. --environment-dir arg Specifies a directory to search forenvironments. -f [ --facts ] argThe path to the YAML facts file to use.Defaults to the current system's facts. -g [ --graph ] argThe path to write a DOT language filefor viewing the catalog depencency dependency graph. --helpDisplay command help. -l [ --log-level ] arg (=notice) Set logging level.Supported levels: debug, info, notice,warning, error, alert, emergency,critical. --module-dir arg Specifies a directory to search forglobal modules. -n [ --node ] arg The node name to use. Defaults to the'fqdn' fact. --no-colorDisables color output. -o [ --output ] arg (=catalog.json) The output path for the compiledcatalog. --verbose Enable verbose (info) output.Compiles a Puppet manifest into a Puppet catalog. When invoked with no options,the compiler will compile the manifest for the 'production' environment.Manifests will be evaluated in the order they are presented on the command line.{code}The help comman
Jira (PUP-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Brandon High commented on PUP-5769 Re: Windows MSI overriding server with default value of "puppet" Also, there doesn't seem to be any PUPPET_MASTER_SERVER value set in the registry post-upgrade. I'm running a test right now to check what is in the registry pre-upgrade. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Brandon High updated an issue Puppet / PUP-5769 Windows MSI overriding server with default value of "puppet" Change By: Brandon High Attachment: windows-2012r2-x86_64.cfg Attachment: run_frictionless_upgrade.sh Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Brandon High updated an issue Puppet / PUP-5769 Windows MSI overriding server with default value of "puppet" Change By: Brandon High Attachment: Screen Shot 2016-01-28 at 4.41.40 PM.png Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Brandon High updated an issue Puppet / PUP-5769 Windows MSI overriding server with default value of "puppet" Change By: Brandon High It appears that PUP 4.3.2 overwrites the value of {{server}} in {{puppet.conf}} on windows 2012r2 (and 2008) with the default of {{puppet}}. This causes puppet runs to fail after upgrades (unless, of course, you are actually configuring {{puppet}} to point to your master.) I discovered this while testing my fix to puppet_agent, and while I cannot see anything in my changes that would be causing this issue, it may be causing it? If you are curious, the PR is https://github.com/puppetlabs/ pe_acceptance_tests puppetlabs-puppet_agent /pull/ 828 66 , which I have been testing with Josh's custom puppet_agent fix for pe_acceptance tests https://github.com/puppetlabs/pe_acceptance_tests/pull/828 and the attached beaker file/beaker command.I don't really know anything about how an MSI is made, but https://github.com/highb/puppet_for_the_win/blob/master/wix/puppet.wxs#L637 seems suspect to me? It seems to indicate to me that the default will be set if the command line option is not passed in, and the rest of the MSI appears to always set the value in the conf to whatever PUPPET_MASTER_SERVER has been set to. It appears that the documented behavior is to not change the value if the command line arg is not given: https://docs.puppetlabs.com/pe/latest/install_windows.html#puppetmasterserver {quote}"If you set a non-default value for this property, the installer will replace any existing value in puppet.conf. Also, the next time you upgrade, the installer will re-use your previous value for this property unless you set a new value on the command line. So if you’ve used this property once, you shouldn’t change the server setting directly in puppet.conf; you should re-run the installer and set a new value there instead."{quote} Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5769) Windows MSI overriding server with default value of "puppet"
Title: Message Title Brandon High created an issue Puppet / PUP-5769 Windows MSI overriding server with default value of "puppet" Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: Windows Created: 2016/01/28 4:58 PM Environment: centos 6 PE AIO master, upgraded from PE 3.8.3 to PE 2015.3.2-rc0-86-gb244f29 windows 2012r2 agent, upgraded from PUP 3.8.3 to PUP 4.3.2 with puppet_agent module Priority: Normal Reporter: Brandon High It appears that PUP 4.3.2 overwrites the value of server in puppet.conf on windows 2012r2 (and 2008) with the default of puppet. This causes puppet runs to fail after upgrades (unless, of course, you are actually configuring puppet to point to your master.) I discovered this while testing my fix to puppet_agent, and while I cannot see anything in my changes that would be causing this issue, it may be causing it? If you are curious, the PR is https://github.com/puppetlabs/pe_acceptance_tests/pull/828 , which I have been testing with Josh's custom puppet_agent fix fo
Jira (PUP-5699) Inline symlink metadata
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5699 Inline symlink metadata Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5122) Acceptance tests for direct puppet running from cache
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5122 Acceptance tests for direct puppet running from cache Change By: Eric Thompson QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5701) Compare files using checksum_value
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5701 Compare files using checksum_value Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5117) Inline file checksums
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5117 Inline file checksums Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5698) Inline directory metadata
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5698 Inline directory metadata Change By: Eric Thompson QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3077 When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment Change By: Eric Thompson QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5119) Handle file sources outside codedir
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5119 Handle file sources outside codedir Change By: Eric Thompson QA Risk Assessment: Medium High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5119) Handle file sources outside codedir
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5119 Handle file sources outside codedir Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5703 Handle cached catalog and pluginsync inconsistencies Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-917) Identify why a cached catalog was used
Title: Message Title Steve Barlow updated an issue Puppet / PUP-917 Identify why a cached catalog was used Change By: Steve Barlow Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5724) Backport PUP-5693 (benchmark function loading) to stable 4.3.3
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5724 Backport PUP-5693 (benchmark function loading) to stable 4.3.3 Change By: Eric Thompson QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5712) TypeParser cannot handle negative numbers
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5712 TypeParser cannot handle negative numbers Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1317) Facter YAML output can be accidentally parsed as sexagesimal
Title: Message Title Eric Thompson updated an issue Facter / FACT-1317 Facter YAML output can be accidentally parsed as sexagesimal Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5741) Confusing error message for invalid types for comparison operations
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5741 Confusing error message for invalid types for comparison operations Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5617) agent stalls when connection with master is dropped
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Eric Thompson QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5646) fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5646 fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used. Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5356) Nagios extension check_puppet.rb error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5356 Nagios extension check_puppet.rb error Change By: Eric Thompson QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5708) Deprecate pluginsync setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5356) Nagios extension check_puppet.rb error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5356 Nagios extension check_puppet.rb error Change By: Eric Thompson QA Risk Assessment Reason: no CI, rare usage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5356) Nagios extension check_puppet.rb error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5356 Nagios extension check_puppet.rb error Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5708) Deprecate pluginsync setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Eric Thompson QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1276) Module level external facts not resolved when using the Vagrant Puppet provider
Title: Message Title Bill Niestempski updated an issue Facter / FACT-1276 Module level external facts not resolved when using the Vagrant Puppet provider Change By: Bill Niestempski CS Priority: Needs Priority Normal CS Impact: Users that want to test their external facts using Vagrant on Windows can't do so easily. This issue essential breaks the Vagrant "share". CS Severity: 3 CS Business Value: 3 CS Frequency: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) --
Jira (PUP-5768) Fix problematic usage of ENV for Windows
Title: Message Title Ethan Brown commented on PUP-5768 Re: Fix problematic usage of ENV for Windows It might be worth pushing on Ruby to backport the fix to 2.1.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5768) Fix problematic usage of ENV for Windows
Title: Message Title Ethan Brown commented on PUP-5768 Re: Fix problematic usage of ENV for Windows There were some additional search hits inside of Ruby Facter 2.x where there is likely bad behavior as well. Probably not worth fixing at this point given these probably don't impact native Facter 3.x, but notes added for historical reasons: C:\source\puppet\.bundle\gems\ruby\2.1.0\gems\facter-2.4.4-x64-mingw32\lib\facter\path.rb: 10 Facter.add(:path) do 11setcode do 12: ENV['PATH'] 13end 14 end C:\source\puppet\.bundle\gems\ruby\2.1.0\gems\facter-2.4.4-x64-mingw32\lib\facter\core\execution\base.rb: 5 values.each do |var, value| 6# save the old value if it exists
Jira (PUP-5768) Fix problematic usage of ENV for Windows
Title: Message Title Ethan Brown created an issue Puppet / PUP-5768 Fix problematic usage of ENV for Windows Issue Type: Bug Assignee: Unassigned Created: 2016/01/28 2:50 PM Labels: windows Priority: Normal Reporter: Ethan Brown As part of PUP-5726, Windows API calls for retrieving / setting environment variables were added. This was done to work around a Ruby ENV bug https://bugs.ruby-lang.org/issues/8822 that corrupts UTF8 characters set in the environment (as keys or values) that don't map cleanly to the local codepage. While this was allegedly fixed in Ruby 2.3.0, it has not yet been backported or scheduled for backport. Therefore, the withenv helper was updated to not use Rubys ENV, and to instead use the API calls. However, there are a number of places where ENV is accessed and modified that may also trigger corruption issues. This ticket should cover: Finding other danger spots in the code - for instance access through ENV of PATH and HOME have risks of being problematic, but SYSTEMROOT, PATHEXT, windir and COMSPEC should be safe to ignore due to the low likelihood of these values containing Unicode characters. ENV usage inside tests can also generally be ignored, as problems running specs would likely only manifest on a non-English Windows install with a username that includes Unicode chars, that has a Unicode path as a home dir.
Jira (PUP-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg commented on PUP-5761 Re: when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing That helps pinpointing where it drives off the road... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable I have not looked at the implementation of the hiera-wrapper, but the user reported it as working for them. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable The ticket HI-421 is about a "whitelist filter". That ended with the user writing a hiera-wrapper backend. You can find that here: https://github.com/senax/hiera-wrapper (that is the white list wrapper), which you can probably use as a model for how to do what you want. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable The feature to let a backend take over is HI-471 . There is no example of a wrapping backend related to that. One other users created a wrapping backend for another purpose IIRC. Will try to find that ticket as well. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5497) (Burnside) Direct Puppet: Client Static Catalog
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5497 (Burnside) Direct Puppet: Client Static Catalog Change By: Sean Griffin QA Contact: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1780) Issue warning when undefined variables are accessed
Title: Message Title Henrik Lindberg commented on PUP-1780 Re: Issue warning when undefined variables are accessed A warning should given when user interpolates an undefined variable All of the following should lead to the same warning when used in a manifest: notice $boogie_man notice $boogie::man notice $::boogie_man notice $::boogie::man notice "$boogie_man" notice "$boogie::man" notice "$::boogie_man" notice "$::boogie::man"
Jira (PUP-5698) Inline directory metadata
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5698 Inline directory metadata Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-917) Identify why a cached catalog was used
Title: Message Title Hailee Kenney commented on PUP-917 Re: Identify why a cached catalog was used Verified that all the cases Whopper describes above work as intended at 'da82e8f0b0dcfe51a5bb6ca49b72b959c3245c4a'. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-917) Identify why a cached catalog was used
Title: Message Title Hailee Kenney assigned an issue to Steve Barlow Puppet / PUP-917 Identify why a cached catalog was used Change By: Hailee Kenney Assignee: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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 (NPUP-16) Refactor command line options to support commands
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-16 Refactor command line options to support commands Change By: Peter Huene The native compiler needs to support more commands than simply "compiling" a catalog for an environment. The proposed syntax When run without commands, the native compiler should output the help showing the available commands.Initially there should be three commands : compile (current behavior), help (display command help), and version (shows the compiler's version information). When run without a command, the native compiler should display a useful help summary with the list of supported commands: {code} $ bin/ puppetcpp [ Usage: puppetcpp < command > [options ] Compiles Puppet manifests into Puppet catalogs.Commands: compile Compile Puppet manifests into a Puppet catalog help Display help information version Show the version informationRun 'puppetcpp help < options command > ' for more information on a command. {code} Where The compile command should support the " same options as before, except for the {{--version}} option which is now handled as a separate command " will default :{code}$ bin/puppetcpp help compileUsage: puppetcpp compile [options] [[manifest] [manifest] ...]Compile Puppet manifests into a Puppet catalog.Options: --code-dir argThe Puppet code directory to " use.Defaults to the current platform's codedirectory. --color Forces color output on platforms thatsupport colorized output. -d [ --debug ]Enable debug output. -e [ --environment ] arg (=production)The environment to compile " with for. --environment-dir arg Specifies a directory to search forenvironments. -f [ --facts ] argThe path to the existing behavior YAML facts file to use . Defaults to the current system's facts. Initially there will be two commands -g [ --graph ] argThe path to write a DOT language filefor viewing the catalog depencencygraph. --helpDisplay command help. -l [ --log-level ] arg (=notice) Set logging level.Supported levels : "compile" and "parse" debug, info, notice,warning, error, alert, emergency,critical . --module-dir arg Specifies a directory to search forglobal modules. -n [ --node ] arg The latter node name to use. Defaults to the'fqdn' fact. --no-colorDisables color output. -o [ --output ] arg (=catalog.json) The output path for the compiledcatalog. --verbose Enable verbose (info) output.Compiles a Puppet manifest into a Puppet catalog. When invoked with no options
Jira (PUP-1780) Issue warning when undefined variables are accessed
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-1780 Issue warning when undefined variables are accessed Change By: Henrik Lindberg Assignee: Andrew Parker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5767) Add the specification from PUP-1985 to language specification repo
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5767 Add the specification from PUP-1985 to language specification repo Change By: Henrik Lindberg Component/s: Language Specification Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5767) Add the specification from PUP-1985 to language specification repo
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5767 Add the specification from PUP-1985 to language specification repo Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5767) Add the specification from PUP-1985 to language specification repo
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5767 Add the specification from PUP-1985 to language specification repo Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5767) Add the specification from PUP-1985 to language specification repo
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5767 Add the specification from PUP-1985 to language specification repo Issue Type: Task Assignee: Unassigned Created: 2016/01/28 1:07 PM Priority: Normal Reporter: Henrik Lindberg In PUP-1985 we did the implementation and definition of how parameters in a function, lambda, user defined resource and class may reference parameters in the same definition within the default value expressions. While working on PUP-1985 the spec work was done in a google document https://docs.google.com/document/d/1BAkV6rIhW-EWqUKXrqhlh7FmmUUK8wlfS5Xiw1e6ync/edit# that now needs to be transformed in style and content and be added to the language specification. Add Comment
Jira (PUP-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3142 exec type should allow passing of arguments as an array rather than a string Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Adrian Muraru commented on HI-496 Re: Hiera subkeys lookup should be configurable Please link this jira to the original request to see how the bacjend would look like. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2126) Add the `catalog_uuid` field to catalogs and `reports`
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2126 Add the `catalog_uuid` field to catalogs and `reports` Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2269) Store cached catalog reason
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2269 Store cached catalog reason Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2367) (maint) Add better config file handling
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2367 (maint) Add better config file handling Change By: gepetto-bot Sprint: PuppetDB 2016-02-10 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2367) (maint) Add better config file handling
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2367 (maint) Add better config file handling Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Had time waiting for reviews on other outstanding PRs Fix Version/s: PDB CLI 0.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2367) (maint) Add better config file handling
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2367 (maint) Add better config file handling Issue Type: Bug Assignee: Unassigned Created: 2016/01/28 12:14 PM Priority: Normal Reporter: gepetto-bot This commit removes a bug where the default configuration JSON was in the incorrect format. This commit also adds the ability to pass in either a single `server_urls` as a string or an array of `server_urls` for PuppetDB failover. This commit catches JSON parse errors as well and warns the user when they are encoutered, falling back to the default configuration. This commit also aligns the format of the CLI configuration file with all of the other PuppetDB configuration files, such that there is now a single `puppetdb` header where you specify your server_urls and ssl credentials. We do lose the ability to specify multiple PuppetDB environments but we'll gain this back we add in the ability to specify the path to the config file via a command line flag. Add Comment
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge commented on PUP-5766 Re: (Static Catalog) PE documentation for static catalogs in Burnside Josh Cooper, Eric Sorenson, Ryan Coleman. The way we document static catalogs will be slightly different (in audience and tone) than for OSS. I'm trying to put together an outline for what I'll cover. Can you indicate if I'm on the right track or not? I appreciate your help and feedback. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment.* During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade.* Documentation tracking off PE-13884.h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question * If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment.* During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade. * Documentation tracking off PE-13884. h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* ( I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me . ) h2. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this mess
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge created an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Issue Type: Task Assignee: Isaac Eldridge Components: DOCS Created: 2016/01/28 11:17 AM Priority: Normal Reporter: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following: Enabling static catalogs During fresh install of PE, they enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment. During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade. Conceptual overview info Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated wi
Jira (PUP-5117) Inline file checksums
Title: Message Title Michael Smith commented on PUP-5117 Re: Inline file checksums Discussion with Josh Cooper so far: This should happen as part of the catalog Compiler terminus, not the StaticCompiler terminus. The behavior may borrow most of the StaticCompiler implementation, but doesn't need to be identical if it doesn't make sense. Having a framework in the Compiler terminus for inlining things (this, PUP-5697, PUP-5699) seems useful, so I'm going to put that up as initial work (maybe it should be a separate ticket?). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5117) Inline file checksums
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5117 Inline file checksums Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Sean Griffin commented on PUP-5761 Re: when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing There is an error message reported when the lookup function is used instead. [root@fzs6mpn39mljkhq code]# puppet apply -e 'notice(lookup("hello::module_key"))' Error: Module data for module 'hello' must use keys qualified with the name of the module [root@fzs6mpn39mljkhq code]# Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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/pupp
Jira (PUP-1780) Issue warning when undefined variables are accessed
Title: Message Title Henrik Lindberg commented on PUP-1780 Re: Issue warning when undefined variables are accessed This is already in place for some use cases but not all. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-199) improve bindings with override and abstract
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-199 improve bindings with override and abstract Change By: Henrik Lindberg Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-199) improve bindings with override and abstract
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-199 improve bindings with override and abstract Change By: Henrik Lindberg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-199) improve bindings with override and abstract
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-199 improve bindings with override and abstract Change By: Henrik Lindberg Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-199) improve bindings with override and abstract
Title: Message Title Henrik Lindberg commented on PUP-199 Re: improve bindings with override and abstract This is of value, but as the binder is now only used at the lowest level tying plugins together, the priority of this is much lower. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-198) Warn if same bindings loaded in lower layer
Title: Message Title Henrik Lindberg commented on PUP-198 Re: Warn if same bindings loaded in lower layer The "binder" is no longer a highly exposed user facing feature that everyone would use. The binder is now used for very technical integration at the plugin level, and providing this type of validation is overkill. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Sean Griffin Attachment: manifest-pup-5761-v2.pp Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Sean Griffin Attachment: manifest-pup-5761.pp Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-499) Design solution for code coverage
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-499 Design solution for code coverage Change By: Henrik Lindberg Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5765) Features for testing and assuring quality of puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5765 Features for testing and assuring quality of puppet Issue Type: Epic Assignee: Unassigned Created: 2016/01/28 10:48 AM Priority: Normal Reporter: Henrik Lindberg This epic is about features that enable/help users test their puppet manifest, and related logic (types, providers). It also includes features that help assure quality throughout the code. This epic is related to Code Validation, which deals with parsing/validation and error reporting. This epic in contrast is about testing frameworks, testing APIs, code coverage, runtime APIs helping testing frameworks set up and run and provide a stable way of running Puppet as a Library for testing purposes. Add Comment
Jira (PUP-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing I think we should issue a warning when user has such a key in the returned data. The keys that are ok should function. Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Fix Version/s: PUP 4.3.3 Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-4474) Complete the lookup, "data in modules" feature
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4474 Complete the lookup, "data in modules" feature Change By: Henrik Lindberg Summary: Complete the lookup, "data in modules" functionality introduced in puppet 4.0.0 feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-4474) Complete the "data in modules" functionality introduced in puppet 4.0.0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4474 Complete the "data in modules" functionality introduced in puppet 4.0.0 Change By: Henrik Lindberg Epic Name: 4.x Data in Modules Lookup 4x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1787) Improve Puppet's Modularity
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1787 Improve Puppet's Modularity Change By: Henrik Lindberg Epic Name: Maintainable Puppet Modules Modularity Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1787) Improve Puppet's Modularity
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1787 Improve Puppet's Modularity Change By: Henrik Lindberg Assignee: Andrew Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1787) Improve Puppet's Modularity
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1787 Improve Puppet's Modularity Change By: Henrik Lindberg Summary: Improved strictness and safety in the Language Improve Puppet's Modularity Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-1787) Improved strictness and safety in the Language
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1787 Improved strictness and safety in the Language Change By: Henrik Lindberg UpdateThis Epic is somewhat repurposed to focus on "Module Maintainability" which includes protecting private classes/types and parameters, dependencies between modules, and modularity in general.This epic used to be a very broad "quality, strictness and safety", but that is a scope that is too broad. Many of the tickets in this epic should be moved to the "Code Validation" ticket.Original The puppet language still has a lot of gotchas that can crop up. Many of these allow unexpected behavior to occur or get rid of the guarantees expected by users such as immutability, strictness about variable use, and difficulty creating good encapsulations. We need to implement something like a "strict mode" that lets users turn on certain checks in certain cases and in other cases we need to provide new functionality to let them express what is really needed. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-799) speedup re-parsing by serializing valid parse result
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-799 speedup re-parsing by serializing valid parse result Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-4193) Add ability to use a lambda as case option for advanced matching
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4193 Add ability to use a lambda as case option for advanced matching Change By: Henrik Lindberg Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-4193) Add ability to use a lambda as case option for advanced matching
Title: Message Title Henrik Lindberg commented on PUP-4193 Re: Add ability to use a lambda as case option for advanced matching Will close this in favor of PUP-5764 which is something we should add. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5142) Get pre-suites working for Fedora 23 (i386, x86_64) for Puppet
Title: Message Title John Duarte commented on PUP-5142 Re: Get pre-suites working for Fedora 23 (i386, x86_64) for Puppet Kenn Hussey, no beaker still uses project pre-suites. These will eventually be pulled out into their own gem/library, but until then we need to ensure that these work with the new platform. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5764) Support a single _ to mean ignored parameter
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5764 Support a single _ to mean ignored parameter Issue Type: Improvement Assignee: Unassigned Created: 2016/01/28 10:09 AM Priority: Normal Reporter: Henrik Lindberg It is of value to be able to define that a parameter should be ignored. This helps in situations where a lambda needs to have several parameters, but only some of them are actually needed. The user must otherwise name the parameter. Code checking (that we do not have yet though) would then find a declared parameter that is unused. Using a _ instead of a parameter name also serves as a clear indication that it is ignored. There should be no problems introducing a single _ as a keyword as that is not a meaningful bare word, Here is an example: {a => 10, b => 20}.each |$key, _ | { notice $key } There are other uses cases for the single underscore, it does not always mean ignore, it can also be used as place to put a single injected values, and other use cases. The _ alone should be thought of as anonymous identifier or "Jane Doe".
Jira (PDB-2227) Create PDB CLI man pages
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2227 Create PDB CLI man pages Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2151) Update PE Modules for PuppetDB HA
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2151 Update PE Modules for PuppetDB HA Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-2153) Update HA-guide for classification-based install procedure
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2153 Update HA-guide for classification-based install procedure Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-4193) Add ability to use a lambda as case option for advanced matching
Title: Message Title Henrik Lindberg commented on PUP-4193 Re: Add ability to use a lambda as case option for advanced matching Although we can add this if we want to, I don't see this as that important. We will instead be possible to do something like this with the help of parameterized aliased types since case does an instance_of? check when a case option is a Type and the type system is versatile enough to describe quite elaborate matches. Closing with Won't do. But will add a ticket for the ignore parameter '_¨ (if we do not have that already). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-5120 Send checksum_type and static_catalog query params in catalog request Change By: Branan Riley Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5617) agent stalls when connection with master is dropped
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Branan Riley Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5646) fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-5646 fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used. Change By: Branan Riley Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-4750) Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4750 Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) Change By: Henrik Lindberg Summary: Raise Error when Type/Provider has mixed case in name (eg j2_maxPageReadAhead) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5742 Add ability to create Aliases for Puppet Types in PL Change By: Henrik Lindberg Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this 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.