Jira (PDB-3052) [QA] Identify Tests Required
Title: Message Title Andrew Hayes assigned an issue to Seamus McKenna PuppetDB / PDB-3052 [QA] Identify Tests Required Change By: Andrew Hayes Assignee: Andrew Hayes Seamus McKenna Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3050) Implementation
Title: Message Title Andrew Hayes assigned an issue to Seamus McKenna PuppetDB / PDB-3050 Implementation Change By: Andrew Hayes Assignee: qa Seamus McKenna Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title Elof Ofel created an issue PuppetDB / PDB-3063 latest_report_noop_pending=null, should be =true Issue Type: Bug Affects Versions: PDB 4.2.2 Assignee: Unassigned Components: PuppetDB Created: 2016/09/21 3:27 AM Priority: Normal Reporter: Elof Ofel Hmm, I think the changes with "noop_pending", intoduced in v4.2 ( PDB-2753 ) is buggy. latest_report_noop_pending is set to null even though the last noop run showed changes. Example: On node foo.bar.com I run 'puppet agent -t --noop'. It shows me there are changes to be made. In puppetdb however, it looks like this: curl -X GET http://127.0.0.1:8080/pdb/query/v4/nodes/foo.bar.com
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title
Elof Ofel updated an issue
PuppetDB / PDB-3063
latest_report_noop_pending=null, should be =true
Change By:
Elof Ofel
Hmm, I think the changes with "noop_pending", intoduced in v4.2 (PDB-2753) is buggy.latest_report_noop_pending is set to null even though the last noop run showed changes.Example:On node foo.bar.com I run 'puppet agent -t --noop'.It shows me there are changes to be made.In puppetdb however, it looks like this:{noformat}curl -X GET http://127.0.0.1:8080/pdb/query/v4/nodes/foo.bar.com{ "deactivated" : null, "latest_report_hash" : "114082ba90a7a0fc94580ffa520315d8d1f2723a", "facts_environment" : "production", "cached_catalog_status" : "not_used", "report_environment" : "production", "latest_report_corrective_change" : null, "catalog_environment" : "production", "facts_timestamp" : "2016-09-21T08:33:28.459Z", "latest_report_noop" : true, "expired" : null, "latest_report_noop_pending" : null, "report_timestamp" : "2016-09-21T08:33:31.811Z", "certname" : "foo.bar.com", "catalog_timestamp" : "2016-09-21T08:33:32.601Z", "latest_report_status" : "unchanged"}{noformat}{noformat}So... "report_timestamp" : "2016-09-21T08:33:31.811Z" Correct. That's the time I ran the noop. "latest_report_noop" : true Correct, I've run nothing else after the noop. "latest_report_status" : "unchanged" Correct, nothing was changed. "latest_report_noop_pending" : {color:red} null {color} Wrong!{noformat}I have a cron job that periodically do a noop-run on all my nodes.For nodes that are not "up to date", I get an email report.Also, in PuppetExplorer I list these "nodes with pending jobs" using a query like this:{noformat}#report { latest_report?=true and noop=true and status="unchanged" }{noformat}Since PuppetDB 4.2, this query doesn't work any more.The problem is that neither of these querys now show me the list of nodes with pending jobs:{noformat}#node { latest_report_noop_pending=true }#report { latest_report?=true and noop_pending=true }{noformat}Is my query wrong, or is there a bug in puppetdb?(Running the latest puppet on Debian 8.6: puppet-agent 1.6.2-1jessiepuppetdb 4.2.2-1puppetlabs1puppetdb-termini 4.2.2-1puppetlabs1puppetexplorer 2.0.0-62puppetlabs-release-pc1 1.1.0-2jessiepuppetserver 2.6.0-1puppetlabs1)
Add Comment
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title
Elof Ofel updated an issue
PuppetDB / PDB-3063
latest_report_noop_pending=null, should be =true
Change By:
Elof Ofel
Hmm, I think the changes with "noop_pending", intoduced in v4.2 (PDB-2753) is buggy.latest_report_noop_pending is set to null even though the last noop run showed changes.Example:On node foo.bar.com I run 'puppet agent -t --noop'.It shows me there are changes to be made.In puppetdb however, it looks like this:{noformat}curl -X GET http://127.0.0.1:8080/pdb/query/v4/nodes/foo.bar.com{ "deactivated" : null, "latest_report_hash" : "114082ba90a7a0fc94580ffa520315d8d1f2723a", "facts_environment" : "production", "cached_catalog_status" : "not_used", "report_environment" : "production", "latest_report_corrective_change" : null, "catalog_environment" : "production", "facts_timestamp" : "2016-09-21T08:33:28.459Z", "latest_report_noop" : true, "expired" : null, "latest_report_noop_pending" : null, "report_timestamp" : "2016-09-21T08:33:31.811Z", "certname" : "foo.bar.com", "catalog_timestamp" : "2016-09-21T08:33:32.601Z", "latest_report_status" : "unchanged"}{noformat}{noformat}So... "report_timestamp" : "2016-09-21T08:33:31.811Z" Correct. That's the time I ran the noop. "latest_report_noop" : true Correct, I've run nothing else after the noop. "latest_report_status" : "unchanged" Correct, nothing was changed. "latest_report_noop_pending" : null Wrong!{noformat} I have a cron job that periodically do a noop-run on all my nodes.For nodes that are not "up to date", I get an email report.Also, in PuppetExplorer I list these "nodes with pending jobs" using a query like this:{noformat}#report { latest_report?=true and noop=true and status="unchanged" }{noformat}Since PuppetDB 4.2, this query doesn't work any more.The problem is that neither of these querys now show me the list of nodes with pending jobs:{noformat}#node { latest_report_noop_pending=true }#report { latest_report?=true and noop_pending=true }{noformat}Is my query wrong, or is there a bug in puppetdb?(Running the latest puppet on Debian 8.6: puppet-agent 1.6.2-1jessiepuppetdb 4.2.2-1puppetlabs1puppetdb-termini 4.2.2-1puppetlabs1puppetexplorer 2.0.0-62puppetlabs-release-pc1 1.1.0-2jessiepuppetserver 2.6.0-1puppetlabs1)
Add Comment
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title
Elof Ofel updated an issue
PuppetDB / PDB-3063
latest_report_noop_pending=null, should be =true
Change By:
Elof Ofel
Hmm, I think the changes with "noop_pending", intoduced in v4.2 (PDB-2753) is buggy.latest_report_noop_pending is set to null even though the last noop run showed changes.Example:On node foo.bar.com I run 'puppet agent -t --noop'.It shows me there are changes to be made.In puppetdb however, it looks like this:{noformat}curl -X GET http://127.0.0.1:8080/pdb/query/v4/nodes/foo.bar.com{ "deactivated" : null, "latest_report_hash" : "114082ba90a7a0fc94580ffa520315d8d1f2723a", "facts_environment" : "production", "cached_catalog_status" : "not_used", "report_environment" : "production", "latest_report_corrective_change" : null, "catalog_environment" : "production", "facts_timestamp" : "2016-09-21T08:33:28.459Z", "latest_report_noop" : true, "expired" : null, "latest_report_noop_pending" : null, "report_timestamp" : "2016-09-21T08:33:31.811Z", "certname" : "foo.bar.com", "catalog_timestamp" : "2016-09-21T08:33:32.601Z", "latest_report_status" : "unchanged"}{noformat}{noformat}So... "report_timestamp" : "2016-09-21T08:33:31.811Z" Correct. That's the time I ran the noop. "latest_report_noop" : true Correct, I've run nothing else after the noop. "latest_report_status" : "unchanged" Correct, nothing was changed. "latest_report_noop_pending" : null Wrong!{noformat} \\ \\ \\ I have a cron job that periodically do a noop-run on all my nodes.For nodes that are not "up to date", I get an email report.Also, in PuppetExplorer I list these "nodes with pending jobs" using a query like this:{noformat}#report { latest_report?=true and noop=true and status="unchanged" }{noformat}Since PuppetDB 4.2, this query doesn't work any more.The problem is that neither of these querys now show me the list of nodes with pending jobs:{noformat}#node { latest_report_noop_pending=true }#report { latest_report?=true and noop_pending=true }{noformat} \\ \\ Is my query wrong, or is there a bug in puppetdb?(Running the latest puppet on Debian 8.6: puppet-agent 1.6.2-1jessiepuppetdb 4.2.2-1puppetlabs1puppetdb-termini 4.2.2-1puppetlabs1puppetexplorer 2.0.0-62puppetlabs-release-pc1 1.1.0-2jessiepuppetserver 2.6.0-1puppetlabs1)
Add Comment
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title
Elof Ofel updated an issue
PuppetDB / PDB-3063
latest_report_noop_pending=null, should be =true
Change By:
Elof Ofel
Hmm, I think the changes with "noop_pending", intoduced in v4.2 (PDB-2753) is buggy.latest_report_noop_pending is set to null even though the last noop run showed changes.Example:On node foo.bar.com I run 'puppet agent -t --noop'.It shows me there are changes to be made.In puppetdb however, it looks like this:{noformat}curl -X GET http://127.0.0.1:8080/pdb/query/v4/nodes/foo.bar.com{ "deactivated" : null, "latest_report_hash" : "114082ba90a7a0fc94580ffa520315d8d1f2723a", "facts_environment" : "production", "cached_catalog_status" : "not_used", "report_environment" : "production", "latest_report_corrective_change" : null, "catalog_environment" : "production", "facts_timestamp" : "2016-09-21T08:33:28.459Z", "latest_report_noop" : true, "expired" : null, "latest_report_noop_pending" : null, "report_timestamp" : "2016-09-21T08:33:31.811Z", "certname" : "foo.bar.com", "catalog_timestamp" : "2016-09-21T08:33:32.601Z", "latest_report_status" : "unchanged"}{noformat}{noformat}So... "report_timestamp" : "2016-09-21T08:33:31.811Z" Correct. That's the time I ran the noop. "latest_report_noop" : true Correct, I've run nothing else after the noop. "latest_report_status" : "unchanged" Correct, nothing was changed. "latest_report_noop_pending" : null Wrong!{noformat}\\I have a cron job that periodically do a noop-run on all my nodes.For nodes that are not "up to date", I get an email report.Also, in PuppetExplorer I list these "nodes with pending jobs" using a query like this:{noformat}#report { latest_report?=true and noop=true and status="unchanged" }{noformat}Since PuppetDB 4.2, this query doesn't work any more.The problem is that neither of these querys now show me the list of nodes with pending jobs:{noformat}#node { latest_report_noop_pending=true }#report { latest_report?=true and noop_pending=true } #report { latest_report?=true and noop=true and status="unchanged" }{ noformat}Is my query wrong, or is there a bug in puppetdb?(Running the latest puppet on Debian 8.6: puppet-agent 1.6.2-1jessiepuppetdb 4.2.2-1puppetlabs1puppetdb-termini 4.2.2-1puppetlabs1puppetexplorer 2.0.0-62puppetlabs-release-pc1 1.1.0-2jessiepuppetserver 2.6.0-1puppetlabs1)
Add Comment
Jira (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Scott Walker updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Scott Walker Fix Version/s: pe everett Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6637) New attribute :manage_mountpoint for Mount type
Title: Message Title Matt Schuchard updated an issue Puppet / PUP-6637 New attribute :manage_mountpoint for Mount type Change By: Matt Schuchard The manage_mountpoint attribute parameter for the Mount type will create the mountpoint directory with limited permissions if it is missing prior to mounting and the attribute is set to true. It will also remove the mountpoint after unmounting if the attribute parameter is set to true. Default value for attribute is false.Since this resolves the File[mountpoint directory] --> Mount[mountpoint directory] --> File[directory permissions] circular dependency that formerly was worked around with an exec for File[mountpoint directory], we can now also implement an autobefore of Mount[mountpoint directory] --> File[directory permissions]. I encourage discussion over the worthwhileness (probably not a word) of that proposal. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3052) [QA] Identify Tests Required
Title: Message Title Scott Walker updated an issue PuppetDB / PDB-3052 [QA] Identify Tests Required Change By: Scott Walker Fix Version/s: pe everett Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3050) Implementation
Title: Message Title Scott Walker updated an issue PuppetDB / PDB-3050 Implementation Change By: Scott Walker Fix Version/s: pe everett Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6717) (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen
Title: Message Title Tatar Robert created an issue Puppet / PUP-6717 (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen Issue Type: Bug Assignee: Unassigned Created: 2016/09/21 6:08 AM Priority: Blocker Reporter: Tatar Robert We seem to be receiving the following error messages for all our modules which are using stdlib functions: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Internal Server Error: org.jruby.exceptions.RaiseException: (LoadError) no such file to load – puppet_x/puppetlabs/std lib/deprecation_gen Apparently this requirement has been introduces 2 hours ago. Is this an known issues ? Thank you. Add Comment
Jira (PUP-6717) (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen
Title: Message Title Tatar Robert updated an issue Puppet / PUP-6717 (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen Change By: Tatar Robert Component/s: Breaking Change Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6717) (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen
Title: Message Title Tatar Robert updated an issue Puppet / PUP-6717 (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen Change By: Tatar Robert Affects Version/s: PUP 4.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6717) (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen
Title: Message Title R.I.Pienaar commented on PUP-6717 Re: (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen you should not run master of stdlib, run a release. master has no guarantees about it working ever. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6717) (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen
Title: Message Title Tatar Robert commented on PUP-6717 Re: (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen Thanks R.I., didn't knew that!. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Nirupama Mantha Sprint: SCR 2016-09-21 , SCR 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6005) Specify the ordering used for directory based main manifest
Title: Message Title Thomas Hallgren commented on PUP-6005 Re: Specify the ordering used for directory based main manifest Merged to master at b4f4479. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6714) PCore generation omits information about capability types
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6714 PCore generation omits information about capability types Change By: Thomas Hallgren Assignee: Thomas Hallgren Story Points: 2 Team: Puppet Developer Support Sprint: PDS 2016-09-21 Fix Version/s: PUP 4.8.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this gr
Jira (PUP-6714) PCore generation omits information about capability types
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6714 PCore generation omits information about capability types Change By: Thomas Hallgren Sprint: PDS 2016- 09 10 - 21 05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3063) latest_report_noop_pending=null, should be =true
Title: Message Title Wyatt Alt commented on PDB-3063 Re: latest_report_noop_pending=null, should be =true Elof Ofel The new feature here is actually in the puppet agent – PuppetDB is simply passing it through. Can you confirm your agent version and that you're on the latest? PuppetDB will behave the way you're describing on versions prior to the introduction of the feature. I'm not sure I completely follow you on the second question. The behavior of the first query shouldn't have changed in 4.2, and the two involving noop_pending may be broken due to the agent version. Are you saying the first now returns incorrect data? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6534) Windows parallel specs fail
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6534 Windows parallel specs fail Change By: Geoff Nichols Sprint: Windows 2016-07-27, Windows 2016-08-10, AP 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6642) Puppet::Agent class accepts Report but no way to use correct transaction_uuid
Title: Message Title David Kramer updated an issue Puppet / PUP-6642 Puppet::Agent class accepts Report but no way to use correct transaction_uuid Change By: David Kramer Sprint: PCP 2016-09-07, Hotlist, FF 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3062) Write up end-user docs with perf recommendations with stockpile
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3062 Write up end-user docs with perf recommendations with stockpile Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3061) Create an AMQ upgrade acceptance test
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3061 Create an AMQ upgrade acceptance test Change By: Ryan Senior Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3061) Create an AMQ upgrade acceptance test
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3061 Create an AMQ upgrade acceptance test Change By: Ryan Senior Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2640) Use gzip compression for commands sent from the terminus
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2640 Use gzip compression for commands sent from the terminus Change By: Ryan Senior Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6642) Puppet::Agent class accepts Report but no way to use correct transaction_uuid
Title: Message Title Susan McNerney updated an issue Puppet / PUP-6642 Puppet::Agent class accepts Report but no way to use correct transaction_uuid Change By: Susan McNerney Sprint: PCP 2016-09-07, Hotlist FF 2016-10-05 , FF 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2640) Use gzip compression for commands sent from the terminus
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2640 Use gzip compression for commands sent from the terminus Change By: Ryan Senior Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3040) Implement bypassing the queue perf optimization
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3040 Implement bypassing the queue perf optimization Change By: Ryan Senior Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3062) Write up end-user docs with perf recommendations with stockpile
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3062 Write up end-user docs with perf recommendations with stockpile Change By: Ryan Senior Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3060) Make the concurrent-writes config "official"
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3060 Make the concurrent-writes config "official" Change By: Ryan Senior Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: SE 2016-10-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: SE 2016-10- 19 05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6703) Minor improvement to agent failover test (originally PUP-6383)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6703 Minor improvement to agent failover test (originally PUP-6383) Change By: Geoff Nichols Sprint: Windows 2016-09-21, AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Geoff Nichols Sprint: Windows 2016-09-21, AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Geoff Nichols Sprint: Windows 2016-09-21, AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-348) Facter should provide a convenient way to cache values
Title: Message Title Geoff Nichols updated an issue Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Geoff Nichols Sprint: Windows 2016-09-21, AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1356 External facts should be able to return structured data Change By: Geoff Nichols Sprint: Windows 2016-09-21, AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2777) Make sure stockpile tests have some coverage of the "no metadata" case
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2777 Make sure stockpile tests have some coverage of the "no metadata" case Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6476) Add Hocon support to Puppet
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3026) Merge cmd-proc-refactor to master
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3026 Merge cmd-proc-refactor to master Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2948) Deprecate obsolete ActiveMQ and DLO config
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2948 Deprecate obsolete ActiveMQ and DLO config Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2791) Test stockpile/store's error cases more thoroughly.
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2791 Test stockpile/store's error cases more thoroughly. Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2779) stockpile: satisfy ourselves that the durability approach is reliable enough, or adjust it
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2779 stockpile: satisfy ourselves that the durability approach is reliable enough, or adjust it Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2983) Ensure PDB + Stockpile is HUPable
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2983 Ensure PDB + Stockpile is HUPable Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2982) Create shorter command names for the stockpile metadata
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2982 Create shorter command names for the stockpile metadata Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3039) Stockpile metadata string length enforcement
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3039 Stockpile metadata string length enforcement Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3037) Find/remove ActiveMQ code no longer being used
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3037 Find/remove ActiveMQ code no longer being used Change By: Karen Van der Veer Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-348) Facter should provide a convenient way to cache values
Title: Message Title Geoff Nichols updated an issue Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Geoff Nichols Sprint: Windows AP 2016- 09 10 - 21 05 , AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6703) Minor improvement to agent failover test (originally PUP-6383)
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6703 Minor improvement to agent failover test (originally PUP-6383) Change By: Geoff Nichols Sprint: Windows AP 2016- 09 10 - 21 05 , AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6542 Group resource emits misleading change notification with auth_membership => false Change By: Geoff Nichols Sprint: Windows AP 2016- 09 10 - 21 05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Geoff Nichols Sprint: Windows AP 2016- 09 10 - 21 05 , AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1356 External facts should be able to return structured data Change By: Geoff Nichols Sprint: Windows AP 2016- 09 10 - 21 05 , AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Geoff Nichols Sprint: Windows AP 2016- 09 10 - 21 05 , AP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6542 Group resource emits misleading change notification with auth_membership => false Change By: Geoff Nichols Sprint: AP 2016- 10 11 - 05 02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1356 External facts should be able to return structured data Change By: Geoff Nichols Sprint: AP 2016- 10 09 - 05 21 , AP 2016- 09 10 - 21 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1503) Regression - facter no longer returns value for system_uptime on Window2012
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1503 Regression - facter no longer returns value for system_uptime on Window2012 Change By: Geoff Nichols Sprint: AP 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1446) Improve the windows user check in facter/acceptance/test/facts/window.rb
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1446 Improve the windows user check in facter/acceptance/test/facts/window.rb Change By: Geoff Nichols Sprint: AP 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Geoff Nichols Sprint: AP 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1492 FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016 Change By: Geoff Nichols Sprint: AP 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Moses Mendoza commented on FACT-1502 Re: acceptance: mount a tmpfs directory and check the fact this passed CI at https://jenkins.puppetlabs.com/view/agent-platform-triage/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-master/197/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6703) Minor improvement to agent failover test (originally PUP-6383)
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-6703 Minor improvement to agent failover test (originally PUP-6383) Change By: Moses Mendoza Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6703) Minor improvement to agent failover test (originally PUP-6383)
Title: Message Title Moses Mendoza commented on PUP-6703 Re: Minor improvement to agent failover test (originally PUP-6383) this was merged and had a successful CI run at https://jenkins.puppetlabs.com/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-stable/205/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-97) Initial increment for puppet strings and docs workflow
Title: Message Title
Lindsey Smith updated an issue
Puppet Strings / PDOC-97
Initial increment for puppet strings and docs workflow
Change By:
Lindsey Smith
Generated puppet references, for each .y release there is a tool that generates docsProblem is the embedded docs in the puppet repo are in different formatsGoal is that strings can cope with the worst of these formatsresource types and providers: change frequently, important to experienced users- current tooling is extremely brittle- done: you can point `puppet strings #{puppet dir} --json` at puppet core --> goes into updated versions of existing templates, which live in puppet-docs/lib-- output needs to be mostly the same-- comprehensive: updating the actual docstrings
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-97) Initial increment for puppet strings and docs workflow
Title: Message Title Lindsey Smith created an issue Puppet Strings / PDOC-97 Initial increment for puppet strings and docs workflow Issue Type: Epic Assignee: Unassigned Created: 2016/09/21 11:30 AM Fix Versions: PDOC 1.0.0 Priority: Critical Reporter: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received thi
Jira (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title Lindsey Smith commented on PDOC-85 Re: Handle the case of 4x functions and 3x stubs Nicholas Fagerlund believes this unnecessary and we'll fix it in the templates Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-97) Initial increment for puppet strings and docs workflow
Title: Message Title
Lindsey Smith updated an issue
Puppet Strings / PDOC-97
Initial increment for puppet strings and docs workflow
Change By:
Lindsey Smith
# Running from bundler in the docs team workflow, puppet strings can consume the puppet repo to produce JSON output for resource types/providers and functions# Confirm that JSON format is sufficient Generated puppet references, for each .y release there is a tool that generates docsProblem is the embedded docs in the puppet repo are in different formatsGoal is that strings can cope with the worst of these formatsresource types and providers: change frequently, important to experienced users- current tooling is extremely brittle- done: you can point `puppet strings #{puppet dir} --json` at puppet core --> goes into updated versions of existing templates, which live in puppet-docs/lib-- output needs to be mostly the same-- comprehensive: updating the actual docstrings
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-88) Create a test plan for ensuring strings support going forward
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-88 Create a test plan for ensuring strings support going forward Change By: Lindsey Smith Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-59) Improve behavior of Strings to support integration into Docs workflow
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-59 Improve behavior of Strings to support integration into Docs workflow Change By: Lindsey Smith Note: this epic covers precursor work to improving the utility of puppet strings for the puppet docs team. Remaining work required to be minimally useful to the docs team is tracked in PDOC-97. Potential beyond the initial increment is tracked in PDOC-TBD. The purpose of this epic is to allow the docs team to use Strings in order to document 4.x style functions. As part of supporting that goal, this epic will also contain tickets that are needed so that the docs team can integrate strings with their workflow. You can point Strings at a checkout of Puppet's core Ruby code, and get something fairly useful! But there are some problems still. I'm mostly focusing on JSON behavior for this epic; I haven't looked at the yardoc website it generates, and am not sure what I'd find if I did. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-98) Puppet string and Docs team potential future work
Title: Message Title Lindsey Smith created an issue Puppet Strings / PDOC-98 Puppet string and Docs team potential future work Issue Type: Epic Assignee: Unassigned Created: 2016/09/21 11:54 AM Priority: Normal Reporter: Lindsey Smith This epic collects potential future work around puppet strings to improve life for the puppet docs team. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-59) Improve behavior of Strings to support integration into Docs workflow
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-59 Improve behavior of Strings to support integration into Docs workflow Change By: Lindsey Smith Note: this epic covers precursor work to improving the utility of puppet strings for the puppet docs team. Remaining work required to be minimally useful to the docs team is tracked in PDOC-97. Potential beyond the initial increment is tracked in PDOC- TBD 98 .The purpose of this epic is to allow the docs team to use Strings in order to document 4.x style functions. As part of supporting that goal, this epic will also contain tickets that are needed so that the docs team can integrate strings with their workflow. You can point Strings at a checkout of Puppet's core Ruby code, and get something fairly useful! But there are some problems still. I'm mostly focusing on JSON behavior for this epic; I haven't looked at the yardoc website it generates, and am not sure what I'd find if I did. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-59) Improve behavior of Strings to support integration into Docs workflow
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-59 Improve behavior of Strings to support integration into Docs workflow Change By: Lindsey Smith * Note: * this epic covers precursor work to improving the utility of puppet strings for the puppet docs team. Remaining work required to be minimally useful to the docs team is tracked in PDOC-97. Potential beyond the initial increment is tracked in PDOC-98.The purpose of this epic is to allow the docs team to use Strings in order to document 4.x style functions. As part of supporting that goal, this epic will also contain tickets that are needed so that the docs team can integrate strings with their workflow. You can point Strings at a checkout of Puppet's core Ruby code, and get something fairly useful! But there are some problems still. I'm mostly focusing on JSON behavior for this epic; I haven't looked at the yardoc website it generates, and am not sure what I'd find if I did. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-98) Puppet strings for the Docs team potential future work
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-98 Puppet strings for the Docs team potential future work Change By: Lindsey Smith Summary: Puppet string and strings for the Docs team potential future work Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-97) Initial increment for puppet strings and docs workflow
Title: Message Title
Lindsey Smith updated an issue
Puppet Strings / PDOC-97
Initial increment for puppet strings and docs workflow
Change By:
Lindsey Smith
This epic tracks the work required for puppet strings to be minimally useful to the Puppet docs team.Potential future work for puppet strings and improving its utility for the docs team is tracked in PDOC-98*Acceptance criteria:* # Running from bundler in the docs team workflow, puppet strings can consume the puppet repo to produce JSON output for resource types/providers and functions# Confirm Confirmation that JSON format is sufficient Raw notes to be cleaned up later:{quote} Generated puppet references, for each .y release there is a tool that generates docsProblem is the embedded docs in the puppet repo are in different formatsGoal is that strings can cope with the worst of these formatsresource types and providers: change frequently, important to experienced users- current tooling is extremely brittle- done: you can point `puppet strings #{puppet dir} --json` at puppet core --> goes into updated versions of existing templates, which live in puppet-docs/lib-- output needs to be mostly the same-- comprehensive: updating the actual docstrings {quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-2769) specify how 4.x function api code can get caller / source location
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2769 specify how 4.x function api code can get caller / source location Change By: Henrik Lindberg Sprint: PDS 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-83) Define a proper JSON schema for strings
Title: Message Title Craig Gomes updated an issue Puppet Strings / PDOC-83 Define a proper JSON schema for strings Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5834) Handle extended data in the catalog
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5834 Handle extended data in the catalog Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6592) acceptance: Sensitive data
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6592 acceptance: Sensitive data Change By: Craig Gomes Sprint: Language 2016-09-07, PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6705 Add Sensitive type to Puppet Serialization Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6291) Add 'abs' support to Numeric.new
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6682) $settings leaks symbols into manifests
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6682 $settings leaks symbols into manifests Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6706) Add Binary type to Puppet Serialization
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6706 Add Binary type to Puppet Serialization Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: Craig Gomes Sprint: Language 2016-09-07, PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6685) Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6685 Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds Change By: Craig Gomes Sprint: Language 2016-09-07, PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5831) Add a Binary type and runtime object
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5831 Add a Binary type and runtime object Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6689) Timespan and Timestamp should inherit from Scalar, not from Numeric
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6689 Timespan and Timestamp should inherit from Scalar, not from Numeric Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Craig Gomes Sprint: Language 2016-06-01, Language 2016-06-15, Language 2016-06-29, PDS 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6592) acceptance: Sensitive data
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6592 acceptance: Sensitive data Change By: Craig Gomes Sprint: Language 2016-09-07, PDS 2016-09-21, PDS 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5908) Implement a PCore MsgPack Serializer
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Craig Gomes Sprint: Language 2016-06-29, PDS 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Craig Gomes commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server lindsey.smith to follow up on concerns around changes to Hiera. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Craig Gomes updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Craig Gomes Sprint: PDS 2016-10- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1810) Deprecate referencing classes with an initial capital letter
Title: Message Title Craig Gomes assigned an issue to Henrik Lindberg Puppet / PUP-1810 Deprecate referencing classes with an initial capital letter Change By: Craig Gomes Assignee: Andrew Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
