Jira (PUP-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Aaron Armstrong Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Aaron Armstrong updated an issue Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Aaron Armstrong Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/668/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1250) PR (1273): (maint) switch testing to m3.large - wkalt
Title: Message Title gepetto-bot commented on PDB-1250 Re: PR (1273): (maint) switch testing to m3.large - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/667/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3666) Replace 'configtimeout' with separate HTTP connect and read timeout settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3666 Replace 'configtimeout' with separate HTTP connect and read timeout settings Change By: Nicholas Fagerlund Labels: docs_reviewed redmine Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3666) Replace 'configtimeout' with separate HTTP connect and read timeout settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3666 Replace 'configtimeout' with separate HTTP connect and read timeout settings Change By: Nicholas Fagerlund There's an agent setting 'configtimeout' which purports to:{noformat}:configtimeout => { :default => 120, :desc => "How long the client should wait for the configuration to be retrieved before considering it a failure. This can help reduce flapping if too many clients contact the server at one time.",},{noformat}This is not correct though, as it's actually used for all http connections. The option should be renamed to reflect reality (perhaps to `httptimeout`?) and docs updated accordingly.Final decision: * New setting: {{http_connect_timeout}} — controls how long Puppet should attempt to make a connection. Normal to have a small value for this. * New setting: {{http_read_timeout}} — controls how long Puppet should allow transfers to continue. Normal to let this last a long time or be infinite, since some things just take a while to compile or download. * {{configtimeout}} is deprecated, and logs a warning if it's set. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more o
Jira (PUP-3666) Replace 'configtimeout' with separate HTTP connect and read timeout settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3666 Replace 'configtimeout' with separate HTTP connect and read timeout settings Change By: Nicholas Fagerlund There's an agent setting 'configtimeout' which purports to:{noformat}:configtimeout => { :default => 120, :desc => "How long the client should wait for the configuration to be retrieved before considering it a failure. This can help reduce flapping if too many clients contact the server at one time.",},{noformat}This is not correct though, as it's actually used for all http connections. The option should be renamed to reflect reality (perhaps to `httptimeout`?) and docs updated accordingly. Final decision: Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3666) Replace 'configtimeout' with separate HTTP connect and read timeout settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3666 Replace 'configtimeout' with separate HTTP connect and read timeout settings Change By: Nicholas Fagerlund Summary: Replace 'configtimeout' setting is erroneously named with separate HTTP connect and read timeout settings Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3666) 'configtimeout' setting is erroneously named
Title: Message Title Nicholas Fagerlund assigned an issue to Nicholas Fagerlund Puppet / PUP-3666 'configtimeout' setting is erroneously named Change By: Nicholas Fagerlund Assignee: Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4034) Update MSI for AIO
Title: Message Title Josh Cooper created an issue Puppet / PUP-4034 Update MSI for AIO Issue Type: Task Assignee: Unassigned Created: 2015/02/23 6:03 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Josh Cooper The MSI needs to: 1. Create the codedir according to https://github.com/puppetlabs/puppet-specifications/pull/25 2. Copy default hiera.yaml to $codedir 3. Create hieradata directory in $codedir Add Comment
Jira (PUP-4034) Update MSI for AIO
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4034 Update MSI for AIO Change By: Josh Cooper Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4034) Update MSI for AIO
Title: Message Title Josh Cooper assigned an issue to Ethan Brown Puppet / PUP-4034 Update MSI for AIO Change By: Josh Cooper Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3605) Puppet doesn't remove users from groups on OpenBSD
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3605 Puppet doesn't remove users from groups on OpenBSD Change By: Nicholas Fagerlund Summary: Puppet doesn't remove users from groups on OpenBSD Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Josh Cooper commented on HI-298 Re: Update FS layout for hiera PR submitted https://github.com/puppetlabs/hiera/pull/255 but currently blocked. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1250) PR (1273): (maint) switch testing to m3.large - wkalt
Title: Message Title gepetto-bot commented on PDB-1250 Re: PR (1273): (maint) switch testing to m3.large - wkalt Pull request (maint) switch testing to m3.large has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-344) Hiera configuration file periodic reload?
Title: Message Title Henrik Lindberg moved an issue Hiera / HI-344 Hiera configuration file periodic reload? Change By: Henrik Lindberg Component/s: Puppet Server Affects Version/s: SERVER 1.0.2 Key: SERVER HI - 341 344 Project: Puppet Server Hiera Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-344) Hiera configuration file periodic reload?
Title: Message Title Henrik Lindberg commented on HI-344 Re: Hiera configuration file periodic reload? Linked this to the "Data in Modules" epic since that is the umbrella for the work on hiera to change this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-826) Change AIO external facts directory
Title: Message Title Josh Cooper updated an issue Facter / FACT-826 Change AIO external facts directory Change By: Josh Cooper Sprint: Client 2015-03-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-826) Change AIO external facts directory
Title: Message Title Josh Cooper updated an issue Facter / FACT-826 Change AIO external facts directory Change By: Josh Cooper Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Henrik Lindberg commented on HI-298 Re: Update FS layout for hiera Paths for Windows are being specified https://github.com/puppetlabs/puppet-specifications/pull/25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg commented on PUP-1806 Re: Varargs support for the new function API We talked about this in chat and decided: to use the name :capturing to let the type specify the min, max the same way as it is specified in the Puppet Language - i.e. T means Array[T], and if min/max is wanted the type should be given as Array[T] - to get a variable number of arrays it is specified as Array[Array[T]] Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt wkalt commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-826) Change AIO external facts directory
Title: Message Title Josh Cooper assigned an issue to Peter Huene Facter / FACT-826 Change AIO external facts directory Change By: Josh Cooper Assignee: Eric Sorenson Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1250) PR (1273): (maint) switch testing to m3.large - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1250 PR (1273): (maint) switch testing to m3.large - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/02/23 4:12 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) switch testing to m3.large Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1273 Discussion Pull Request 1273 File Diff Pull Request Description We're having ec2 capacity issues testing on c3.large; trying m3.large. (webhooks-id: 63ced67204d0a033edbe3e38e2dcefaa)
Jira (FACT-826) Change AIO external facts directory
Title: Message Title Josh Cooper created an issue Facter / FACT-826 Change AIO external facts directory Issue Type: Task Affects Versions: FACT 2.4.1 Assignee: Eric Sorenson Created: 2015/02/23 4:06 PM Fix Versions: FACT 2.4.2 Labels: AIO Priority: Normal Reporter: Josh Cooper Change external facts directory from /opt/puppetlabs/agent/facts.d to /opt/puppetlabs/facter/facts.d on *nix, Windows is unchanged. Add Comment
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/662/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1005) regex operator does not work in abbreviated subqueries against trusted facts
Title: Message Title Wyatt Alt commented on PDB-1005 Re: regex operator does not work in abbreviated subqueries against trusted facts Behavior on the v4 endpoint is consistent now, with the regex operator not working on structured fact values. I think that's appropriate; closing the ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/656/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1229) change reports to use schema and retire validation.clj
Title: Message Title Wyatt Alt assigned an issue to AJ Roetker PuppetDB / PDB-1229 change reports to use schema and retire validation.clj Change By: Wyatt Alt Assignee: AJ Roetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1218) Metrics, Status & Logs: Add id to reports table
Title: Message Title Wyatt Alt assigned an issue to AJ Roetker PuppetDB / PDB-1218 Metrics, Status & Logs: Add id to reports table Change By: Wyatt Alt Assignee: AJ Roetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-342) REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port
Title: Message Title Thomas Hallgren commented on HI-342 Re: REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port Ah, forgot my last comment. Just looked at HI-343. I agree, it will fix this issue too. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-342) REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port
Title: Message Title Thomas Hallgren commented on HI-342 Re: REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port John Duarte the failing paths comes from a variable picked up as agent['hieradatadir']. I'm unable to see where it comes from though. Is this path fed into the test from some external source somehow? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Thomas Hallgren commented on PUP-1806 Re: Varargs support for the new function API but thinking more about name, we actually need a name that does mean both unfold and capture in order to be varargs. In that respect, I think the term :splat is OK. And it is well known by a large percentage of the users. Both :unfold and :capturing suffers from just catching one aspect. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Thomas Hallgren commented on PUP-1806 Re: Varargs support for the new function API :unfold should also accept a Variant tree as long as all leafs are of type Array or Tuple. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Thomas Hallgren commented on PUP-1806 Re: Varargs support for the new function API Why not use a type instead, to describe min/max (and other aspects)? We can then have :required, :optiona, or :unfold. When :unfold is used, the parameter type must be an Array or a Tuple. Simple solution, yet with brings all advantages. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-342) REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port
Title: Message Title John Duarte commented on HI-342 Re: REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port Thomas Hallgren this also appears to be a test failure, due to the hiera data paths not being correctly interpreted in the test harness. The PR for HI-343 should also address this test. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-343) REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml
Title: Message Title John Duarte updated an issue Hiera / HI-343 REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml Change By: John Duarte Comment: DO NOT MERGE the above PR yet. There are additional issues that need to be addressed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1249 PR (1270): (maint) benchmark improvements - wkalt Change By: Wyatt Alt Assignee: Wyatt Alt Story Points: 0 Issue Type: Task Improvement Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1249 PR (1270): (maint) benchmark improvements - wkalt Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1249 PR (1270): (maint) benchmark improvements - wkalt Change By: Wyatt Alt Sprint: PuppetDB 2015-02-25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Wyatt Alt Sprint: PuppetDB 2015- 03 02 - 11 25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Wyatt Alt Sprint: PuppetDB 2015- 02 03 - 25 11 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Wyatt Alt Sprint: PuppetDB 2015- 03 02 - 11 25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Wyatt Alt commented on PDB-1124 Re: PuppetDB high CPU usage Anton Fomenko We've seen this before in the context of GC problems related to the same PDB-1031 . You can raise the limit on open files using ulimit, but this may be a symptom of the other issue rather than something new. We believe this specifically happens when the command-processing queue is extremely backed up. The backup would be caused by inability to keep up with incoming commands due to constant heavy gc strain. Does that seem consistent with what you're seeing? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Jean Bond commented on PUP-3546 Re: Modify exec node terminus to support JSON OK, thanks, Henrik Lindberg. Then, if no one objects, I'll unassign myself and take the DOCS component off of it until it actually needs to come to the DOCS teams. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4033) add aio path spec test
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4033 add aio path spec test Change By: Eric Thompson Assignee: Eric Sorenson Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4033) add aio path-spec acceptance tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4033 add aio path-spec acceptance tests Change By: Eric Thompson Summary: add aio path - spec test acceptance tests Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-343) REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml
Title: Message Title John Duarte commented on HI-343 Re: REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml DO NOT MERGE the above PR yet. There are additional issues that need to be addressed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4033) add aio path spec test
Title: Message Title Eric Thompson created an issue Puppet / PUP-4033 add aio path spec test Issue Type: Sub-task Assignee: Eric Sorenson Components: QA Created: 2015/02/23 11:12 AM Priority: Normal Reporter: Eric Thompson ensure installs and code honor puppet-agent path spec: https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1249 PR (1270): (maint) benchmark improvements - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/02/23 10:58 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) benchmark improvements Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1270 Discussion Pull Request 1270 File Diff Pull Request Description This adds two optional flags to benchmark: A/ -archive is passed a path to a PDB export, and will use whatever catalogs/report
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-343) REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml
Title: Message Title John Duarte commented on HI-343 Re: REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml See PR 254 for fixing the pathing issue in the acceptance tests. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg commented on PUP-1806 Re: Varargs support for the new function API The min max should only optionally be allowed on the last :captures variable, the others are implicitly 1:1 for require and 0:1 for optional (and cannot be changed/given). You can naturally not have a min on the capturing parameter if there are optional parameters before it. I don't like the name :splat - it is puppet/ruby-speak for the unary * operator - and it has dual purpose, it means "unfold", and "capture" depending on where it is used. The term :captures is not great as it is on a different form than :optional and :required, it should really be :capturing, or :capturing_rest, but they are kind of heavy. I considered the term :variable but that is really confusing. Thought about a bunch of other names for it that I did not like (on the themes 'array', 'remaining', 'fold', 'spill over', 'excess', 'extra', 'additional', 'zero-many', 'multiple', etc. etc.). Think :capturing is readable both with and without min/max args. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3997) Audit and update puppet acceptance tests that assume the puppet user and group are present
Title: Message Title Michael Smith updated an issue Puppet / PUP-3997 Audit and update puppet acceptance tests that assume the puppet user and group are present Change By: Michael Smith Sprint: Client 2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3967) Run puppet acceptance with cfacter
Title: Message Title Michael Smith updated an issue Puppet / PUP-3967 Run puppet acceptance with cfacter Change By: Michael Smith Sprint: Client 2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1248) Write Initial PuppetDB 3.0 Release Notes
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1248 Write Initial PuppetDB 3.0 Release Notes Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1248) Write Initial PuppetDB 3.0 Release Notes
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1248 Write Initial PuppetDB 3.0 Release Notes Change By: Russell Mull Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1248) Write Initial PuppetDB 3.0 Release Notes
Title: Message Title Russell Mull created an issue PuppetDB / PDB-1248 Write Initial PuppetDB 3.0 Release Notes Issue Type: Task Assignee: Unassigned Created: 2015/02/23 10:04 AM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.
Jira (HI-342) REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port
Title: Message Title Thomas Hallgren commented on HI-342 Re: REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port This is probably because I didn't realize that we had acceptance tests that calls directly on Hiera backends. Sounds like that kind of tests should be covered well by using the Hiera config and its public API. I'll take a look. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1225) Update fact storage and querying to use the new path column in the facts table
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1225 Update fact storage and querying to use the new path column in the facts table Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Thomas Hallgren commented on PUP-1806 Re: Varargs support for the new function API If not :varargs, then I think :splat is a better choice. To me :captures makes good sense together with min/max arguments but not alone. The reason I think min/max is unnecessary is that I don't think anyone ever writes a function that needs 2 - 10 integers. When a specific number of integers is needed they would most likely be declared by name. And even if a use case can be found where min/max would be needed, why pass a type-constrained array as or tuple as one parameter for such cases? I think there's great value in keeping this simple and easy to understand. I spent a fair amount of time trying to grasp the by the arg_count parameter because it was a concept that I'd never seen before in a method signature. Having it on each parameter makes it even harder to understand. Or perhaps you just want it on the last parameter? If so, it's in essence the same thing as the current arg_count. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-343) REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml
Title: Message Title Henrik Lindberg commented on HI-343 Re: REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml looks like a faulty test - path has changed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-342) REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port
Title: Message Title Henrik Lindberg commented on HI-342 Re: REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port Is this a test of the hiera command line tool? Ping Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-343) REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml
Title: Message Title John Duarte created an issue Hiera / HI-343 REGRESSION hiera acceptance failures due to absence of /etc/puppet/scope.yaml Issue Type: Bug Assignee: John Duarte Created: 2015/02/23 9:10 AM Priority: Normal Reporter: John Duarte See CI failure https://jenkins.puppetlabs.com/job/Hiera-Acceptance-master/208/ Standard Error Error: Cannot create /etc/puppet/hieradata; parent directory /etc/puppet does not exist Error: /Stage[main]/Main/File[/etc/puppet/hieradata]/ensure: change from absent to directory failed: Cannot create /etc/puppet/hieradata; parent directory /etc/puppet does not exist
Jira (HI-342) REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port
Title: Message Title John Duarte created an issue Hiera / HI-342 REGRESSION acceptance/tests/yaml_backend/02-lookup_data_with_no_options.rb fails to return http_port Issue Type: Bug Assignee: John Duarte Created: 2015/02/23 9:07 AM Priority: Normal Reporter: John Duarte See CI failure: https://jenkins.puppetlabs.com/job/Hiera-Acceptance-master/208 * Try to lookup string data g8vs6nicup5q5eb.delivery.puppetlabs.net (host) 21:03:28$ hiera http_port nil
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg commented on PUP-1806 Re: Varargs support for the new function API We are missing the ability to specify min and max for variable number of arguments. My proposal is exactly what you propose, only that if you want to specify min/max for a varags/captures, you give that as a hash of options instead of separate arguments. We could naturally accept min, max as additional (optional arguments, with min being 0 by default, and max being infinity). Not sure :varags is a relevant name for puppet users / ruby users who may think more like "splat make the variable capture the rest" - this also because optional arguments also makes it possible to call with a "variable number of arguments". This was the reason I choose :captures. i.e. I am fine with this: param 'Integer', :the_rest, :captures, 2, 10 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Upgrade TK on stable
Title: Message Title Kenneth Barber commented on PDB-1247 Re: Upgrade TK on stable Here's the commit for the original patch fwiw: https://github.com/puppetlabs/puppetdb/commit/ea8f6965bb7f02692b30e5f6447ca79ca42f0e6e Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3982) Ensure puppet service supports conditional restart
Title: Message Title Josh Cooper commented on PUP-3982 Re: Ensure puppet service supports conditional restart Builds are available in http://builds.puppetlabs.lan/puppet-agent/bc00b6e7106846aae0af5b915976a8d192e53803/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Josh Cooper commented on PUP-3632 Re: Update paths and defaults for the unified FS layout Builds are available in http://builds.puppetlabs.lan/puppet-agent/bc00b6e7106846aae0af5b915976a8d192e53803/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Upgrade TK on stable
Title: Message Title Christopher Price commented on PDB-1247 Re: Upgrade TK on stable s/has offered to backport/has offered to provide guidance to assist with a backport/g Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Upgrade TK on stable
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1247 Upgrade TK on stable Change By: Kenneth Barber Fix Version/s: PDB 2.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Upgrade TK on stable
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1247 Upgrade TK on stable Change By: Kenneth Barber Affects Version/s: PDB 2.2.2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Upgrade TK on stable
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1247 Upgrade TK on stable Issue Type: Bug Assignee: Unassigned Created: 2015/02/23 8:36 AM Priority: Normal Reporter: Ryan Senior This ticket covers backporting PDB-618 to stable. Kenneth Barber things this should apply pretty easily to stable. Specifically we want to get the max-threads related fixes in the next PE release. If back porting PDB-618 turns out to be more trouble than it's worth, Christopher Price has offered to backport the change to make it so we don't need to upgrade. Add Comment
Jira (PDB-1246) Add V3 API deprecation message
Title: Message Title Brian LaMetterey updated an issue PuppetDB / PDB-1246 Add V3 API deprecation message Change By: Brian LaMetterey Sprint: AM PuppetDB 2015-03-11 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Upgrade TK on stable
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1247 Upgrade TK on stable Change By: Ryan Senior This ticket covers backporting PDB- 618 813 to stable. [~ken] things this should apply pretty easily to stable. Specifically we want to get the max-threads related fixes in the next PE release. If back porting PDB- 618 813 turns out to be more trouble than it's worth, [~chris] has offered to backport the change to make it so we don't need to upgrade. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Eric Thompson commented on PUP-1635 Re: "current thread not owner" after Puppet Agent receives USR1 signal thanks for the analysis, everyone. this is great! just to clarify: part of our FR process will track the need for an acceptance test at medium priority in testrail. This will ensure we create an acceptance test... sometime Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Thomas Hallgren commented on PUP-1806 Re: Varargs support for the new function API I think the suggested arguments with :optional and :required is fine but then it gets too complicated. Why not add a :varargs instead and forget about the more complex ways of defining things. I can't see the benefit in expressing the details. The disadvantage is that the more advanced this concept gets, the harder it will become to document it in a way that is easy to read. So how about just adding a third parameter that is :required, :optional, or :varargs and skip the details? What actual use-case is not covered by doing that? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1229) change reports to use schema and retire validation.clj
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1229 change reports to use schema and retire validation.clj Change By: Kenneth Barber Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://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 Trevor Vaughan created an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Issue Type: Improvement Assignee: Unassigned Created: 2015/02/23 7:23 AM Environment: Any Priority: Normal Reporter: Trevor Vaughan There was recent discussion on the Puppet Dev list about the new configuration format being HOCON. To provide environment-wide consistency, Hiera should also support a native HOCON back end. Also, a conversion script should be provided to convert existing YAML and JSON data to HOCON (though JSON should 'just work'). Add Comment
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Henrik Lindberg commented on PUP-3546 Re: Modify exec node terminus to support JSON Jean Bond This ticket targets Puppet 5.0.0 (i.e. sometime in the future), and as stated, it may or may not change anything... - if something is changed it will affect docs (given that the mechanism is documented somewhere). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1243) We should accept null fields for noop for incoming commands
Title: Message Title Kenneth Barber assigned an issue to AJ Roetker PuppetDB / PDB-1243 We should accept null fields for noop for incoming commands Change By: Kenneth Barber Assignee: AJ Roetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1218) Metrics, Status & Logs: Add id to reports table
Title: Message Title Kenneth Barber assigned an issue to AJ Roetker PuppetDB / PDB-1218 Metrics, Status & Logs: Add id to reports table Change By: Kenneth Barber Assignee: AJ Roetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1246) Add V3 API deprecation message
Title: Message Title Kenneth Barber commented on PDB-1246 Re: Add V3 API deprecation message I don't think this is such a great idea, marking v3 as deprecated puts us in a weird place in regards to the versioning policy: https://docs.puppetlabs.com/puppetdb/2.2/versioning_policy.html But yet, v4 is still experimental in 2.x, and we know its going to change in 3.x. So we can't just make that 'stable'. So, that would mean marking all of our API's as both deprecated and experimental in 2.x ... I'm not sure this is a great thing. What then is the current API? I would rather leave it as it is, maybe add a mention in the release notes for 2.3.0 that in the future v3 will go away, and v4 will become stable, this is rather implied, and documented already. But I don't think we should drop warning messages in our code, its just going to be confusing to users who think that in 2.x the v3 API is still 'current'. What makes this weird, is the major release boundary at the end of the day, we're making a hard cut at that point, but this is fairly normal for software and semantic versioning. Also be mindful, that this only affects API consumers (like people who write applications against our tool), not end users. End users shouldn't care directly ... since they use tools to get at our API, only API consumers should care and they are a different class of user (in short, they are developers just like us and should get this stuff). If we throw a deprecation warning, most end users might see it and get confused but this is targeting the wrong user, API consumers won't need a continual reminder, they'll be doing the Right Thing (tm) and should already understand our versioning policy before they ship their tool, the major API consumers also generally reach out to us for any clarification if required. Anyway, probably needs more thought & discussion. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to t