Jira (FACT-1835) Add component B
Title: Message Title Enis Inan created an issue Facter / FACT-1835 Add component B Issue Type: Bug Assignee: Unassigned Created: 2018/03/13 9:24 PM Priority: Normal Reporter: Enis Inan Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more
Jira (FACT-1836) Add component C
Title: Message Title Enis Inan created an issue Facter / FACT-1836 Add component C Issue Type: Bug Assignee: Unassigned Created: 2018/03/13 9:24 PM Priority: Normal Reporter: Enis Inan Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more
Jira (FACT-1834) Add component A
Title: Message Title Enis Inan created an issue Facter / FACT-1834 Add component A Issue Type: Bug Assignee: Unassigned Created: 2018/03/13 9:24 PM Priority: Normal Reporter: Enis Inan Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: Alex Dreyer Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-379) Accept ssh key as a string
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-379
Accept ssh key as a string
Change By:
Alex Dreyer
Release Notes Summary:
The private-key config setting accepts a hash with {{key-data}} in addition to a string with the path to the key.
Release Notes:
New Feature
Fix Version/s:
Bolt Next
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-377) Add the ability to pass inventory via environment variables
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-377 Add the ability to pass inventory via environment variables Change By: Alex Dreyer Release Notes Summary: This allows inventory data to be passed to bolt as an environment variable instead of a file. This allows configuring target specific config when calling bolt programmatically without writing a file. Release Notes: New Feature Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8468) Failed to show puppet classes: 500 Api Request
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8468 Failed to show puppet classes: 500 Api Request Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Kate Lopresti commented on BOLT-356 Re: Option to ignore local tasks when using pcp transport Added to release notes. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-381) Move to Ruby 2.1 as minimum supported version
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-381 Move to Ruby 2.1 as minimum supported version Issue Type: Improvement Assignee: Unassigned Created: 2018/03/13 4:55 PM Fix Versions: BOLT 0.18.0 Priority: Normal Reporter: Michael Smith Now that we ship Bolt packages on all platforms that ship with Ruby 2.0, move to Ruby 2.1 as the minimum supported version. Plan to do this on the next breaking version bump. That allows us to cleanup several areas: using Exception#cause in Bolt::PAL using YAML#load instead of YAML#safe_load Add Comment
Jira (PDOC-231) Unbreak resource_api handler
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-231 Unbreak resource_api handler Issue Type: Bug Assignee: Unassigned Created: 2018/03/13 4:55 PM Priority: Normal Reporter: Eric Putnam I made some changes to the resource_api handler based on the acceptance tests, but I should have changed the test instead. This is for that work. More details to come. Maybe. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Kate Lopresti commented on BOLT-167 Re: I want to pass a pql query instead of a list of nodes. Added to release notes. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-373) Update Puppet for new core functions
Title: Message Title Kate Lopresti commented on BOLT-373 Re: Update Puppet for new core functions Added to release notes. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Melissa Stone updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Melissa Stone QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-920) Add catalog application information to report
Title: Message Title Melissa Stone updated an issue Puppet / PUP-920 Add catalog application information to report Change By: Melissa Stone Release Notes Summary: Time metrics recorded in the run report now include the time it takes to convert the catalog, plugin sync, generate facts, retrieve nodes, and evaluate transactions. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-920) Add catalog application information to report
Title: Message Title Melissa Stone updated an issue Puppet / PUP-920 Add catalog application information to report Change By: Melissa Stone QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Melissa Stone updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Melissa Stone Release Notes Summary: Time metrics recorded in the run report now include the time it takes to apply the catalog. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Josh Cooper Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Josh Cooper commented on PUP-6343 Re: Add catalog apply time to Puppet::Util::Metric "time" category Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/7611f1b3f150460df5487f1fbf3b13d6df8a0f44 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-373) Update Puppet for new core functions
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-373 Update Puppet for new core functions Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-920) Add catalog application information to report
Title: Message Title Josh Cooper commented on PUP-920 Re: Add catalog application information to report Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/7611f1b3f150460df5487f1fbf3b13d6df8a0f44 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-920) Add catalog application information to report
Title: Message Title Josh Cooper commented on PUP-920 Re: Add catalog application information to report Melissa Stone could you add release notes? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-373) Update Puppet for new core functions
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-373 Update Puppet for new core functions Change By: Michael Smith Release Notes Summary: Adds new core functions to the Bolt Plan language : empty, keys, values, join, flatten, length. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Change By: Michael Smith Release Notes Summary: Bolt will now defer to Orchestrator on task metadata when running tasks via PCP. In practice this means that invalid parameters will be reported for each target rather than on the run_task invocation itself. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Change By: Michael Smith Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-366) Target cannot be used to construct a copy
Title: Message Title Michael Smith commented on BOLT-366 Re: Target cannot be used to construct a copy Accidentally broke private-key, which is being fixed as part of work on BOLT-379. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-373) Update Puppet for new core functions
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-373 Update Puppet for new core functions Change By: Michael Smith Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Melissa Stone updated an issue Puppet / PUP-6344 metrics.time.total does not correlate to time reported in log Change By: Melissa Stone Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Adam Bottchen commented on PUP-6343 Re: Add catalog apply time to Puppet::Util::Metric "time" category The main thing they wanted was to be able to extract the application time from the metrics hash. They were working around that by regex'ing out the time from self.logs.last.message, which just seemed wrong. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Adam Bottchen commented on PUP-6343 Re: Add catalog apply time to Puppet::Util::Metric "time" category That would fix the problem the customer originally raised: Notice: Applied catalog in 4.74 seconds ... Catalog application: 4.74 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Melissa Stone commented on PUP-6343 Re: Add catalog apply time to Puppet::Util::Metric "time" category With the additions in the PR referenced above, we now have a report summary that looks like this: $ time sudo bundle exec ./bin/puppet agent -t --summarize Info: Using configured environment 'workstation_production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Warning: Facter: Fact resolution fact='profiles', resolution='' resolved to an invalid value: Expected 2017-09-08T17:03:53+00:00 to be one of [Integer, Float, TrueClass, FalseClass, NilClass, String, Array, Hash], but was DateTime Warning: Facter: Fact resolution fact='puppet_classes', resolution='' resolved to an invalid value: Expected all to be one of [Integer, Float, TrueClass, FalseClass, NilClass, String, Array, Hash], but was Symbol Info: Caching catalog for melissa-c02mq17dfd57 Info: Applying configuration version '1520981537' Notice: Applied catalog in 4.74 seconds Changes:
Jira (PDB-3867) Bump versions, push directly, and tag (PuppetDB 5.2.1)
Title: Message Title Geoff Nichols assigned an issue to Rob Browning PuppetDB / PDB-3867 Bump versions, push directly, and tag (PuppetDB 5.2.1) Change By: Geoff Nichols Assignee: Russell Mull Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3866) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.1)
Title: Message Title Geoff Nichols assigned an issue to Rob Browning PuppetDB / PDB-3866 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.1) Change By: Geoff Nichols Assignee: Russell Mull Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3865) Merge-up, branch, and create pipelines (PuppetDB 5.2.1)
Title: Message Title Geoff Nichols assigned an issue to Rob Browning PuppetDB / PDB-3865 Merge-up, branch, and create pipelines (PuppetDB 5.2.1) Change By: Geoff Nichols Assignee: Russell Mull Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3869) Update winston (PuppetDB 5.2.1)
Title: Message Title Geoff Nichols assigned an issue to Rob Browning PuppetDB / PDB-3869 Update winston (PuppetDB 5.2.1) Change By: Geoff Nichols Assignee: Russell Mull Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3868) Check builds, promote to PE (PuppetDB 5.2.1)
Title: Message Title Geoff Nichols assigned an issue to Rob Browning PuppetDB / PDB-3868 Check builds, promote to PE (PuppetDB 5.2.1) Change By: Geoff Nichols Assignee: Russell Mull Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8501) Switch to using multi_json
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8501 Switch to using multi_json Change By: Maggie Dreyer Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8485) Cached failed confine lookups
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8485 Cached failed confine lookups Change By: Maggie Dreyer Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8487) Eliminate use of MethodHelper
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8487 Eliminate use of MethodHelper Change By: Maggie Dreyer Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Melissa Stone commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log Yup, that is exactly why I opened PUP-8511 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3848) Release PuppetDB 5.1.z(Platform 5.3.6 - 2018-04-09)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3848 Release PuppetDB 5.1.z(Platform 5.3.6 - 2018-04-09) Change By: Jeff Yarnell Release PDB in preparation for the Puppet Platform 5.3.6 release [ https://confluence.puppetlabs.com/x/tYfaCQ ]*Stop Ship (code freeze)*: Monday, April 9*Ready to Ship:* Monday, April 16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3848) Release PuppetDB 5.1.z(Platform 5.3.6 - 2018-04-09)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3848 Release PuppetDB 5.1.z(Platform 5.3.6 - 2018-04-09) Change By: Jeff Yarnell Sprint: Data Platform 2018- 03 04 - 28 11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title
Charlie Sharpsteen commented on PUP-6344
Re: metrics.time.total does not correlate to time reported in log
Total here is simply the sum of all the time metrics we've recorded
If it truly is a sum, then it could be more than the actual total time as the following code:
Puppet.profile('outer') do
Puppet.profiler('inner') do
...
end
end
Would double-count the time taken for the inner operation since that time is also measured as part of the outer operation.
Add Comment
This message was sent by Atlassian JIRA
Jira (PDB-3869) Update winston (PuppetDB 5.2.1)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3869 Update winston (PuppetDB 5.2.1) Change By: Jeff Yarnell Sprint: Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3868) Check builds, promote to PE (PuppetDB 5.2.1)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3868 Check builds, promote to PE (PuppetDB 5.2.1) Change By: Jeff Yarnell Sprint: Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3866) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.1)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3866 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.1) Change By: Jeff Yarnell Sprint: Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3867) Bump versions, push directly, and tag (PuppetDB 5.2.1)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3867 Bump versions, push directly, and tag (PuppetDB 5.2.1) Change By: Jeff Yarnell Sprint: Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3865) Merge-up, branch, and create pipelines (PuppetDB 5.2.1)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3865 Merge-up, branch, and create pipelines (PuppetDB 5.2.1) Change By: Jeff Yarnell Sprint: Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3875) Start shipping Puppet 6 nightlies
Title: Message Title Jeff Yarnell created an issue PuppetDB / PDB-3875 Start shipping Puppet 6 nightlies Issue Type: Task Assignee: Unassigned Created: 2018/03/13 3:20 PM Priority: Normal Reporter: Jeff Yarnell As we prepare for the release of Puppet Platform 6, you may want to start shipping puppet6 nightlies. There are several small steps you should take to make sure your builds end up in the right place. In ext/build-defaults.yaml: For any branches targeting puppet6: - update `nonfinal_repo_name` to 'puppet6-nightly' - update `repo_name` to 'puppet6' (not needed until we ship for real, but won't hurt anything) For any branches still targeting puppet5: - remove `nonfinal_repo_link_target` - the 'puppet-nightly' directory is intended to be a symlink to the latest major version directory (soon to be 'puppet6-nightly', currently 'puppet5-nightly'). Without this change, anything still shipping puppet5 nightlies will overwrite the symlink. A similar change will be needed for `repo_link_target`, but not until we start shipping puppet6 for real. This should apply to anything shipping nightlies, which (as far as I know) is just puppet-agent, puppetserver, puppetdb, and pdk. If you have any questions or run into trouble, please let the RE team know (either by email or in the 'release-new' HipChat room).
Jira (PDB-3740) Better JDK version checking
Title: Message Title Kevin Häfeli commented on PDB-3740 Re: Better JDK version checking 5 months later, updated to puppetdb forge module 6.0.2. run into the same error again Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Melissa Stone commented on PUP-6343 Re: Add catalog apply time to Puppet::Util::Metric "time" category I assume you meant to link PUP-920, but no, this work is not covered by that ticket. I've added that work for this ticket to https://github.com/puppetlabs/puppet/pull/6677 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Melissa Stone updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Melissa Stone Sub-team: Coremunity Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-6344 metrics.time.total does not correlate to time reported in log Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Melissa Stone commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log Total here is simply the sum of all the time metrics we've recorded, so it doesn't actually report the total time. There are likely functions that aren't wrapped in a time block. I'm looking at fixing this The first part of this ticket is a dup of PUP-6343, but the second is covered by PUP-8511. I'm going to close PUP-8511 in favor of this one, but keep PUP-6343 open to cover the work to add the catalog application time to the report. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4937) puppet agent runs report time spent applying catalogue but omit total time spent
Title: Message Title Melissa Stone commented on PUP-4937 Re: puppet agent runs report time spent applying catalogue but omit total time spent We do include the total time in the report, but we don't add a notify during the puppet run. If you pass in the --summarize flag, you'll get a nice print out of the metrics we've gathered for the report. It's also stored in the reportdir, which you can find by running puppet config print reportdir. Usually this is something like /opt/puppet/cache/reports. However, I have a strong hunch the total time we report isn't actually accurate. That issue you can follow in PUP-8511. It was also reported in PUP-6344. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-379) Accept ssh key as a string
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-379 Accept ssh key as a string Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-374) Update bolt-vanagon to ship latest platforms
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-374 Update bolt-vanagon to ship latest platforms Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-343) Document Bolt with Orchestrator
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-343 Document Bolt with Orchestrator Change By: Michael Smith Assignee: Michael Smith Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3647) Puppet stores files forever in state.yaml
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-3647 Puppet stores files forever in state.yaml Change By: Eric Sorenson Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8232) Re-add the puppet facts upload face and REST facts terminus
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8232 Re-add the puppet facts upload face and REST facts terminus Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-380) Support ed25519 out-of-the-box
Title: Message Title Michael Smith commented on BOLT-380 Re: Support ed25519 out-of-the-box net-ssh-krb is a similar issue for password-less support via Kerberos. That may be slightly more complex if we need to have system libraries installed as well. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-380) Support ed25519 out-of-the-box
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-380 Support ed25519 out-of-the-box Issue Type: Improvement Assignee: Unassigned Created: 2018/03/13 1:33 PM Priority: Normal Reporter: Michael Smith net-ssh requires several extra libraries for ed25519 support. Without them, users see ``` 2018-02-26T13:59:32.131096 WARN Net::SSH: ignoring unimplemented key:unsupported key type `ssh-ed25519' net-ssh requires the following gems for ed25519 support: rbnacl (>= 3.2, < 5.0) rbnacl-libsodium, if your system doesn't have libsodium installed. bcrypt_pbkdf (>= 1.0, < 2.0) See https://github.com/net-ssh/net-ssh/issues/478 for more information Gem::MissingSpecError : "Could not find 'rbnacl' (< 5.0, >= 3.2.0) among 86 total gem(s) ``` Add Comment
Jira (BOLT-380) Support ed25519 out-of-the-box
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-380 Support ed25519 out-of-the-box Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: Nick Lewis Release Notes Summary: The --query flag can now be used to target nodes based on a PuppetDB query. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8545) puppet 5/ruby 2.4 can't handle invalid plists
Title: Message Title
Eric Sorenson commented on PUP-8545
Re: puppet 5/ruby 2.4 can't handle invalid plists
(Because Jira is SOooOO awesome, only single line code samples can be formatted with double-curly braces. Multiline samples need to get wrapped in {code} tags)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-8545) puppet 5/ruby 2.4 can't handle invalid plists
Title: Message Title Clay Caviness commented on PUP-8545 Re: puppet 5/ruby 2.4 can't handle invalid plists I fail at formatting here. You get the idea. It seems to be a pretty simple fix: https://github.com/puppetlabs/puppet/pull/6733 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title
Melissa Stone commented on PUP-8443
Re: Topscope 'environment' can become nil when setting node parameters in a custom terminus
I've manually validated this. First I verified I could reproduce this issue in puppet-agent 5.3.4, and then validated it was fixed in puppet-agent 5.4.0.489.gc5e2622 I tested by changing the `find` method in lib/puppet/indirector/node/plain.rb
def find(request)
node = super
node.environment = request.environment
node.environment = 'foo'
facts = request.options[:facts].is_a?(Puppet::Node::Facts) ? request.options[:facts] : nil
node.fact_merge(facts)
node.parameters['evironment'] = 'bar'
node
end
running {{puppet apply -e " file {'/tmp/foo': ensure => present, content => \"environment is '$::environment'\n\" } "}} and then verifying the contents of /tmp/foo puppet-agent 5.3.4:
# cat /tmp/foo
Jira (PUP-8545) puppet 5/ruby 2.4 can't handle invalid plists
Title: Message Title
Clay Caviness commented on PUP-8545
Re: puppet 5/ruby 2.4 can't handle invalid plists
This happens because puppet prefetches resources for the launchd service provider. The code is triggered if there's any malformed plists it the /Library/LaunchDaemons directory, whether they're managed my puppet or not. This only triggers a warning; puppet continues processing. Trimmed debug output: {{Debug: Prefetching launchd resources for service [...] Debug: Reading launchd plist /Library/LaunchDaemons/good.plist Debug: Reading launchd plist /Library/LaunchDaemons/badcomment.plist }}Debug: Failed with CFFormatError on /Library/LaunchDaemons/badcomment.plist: # Line: 10 Position: 383 Last 80 unconsumed characters: > Debug: Plist /Library/LaunchDaemons/badcomment.plist ill-formatted, converting with plutil Debug: Executing: '/usr/bin/plutil -convert xml1 -o /dev/stdout /Library/LaunchDaemons/badcomment.plist' Warning: Cannot read file /Library/LaunchDaemons/badcomment.plist; Puppet is skipping it.\nDetails: Execution of '/usr/bin/plutil -convert xml1 -o /dev/stdout /Library/LaunchDaemons/badcomment.plist' returned 1: {{ KeepAlive}} {{ }} {{ Label}} {{ badcomment}} {{ ProcessType}} {{ Background}} {{ ProgramArguments}} {{ }} {{ /bin/true}} {{ }} {{ RunAtLoad}} {{ }} /dev/stdout: Operation not supported
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
Jira (PUP-8545) puppet 5/ruby 2.4 can't handle invalid plists
Title: Message Title Eric Sorenson commented on PUP-8545 Re: puppet 5/ruby 2.4 can't handle invalid plists Clay Caviness thanks for the report - what is the puppet code that triggers this situation? Are you managing the plist directly or is this through a service resource? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8486) Warning for undefined variables is slow in jruby
Title: Message Title Patrick Carlisle commented on PUP-8486 Re: Warning for undefined variables is slow in jruby It seems worth it to me. I don't like having it in one more place either but it would probably be pretty small. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: Nick Lewis Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8545) puppet 5/ruby 2.4 can't handle invalid plists
Title: Message Title Clay Caviness created an issue Puppet / PUP-8545 puppet 5/ruby 2.4 can't handle invalid plists Issue Type: Bug Assignee: Unassigned Created: 2018/03/13 11:57 AM Priority: Normal Reporter: Clay Caviness Puppet Version: 5.4.0 Puppet Server Version: n/a OS Name/Version: macOS 10.13.3 Puppet 5.4.0 using ruby 2.4.3 can't handle invalid plists. If a plist contains and invalid comment (e.g., a comment with '–' in the text), CFPropertyList will fail to parse it, passing it on to a shell out to `plutil -convert xml1 -o /dev/stdout`. However, it seems some subsystem (I believe it may be ruby 2.4) doesn't allow operations on `/dev/stdout` Warning: Cannot read file /Library/LaunchDaemons/badcomment.plist; Puppet is skipping it.\nDetails: Execution of '/usr/bin/plutil -convert xml1 -o /dev/stdout /Library/LaunchDaemons/badcomment.plist' returned 1: Warning: Cannot read file /Library/LaunchDaemons/badcomment.plist; Puppet is skipping it.\n [...] /dev/stdout: Operation not supported To reproduce, add a comment containing '–' to any plist in /Library/LaunchDaemons, then run puppet. Desired Behavior: Puppet should handle the malformed plist and successfully call plutil. Actual Behavior: After CFPropertyList fails, the plutil call also fails. Add Comment
Jira (PUP-8542) document that the property 'target' for provider 'yumrepo' does not work
Title: Message Title Josh Cooper commented on PUP-8542 Re: document that the property 'target' for provider 'yumrepo' does not work Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/5ead1e3071a51db2998a0e9d82726ed059da2720 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1547) Create a Windows binary facter gem
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Facter / FACT-1547 Create a Windows binary facter gem Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1547) Create a Windows binary facter gem
Title: Message Title Sean McDonald updated an issue Facter / FACT-1547 Create a Windows binary facter gem Change By: Sean McDonald Sprint: Platform OS Ready for Eng. Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8232) Re-add the puppet facts upload face and REST facts terminus
Title: Message Title Eric Delaney commented on PUP-8232 Re: Re-add the puppet facts upload face and REST facts terminus Tested on agent 5.5.x SHA=c5e26226d26f78370f7d00d72b016cb4935bd15d SERVER_VERSION=5.2.1.master.SNAPSHOT.2018.03.13T0952 SERVER [root@cexia0r72jijvdt opt]# sum ./puppetlabs/server/data/puppetserver/yaml/facts/igo8i10m25ex77b.delivery.puppetlabs.net.yaml 5395612 AGENT [root@igo8i10m25ex77b ~]# puppet facts upload Notice: Uploading facts for 'igo8i10m25ex77b.delivery.puppetlabs.net' to: 'cexia0r72jijvdt.delivery.puppetlabs.net' SERVER [root@cexia0r72jijvdt opt]# head ./puppetlabs/server/data/puppetserver/yaml/facts/igo8i10m25ex77b.delivery.puppetlabs.net.yaml --- !ruby/object:Puppet::Node::Facts
Jira (PUP-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Melissa Stone QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2172) Add exceptions to http_proxy_{port,host}
Title: Message Title
James Ralston commented on PUP-2172
Re: Add exceptions to http_proxy_{port,host}
I'm re-opening this ticket, because I believe the severity of the problem hasn't been fully appreciated. Any security-competent site that requires outbound HTTP[S] traffic to use a network proxy will have configured the proxy to deny all requests for internal resources. (Otherwise, internal users can bypass internal network ACLs by routing requests through the proxy.) This means that any application that is proxy-aware must implement an exception list for the proxy. Without this exception list, the application is essentially offering its users two choices:
You can access foreign resources, but not local resources.
You can access local resources, but not foreign resources.
We see this in the applications that rely on the curl-style (http_proxy, https_proxy, and no_proxy) environment variables. E.g.:
$ set | grep proxy
http_proxy=http://proxy.example.org:8080
https_proxy=http://proxy.example.org:8080
no_proxy=localhost,.example.org
The no_proxy setting is not optional: without this, applications will not be able to access local resources. As a real-world example of just how critical the no_proxy list is, consider this example:
package { 'r10k':
ensure => present,
provider => puppet_gem,
Jira (PUP-8232) Re-add the puppet facts upload face and REST facts terminus
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8232 Re-add the puppet facts upload face and REST facts terminus Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8542) document that the property 'target' for provider 'yumrepo' does not work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8542 document that the property 'target' for provider 'yumrepo' does not work Change By: Eric Delaney Release Notes Summary: The yumrepo provider contains the property 'target' which does not work. We have removed the description for the property so it will no longer appear be enabled in the documentation a future release and should not be used . Release Notes: Bug Fix Known Issue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8481) Load the major part of pcore types statically instead of per environment
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8481 Load the major part of pcore types statically instead of per environment Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8494) Issue based errors are formatted too early and arguments are lost.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8494 Issue based errors are formatted too early and arguments are lost. Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8439) Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6702) Windows service in Paused state cannot be managed
Title: Message Title Michael Smith commented on PUP-6702 Re: Windows service in Paused state cannot be managed The pxp-agent issue causing it to be suspended in the first place is being addressed in PA-1850. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8542) document that the property 'target' for provider 'yumrepo' does not work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8542 document that the property 'target' for provider 'yumrepo' does not work Change By: Eric Delaney Remove Change documentation about the 'target' property for the 'yumrepo' providerThe 'target' property of the yumrepo provider does not work. To make it work would take a bit of work, which we want to do, but it would be best to wait until we've split the provider out of puppet. This ticket is to just remove change the documentation for 'target' for now and later we'll want to address PUP-2782 to make 'target' work correctly. "The target parameter will be enabled in a future release and should not be used." Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-8542) document that the property 'target' for provider 'yumrepo' does not work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8542 document that the property 'target' for provider 'yumrepo' does not work Change By: Eric Delaney Acceptance Criteria: 'target' property is described as "The target parameter will be enabled in a future release and should not longer document be used." Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8542) document that the property 'target' for provider 'yumrepo' does not work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8542 document that the property 'target' for provider 'yumrepo' does not work Change By: Eric Delaney Summary: document that the property 'target' for provider ' yumrepo property target as it ' does not work Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8542) document that the property for yumrepo property target as it does not work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8542 document that the property for yumrepo property target as it does not work Change By: Eric Delaney Summary: remove documentation document that the property for yumrepo property target as it does not work Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8541 Hiera lookup must hard fail on invalid YAML Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8541) Hiera lookup must hard fail on invalid YAML
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8541 Hiera lookup must hard fail on invalid YAML Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8501) Switch to using multi_json
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8501 Switch to using multi_json Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Michael Smith It's common to want to support boolean and integer types, which currently require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time.Handling for different target types:- If String is assignable to the type specified in the plan do not attempt to parse the value.- If String is not assignable to the type specified attempt to parse it as JSON and pass it on to puppet. If it cannot be parsed raise a useful error.Test common Data types (including that Data gets a string). Also Variant[String, ...]. Optional should not error. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Michael Smith It's common to want to support boolean and integer types, which currently require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time.Handling for different target types:- If String is assignable to the type specified in the plan do not attempt to parse the value.- If String is not assignable to the type specified attempt to parse it as JSON and pass it on to puppet. If it cannot be parsed raise a useful error.Test common Data types (including that Data gets a string). Also Variant[String, ...]. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and
Jira (PUP-8498) No title provided and "foo" is not a valid resource reference
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8498 No title provided and "foo" is not a valid resource reference Change By: Josh Cooper Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Michael Smith It's common to want to support boolean and integer types, which currently require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time.Handling for different target types:- If String is assignable to the type specified in the plan is assignable to String do not attempt to parse the value.- If the type specified String is not assignable to String the type specified attempt to parse it as JSON and pass it on to puppet. If it cannot be parsed raise a useful error.Test common Data types (including that Data gets a string). Also Variant[String, ...]. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google
