Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1337 Make .filter_set called on a ResultSet return a ResultSet Change By: Lucy Wyman Assignee: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.24067.1559087580560%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-267) Grouping of parameters
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-267 Grouping of parameters Ewoud Kohl van Wijngaarden sorry for the delay in responding to this request! Could you confirm if this is still something you would find useful and if so, provide a concrete example of some code that makes use of a parameter grouping syntax? If this is something that would require extensive customization to YARD, we probably won't have the bandwidth to address it any time soon, but given an example we might be able to come up with something that would work for you. Thanks! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.275678.1536876963000.23924.1559084700305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1304) Config set on target-lookups targets does not override inherited config
Title: Message Title Cas Donoghue commented on BOLT-1304 Re: Config set on target-lookups targets does not override inherited config It appears that this only affects the puppetdb plugin and is solved with https://github.com/puppetlabs/bolt/pull/992 Verified config is inherited correctly for both terraform and puppetdb as implemented in BOLT-1264 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308766.1557939563000.23918.1559084406886%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet
Title: Message Title Reid Vandewiele updated an issue Puppet Task Runner / BOLT-1337 Make .filter_set called on a ResultSet return a ResultSet Change By: Reid Vandewiele Summary: Make . filter filter_set called on a ResultSet return a ResultSet 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.23897.1559083920063%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1337) Make .filter called on a ResultSet return a ResultSet
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-1337
Make .filter called on a ResultSet return a ResultSet
Change By:
Reid Vandewiele
This should work. It doesn’t, because filter called on a ResultSet returns an array.{code}# Identify those nodes that need to be rebooted.$reboot_targets = $patch_results.ok_set.filter |$result| { $result['reboot_flag'] == true}.targets{code}Make a new method, {{. filter filter_set }} , which when called on a ResultSet return returns a ResultSet. Making a new method instead of just fixing {{.filter}} because of concerns over breaking / backwards incompatible changes.
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
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-262 Puppet Strings output of Puppet types is inconsistent with puppet doc Going to create an epic and break this down into smaller individual tickets Change By: Jesse Scott Issue Type: Bug Story 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. To view this discussion on the web visit
Jira (PDOC-256) REFERENCE.md in CI
Title: Message Title Jesse Scott assigned an issue to Jesse Scott Puppet Strings / PDOC-256 REFERENCE.md in CI Change By: Jesse Scott Assignee: Eric Putnam Jesse Scott 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.258793.1528149696000.23689.1559081160684%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-256) REFERENCE.md in CI
Title: Message Title Jesse Scott assigned an issue to Unassigned Puppet Strings / PDOC-256 REFERENCE.md in CI Change By: Jesse Scott Assignee: Jesse Scott 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.258793.1528149696000.23692.1559081160825%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1304) Config set on target-lookups targets does not override inherited config
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1304 Config set on target-lookups targets does not override inherited config Change By: Cas Donoghue Assignee: Lucy Wyman Cas Donoghue 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308766.1557939563000.23669.1559080800436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Alex Dreyer Comment: Is this about part of the module path User has this Bolt project folder:`C:\DATA\workshop` with a bolt.yaml in itand subsequently the modulepath becomes c:/data/workshop/modulesHowever no tasks/plans are ever found there.If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it worksBolt needs to be completely case insensitive on Windows, otherwise this breaks everything 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.23577.1559078100975%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Alex Dreyer Bolt won’t handle folder names with one or more uppercase characters in the name incorrectly, when they are part of the modulepath. I encountered this while doing a Bolt Workshop at KPN.If the modulepath has a capitalized foldername in it, not Tasks or Plans are found in that module. It is as if the module is not there. User has this Bolt project folder:`C:\DATA\workshop` with a bolt.yaml in itand subsequently the modulepath becomes c:/data/workshop/modulesHowever no tasks/plans are ever found there.If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it worksBolt needs to be completely case insensitive on Windows, otherwise this breaks everything 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
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows Is this about part of the module path User has this Bolt project folder: `C:\DATA\workshop` with a bolt.yaml in it and subsequently the modulepath becomes c:/data/workshop/modules However no tasks/plans are ever found there. If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it works Bolt needs to be completely case insensitive on Windows, otherwise this breaks everything 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.23575.1559078100882%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1924) Investigate if FFI works on AIX/Solaris and Solaris-sparc
Title: Message Title Sebastian Miclea commented on FACT-1924 Re: Investigate if FFI works on AIX/Solaris and Solaris-sparc https://gist.github.com/sebastian-miclea/9f6f8ba0ba733c718e96251f2dadb7ae 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308706.1557915892000.23508.1559077320178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1341) Support version 4 terraform state files in terraform inventory plugin
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1341 Support version 4 terraform state files in terraform inventory plugin Change By: Nick Lewis Assignee: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310025.155865782.23217.1559074560110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4366) fix since/only problems
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4366 fix since/only problems Change By: Rob Browning Team: PuppetDB 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308095.1557430219000.23121.1559072040235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Molly Waggett commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo okay, that sounds like a cross-that-bridge-when-we-get-there scenario to me. I don't see why that couldn't go into the puppet-enterprise-tools repo, but no use arguing about hypotheticals. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22935.1559068260393%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Lewis commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Molly Waggett Yeah that's where we want cd4pe packages to go, because it's an enterprise-only feature that doesn't ship in PE. But if we ever included a new open source project in the PE tarball (as opposed to a separate download), we wouldn't want it to be in the pe-tools repo. So we would then be forced to put it in the Puppet platform repos instead, where it doesn't belong. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22898.1559067840389%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Walker commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Yes, the install instructions should point to the new repo which works for everyone and doesn't break anything for anyone. We can provide notes for OSS users that if they want a repo with puppet-agent in it as well they can use the existing repo. If that note is ignored it doesn't break anything for anyone. Worst case scenario is that the user would end up with two puppet repos. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22881.1559067721195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Alex Dreyer commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo My understanding from the original meeting was that we wanted a single repo that we could document for all users to prevent PE users from accidentally adding the FOSS puppet platform repo. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22844.1559067420673%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Molly Waggett commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Why wouldn't we want them in puppet-enterprise-tools? I was under the impression that this is EXACTLY where we'd want to put such packages (e.g. cd4pe packages that I hear are coming). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22834.1559067360368%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Jorie Tappa Sprint: Coremunity 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.22804.1559067120763%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Lewis commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo We may have packages that aren't part of the "Puppet platform" but which are shipped in PE. In that case, we wouldn't want them in the Puppet platform repos and we also wouldn't want them in the puppet-enterprise-tools repo. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22776.1559066941225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Molly Waggett commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Nick Lewis What are the use-cases for these two repos? I thought this new repo was "non-'Puppet platform' packages, which are also compatible with PE". 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22764.1559066820900%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Lewis commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo The name isn't the question. The question is the purpose. Is this repo meant for PE users or is it meant for all users? I think we will eventually need to have two repos, one that is "non-'Puppet platform' packages" and one that is "PE-compatible packages". Should we create the second repo now or when we need it? This isn't just a new note for the install doc, it's a whole new set of instructions. And if users ignore the "For Puppet Enterprise Users" section, yes they're gonna be broken. That's true of most of our docs pages; if you pick and choose arbitrary instructions to follow from the page, things will break. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22745.1559066640360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Molly Waggett commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Yasmin Rajabi That name was discussed with my team. We thought that it needed to be clear that this repo is intended for PE users, while FOSS users should continue using the puppetN repos. Are there concerns? If we (RE) shouldn't have been the ones to make that name decision, who should have? How should that have gone differently? /cc Rob Braden 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22686.1559066040596%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1346) Bolt docs: Include example returns, link to docs about returned types
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1346 Bolt docs: Include example returns, link to docs about returned types Change By: Melissa Amos [https://puppet.com/docs/bolt/latest/plan_functions.html].Url: /docs/bolt/latest/plan_functions.htmlRank: 4/5Email: [rbo...@huronconsultinggroup.com|mailto:rbo...@huronconsultinggroup.com] Message:The examples are great! It would be nice to get some examples of the returnsthat the examples would provide. Also would be nice to have links to thetypes that they are returning. for examplewhen using get_targets() it returnsan array of Boltlib::TargetSpec, but it would be nice to have a link to theBoltlib::TargetSpec and or array types so I don't have to go back to googleto figure out how to interact with those types in my plans.thanks!CC [~melissa.amos] 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
Jira (BOLT-1346) Bolt docs: Include example returns, link to docs about returned types
Title: Message Title Melissa Amos moved an issue Puppet Task Runner / BOLT-1346 Bolt docs: Include example returns, link to docs about returned types Change By: Melissa Amos Team: Bolt Workflow: Documentation Scrum Team Workflow Key: DOC BOLT - 4137 1346 Project: Documentation [Internal] Puppet Task Runner 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
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Yasmin Rajabi commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Alex Dreyer Nick Walker Molly Waggett theres some confusion on what this name should be... I don't think we discussed puppet-enterprise-tools in the meeting? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22575.1559064780400%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Sean McDonald commented on PUP-9722 Re: Regression: File mode changed on every puppet run Ping Mihai Buzgau on this ticket. I've assigned it to your team and added it to your PR triage. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.22545.1559064420997%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9722 Regression: File mode changed on every puppet run Change By: Sean McDonald Sprint: PR - Triage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.22541.1559064420810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9722 Regression: File mode changed on every puppet run Change By: Sean McDonald Team: Platform OS Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.22538.1559064420706%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Josh Cooper Fix Version/s: PUP 6.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.22528.1559064362966%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9570 Catalog failure on first run due to pluginsync and environment switch Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.22517.1559064362450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9714) Add support for nested hiera interpolation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9714 Add support for nested hiera interpolation Change By: Josh Cooper Team: Server 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309648.1558477577000.22502.1559064301405%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9714) Add support for nested hiera interpolation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9714 Add support for nested hiera interpolation 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309648.1558477577000.22504.1559064301461%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9722 Regression: File mode changed on every puppet run Change By: Josh Cooper Team: Platform OS 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.22488.1559064240256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Walker commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo I'm confused. I thought we were going to make a new repo with bolt and pdk in it. Then we were going to update the install instructions for Bolt to always refer to that repo so that PE users couldn't accidentally read instructions for installing that would inevitably break their PE install. The new repo just upgrades the existing note about how installing the OSS repo might cause you problems to saying we have a defined way for PE users to install but it doesn't really stop a non-attentive users from skipping the "install for PE" section and going to "install on *nix" section and ending up in the same problematic state. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22490.1559064240351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1928) Facter routing table process issues for Bionic on Windows
Title: Message Title Josh Cooper moved an issue Facter / FACT-1928 Facter routing table process issues for Bionic on Windows Change By: Josh Cooper Key: PUP FACT - 9721 1928 Project: Puppet Facter 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310245.1558775246000.22476.1559064120679%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9721) Facter routing table process issues for Bionic on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9721 Facter routing table process issues for Bionic on Windows Change By: Josh Cooper Team: Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310245.1558775246000.22474.1559064120588%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4354) Support FIPS certification
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4354 Support FIPS certification Change By: Rob Browning Summary: Work to support Support FIPS certification on PuppetDB 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306362.155621099.22434.1559063581350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4378) Make sure upgrade docs clearly state multi-pdb migration requirements
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4378 Make sure upgrade docs clearly state multi-pdb migration requirements Issue Type: New Feature Assignee: Unassigned Created: 2019/05/28 10:10 AM Priority: Normal Reporter: 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.
Jira (PUP-4930) Provide helpful error message when provider does not have instances defined
Title: Message Title Jorie Tappa commented on PUP-4930 Re: Provide helpful error message when provider does not have instances defined Merged to 5.5.x at 59922c930139c415e9e982d17ab1ca5d836fb3e9 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.90662.1438016947000.22337.1559062681130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1337) Make .filter called on a ResultSet return a ResultSet
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1337 Make .filter called on a ResultSet return a ResultSet Change By: Alex Dreyer Sprint: Bolt 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.22323.1559062500262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1317) Only ship bolt gem to rubygems when syncing packages to public repos
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1317 Only ship bolt gem to rubygems when syncing packages to public repos Change By: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309311.1558128719000.22303.1559062260367%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1261) Common debugging and best practices documents
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1261 Common debugging and best practices documents Change By: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305719.1555863895000.22301.1559062260238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1345) Add navigation to bolt website
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1345 Add navigation to bolt website Issue Type: Task Assignee: Unassigned Created: 2019/05/28 9:49 AM Priority: Normal Reporter: Lucy Wyman The bolt website should have some navigation. It should have top-level 'categories', of which the task hands on lab is one with each lesson being a 'subpage'. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1261) Common debugging and best practices documents
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1261 Common debugging and best practices documents Change By: Lucy Wyman 2 ideas for documentation that's been asked for frequently:1. Common issues This should be a minimal list of common errors and how common ways to debug or fix them - . For example: this came up when someone was getting a "bolt can't find that task" error, and mentioned we should record common things to try when you encounter this error.a. Bolt can't find a taskb. can’t find gem bolt (>= 0.a) with executable bolt (Gem::GemNotFoundException) 2. A Bolt best practices doc. It might This can be too early in Bolt development added to start this, but a document like https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html that links to other docmentation as issues come up in Bolt would be useful Slack . For example, we get the question of how to structure This is also a project directory pretty frequently. We might need to think about improving SEO in that case, or linking to the project directory page from a good place for "we run into this issue and don ' Best Practices' page t know why" . Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1261) Common debugging and best practices documents
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1261 Common debugging and best practices documents Change By: Lucy Wyman This should be a minimal list of common errors and common ways to debug or fix them. For example: this came up when someone was getting a "bolt can't find that task" error, and mentioned we should record common things to try when you encounter this error.a. Bolt can't find a taskb. can’t find gem bolt (>= 0.a) with executable bolt (Gem::GemNotFoundException)This can be added to as issues come up in Slack. This is also a good place for "we run into this issue and don't know why". This should live in the Bolt website. 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 (PDB-3840) Add additional cleanup of the facts table during migrations
Title: Message Title Rob Browning commented on PDB-3840 Re: Add additional cleanup of the facts table during migrations For future reference, when this issue causes a crash, it should produce an error in the log that looks like this: ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 3 ALTER TABLE facts ADD CONSTRAINT fact_path_id_fk FOREIGN KEY (fact_path_id) REFERENCES fact_paths(id) was aborted. Call getNextException to see the cause. at org.postgresql.jdbc.BatchResultHandler.handleError(BatchResultHandler.java:133) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2004) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:360) at org.postgresql.jdbc.PgStatement.executeBatch(PgStatement.java:1019) at com.zaxxer.hikari.pool.ProxyStatement.executeBatch(ProxyStatement.java:125) at com.zaxxer.hikari.pool.HikariProxyStatement.executeBatch(HikariProxyStatement.java) at clojure.java.jdbc$execute_batch.invokeStatic(jdbc.clj:439)
Jira (BOLT-1261) Common debugging and best practices documents
Title: Message Title Lucy Wyman commented on BOLT-1261 Re: Common debugging and best practices documents Note to Lucy: make ticket for 2. A Bolt best practices doc. It might be too early in Bolt development to start this, but a document like https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html that links to other docmentation in Bolt would be useful. For example, we get the question of how to structure a project directory pretty frequently. We might need to think about improving SEO in that case, or linking to the project directory page from a 'Best Practices' page. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305719.1555863895000.22282.1559061960944%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3840) Add additional cleanup of the facts table during migrations
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3840 Add additional cleanup of the facts table during migrations Change By: Rob Browning Release Notes Summary: PuppetDB should no longer crash when performing an older database migration in some (likely rare) situations. The crash should produce an error in the log that mentions "java.sql.BatchUpdateException: Batch entry 3 ALTER TABLE facts ADD CONSTRAINT fact_path_id_fk". Release Notes: Bug Fix 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. To view this discussion on the web visit
Jira (BOLT-1341) Support version 4 terraform state files in terraform inventory plugin
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1341 Support version 4 terraform state files in terraform inventory plugin Change By: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310025.155865782.22256.1559061840334%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1342) Help text should only list options for that command
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1342 Help text should only list options for that command Change By: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310059.1558709649000.22246.1559061660824%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1342) Help text should only list options for that command
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1342
Help text should only list options for that command
Change By:
Lucy Wyman
Our help text currently lists all available options, even they aren't respected by the command. For example {{bolt puppetfile install --help}} lists {{--private-key}}, but doesn't actually use that private key for r10k configuration. We should add documentation around which arguments are respected by which commands, and update help text to only print the options for that specific command. Potentially look into using cri, though it might just be easier to write our own bespoke printing. We should define which options are available for which subcommands - add one more level to the COMMANDS structure.
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
Jira (PDB-3840) Add additional cleanup of the facts table during migrations
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3840 Add additional cleanup of the facts table during migrations Change By: Rob Browning Team: PuppetDB 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.235772.1518051868000.22203.1559061363260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3840) Add additional cleanup of the facts table during migrations
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3840 Add additional cleanup of the facts table during migrations Change By: Rob Browning Assignee: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.235772.1518051868000.22196.1559061362890%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4308) Check whether pdb is unkillable when db is unavailable at startup
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4308 Check whether pdb is unkillable when db is unavailable at startup Change By: Rob Browning Fix Version/s: PDB 6.3.2 Fix Version/s: PDB 6.0.4 Fix Version/s: PDB 5.2.9 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300218.1552580118000.22180.1559061240893%40Atlassian.JIRA. For more
Jira (PDB-4308) Check whether pdb is unkillable when db is unavailable at startup
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4308 Check whether pdb is unkillable when db is unavailable at startup Change By: Rob Browning Release Notes Summary: Previously, if the database were inaccessible during startup, PuppetDB could become "unkillable", meaning that `kill PUPPETDB_PID` or Control-C from a terminal (for example) would no longer stop the server. Now PuppetDB should exit properly in those situations. Release Notes: Bug Fix Issue Type: Improvement Bug 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 (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1127
Bolt should echo port if custom SSH port is used
Change By:
Lucy Wyman
When connecting to the same IP address with Bolt, the output appears as follows:{{[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Finished on 127.0.0.1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Successful on 3 nodes: root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Ran on 3 nodes in 0.24 seconds}} There is no way to tell which node is which. This is mildly problematic with Docker containers, but is very problematic where PAT is being used between networks and multiple nodes are being targeted. Ideally, the output would appear as this: {{[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Finished on 127.0.0.1:32768:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:32769:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:32770:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Successful on 3 nodes: root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Ran on 3 nodes in 0.24 seconds}} Alternatively, it would be good to have a syntax switch in the --nodes parameter such that an alias could be passed - e.g. {{[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768\{node1},root@127.0.0.1:32769\{node2},root@127.0.0.1:32770\{node3}}}{{Started on node1...}}{{Started on node2...}}{{Started on node3...}}{{Finished on node1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on node2:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on node3:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Successful on 3 nodes: root@127.0.0.1:32768\{node1},root@127.0.0.1:32769\{node2},root@127.0.0.1:32770\{node3}}}{{Ran on 3 nodes in 0.24 seconds}} The real issue here is that 'uri' may not be displayable, so how can we compute a display name from the uri if the user doesn't specify a 'name'? If you've specified a name we can use that as the display name.Plan authors can print the display name with {{target.to_s}}How can we ship this in a way that's safe for users on Inventory v1 to use?
Jira (PDB-4364) Fix databind CVE-2018-5968 CVE-2018-19360 CVE-2018-19361 CVE-2018-19362 in 5.1
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4364 Fix databind CVE-2018-5968 CVE-2018-19360 CVE-2018-19361 CVE-2018-19362 in 5.1 Change By: Rob Browning Release Notes: Security Fix 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307473.155716600.22137.1559060580797%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1927) Build Facter for JRuby on redhatfips-7-x86_64
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1927 Build Facter for JRuby on redhatfips-7-x86_64 Change By: Gheorghe Popescu Sprint: PR - Triage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.31.1558650599000.21822.1559056800654%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1927) Build Facter for JRuby on redhatfips-7-x86_64
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1927 Build Facter for JRuby on redhatfips-7-x86_64 Change By: Gheorghe Popescu Team: Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.31.1558650599000.21820.1559056800561%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1927) Build Facter for JRuby on redhatfips-7-x86_64
Title: Message Title Gheorghe Popescu commented on FACT-1927 Re: Build Facter for JRuby on redhatfips-7-x86_64 Hi Sara Meisburger this was implemented here https://github.com/puppetlabs/puppet-agent/commit/24db3b5d529152051bd723680509b4975029fef7 The fix was committed to 5.5.x and it was promoted to all the branches. Can you please validate that the latest nightly build of puppet-agent has this fix? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.31.1558650599000.21816.1559056740137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1926 ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Change By: Gheorghe Popescu Team: Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.21718.1559055900265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1926 ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Change By: Gheorghe Popescu Sprint: PR - Triage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.21720.1559055900362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
