Jira (PUP-11755) each/map/filter functions are slow/buggy on jruby
Title: Message Title Nick Lewis commented on PUP-11755 Re: each/map/filter functions are slow/buggy on jruby Ingrida Cazers Yes, it will be in those releases. That text looks right! Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481178.167581186.1799.1679346900047%40Atlassian.JIRA.
Jira (PUP-11755) each/map/filter functions are slow/buggy on jruby
Title: Message Title Nick Lewis updated an issue Puppet / PUP-11755 each/map/filter functions are slow/buggy on jruby Change By: Nick Lewis Release Notes Summary: This fixes a case where the each/map/filter built-in functions in Puppet language had poor performance and consumed unnecessary resources. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481178.167581186.4392.1678404720026%40Atlassian.JIRA.
Jira (PUP-11755) each/map/filter functions are slow/buggy on jruby
Title: Message Title Nick Lewis updated an issue Puppet / PUP-11755 each/map/filter functions are slow/buggy on jruby Change By: Nick Lewis Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481178.167581186.4391.1678404600038%40Atlassian.JIRA.
Jira (PUP-11755) each/map/filter functions are slow/buggy on jruby
Title: Message Title Nick Lewis created an issue Puppet / PUP-11755 each/map/filter functions are slow/buggy on jruby Issue Type: Bug Assignee: Unassigned Created: 2023/02/07 3:17 PM Priority: Normal Reporter: Nick Lewis The each, map and filter functions use a pattern for enumeration that is both extremely slow and incorrect when run in jruby: The pattern is roughly: enum = object.each object.size.times do yield(enum.next) end Because this only calls next as many times as there are objects in the enuemrator, it never triggers StopIteration. That causes the Fiber associated with the enumerator not to be cleaned up. Since JRuby Fibers are mapped to native threads, that leaves an active native thread, which can cause the server to hit its limit of
Jira (PDB-5557) Enable drop-joins for subqueries
Title: Message Title Nick Lewis updated an issue PuppetDB / PDB-5557 Enable drop-joins for subqueries Change By: Nick Lewis Sprint: Skeletor 12/07/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.473181.127979000.62352.1669850760133%40Atlassian.JIRA.
Jira (PDB-5557) Enable drop-joins for subqueries
Title: Message Title Nick Lewis assigned an issue to Nick Lewis PuppetDB / PDB-5557 Enable drop-joins for subqueries Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.473181.127979000.62351.1669850760059%40Atlassian.JIRA.
Jira (PDB-5555) Correct lock acquisition order of Report Partition GC
Title: Message Title Nick Lewis updated an issue PuppetDB / PDB- Correct lock acquisition order of Report Partition GC Change By: Nick Lewis Fix Version/s: PDB 7.y Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472749.166630080.62308.1669836480044%40Atlassian.JIRA.
Jira (PDB-5555) Correct lock acquisition order of Report Partition GC
Title: Message Title Nick Lewis updated an issue PuppetDB / PDB- Correct lock acquisition order of Report Partition GC Change By: Nick Lewis Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472749.166630080.62307.1669836420104%40Atlassian.JIRA.
Jira (PDB-5555) Correct lock acquisition order of Report Partition GC
Title: Message Title Nick Lewis assigned an issue to Nick Lewis PuppetDB / PDB- Correct lock acquisition order of Report Partition GC Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472749.166630080.58389.1668465900099%40Atlassian.JIRA.
Jira (PDB-5555) Correct lock acquisition order of Report Partition GC
Title: Message Title Nick Lewis updated an issue PuppetDB / PDB- Correct lock acquisition order of Report Partition GC Change By: Nick Lewis Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472749.166630080.52732.1666804860182%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Nick Lewis updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Nick Lewis Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.52731.1666804860133%40Atlassian.JIRA.
Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Nick Lewis updated an issue PuppetDB / PDB-5553 Remove foreign keys from report partitions Change By: Nick Lewis Team: Skeletor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.52730.1666804860086%40Atlassian.JIRA.
Jira (PUP-11315) Plans apply function collides with resource types that have apply attribute
Title: Message Title Nick Lewis updated an issue Puppet / PUP-11315 Plans apply function collides with resource types that have apply attribute Change By: Nick Lewis Release Notes Summary: The names "apply" and "plan" can now be used as resource parameter names in all cases. Previously, using them within an apply() block in a plan would fail. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395282.1618361168000.160026.1634759940533%40Atlassian.JIRA.
Jira (PUP-11315) Plans apply function collides with resource types that have apply attribute
Title: Message Title Nick Lewis updated an issue Puppet / PUP-11315 Plans apply function collides with resource types that have apply attribute Change By: Nick Lewis Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395282.1618361168000.160018.1634759880032%40Atlassian.JIRA.
Jira (PUP-11315) Plans apply function collides with resource types that have apply attribute
Title: Message Title Nick Lewis moved an issue Puppet / PUP-11315 Plans apply function collides with resource types that have apply attribute Change By: Nick Lewis Key: ENTERPRISE PUP - 1421 11315 Project: Puppet Enterprise Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395282.1618361168000.147931.1633474740055%40Atlassian.JIRA.
Jira (PUP-10223) Allow apply blocks in plans to contain node definitions
Title: Message Title Nick Lewis updated an issue Puppet / PUP-10223 Allow apply blocks in plans to contain node definitions Change By: Nick Lewis Release Notes: Not Needed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341353.1578428456000.25137.1581621240082%40Atlassian.JIRA.
Jira (PUP-10223) Allow apply blocks in plans to contain node definitions
Title: Message Title Nick Lewis created an issue Puppet / PUP-10223 Allow apply blocks in plans to contain node definitions Issue Type: Improvement Assignee: Unassigned Created: 2020/01/07 12:20 PM Priority: Normal Reporter: Nick Lewis Currently, Bolt does not support evaluating node definitions when running plans or applying Puppet code. Accordingly, Puppet does not allow node definitions to be specified in plans. In order to now support node definitions with Bolt, we need to relax the restriction in Puppet so the node definitions can be loaded and used by Bolt. For more information: https://github.com/puppetlabs/bolt/issues/1338 Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1502) Do not rely on wrapper script for run-as with stdin task input
Title: Message Title Nick Lewis commented on BOLT-1502 Re: Do not rely on wrapper script for run-as with stdin task input We need to introduce a slightly more complex state machine to the SSH transport. We should now hold off on submitting stdin until we see a marker message indicating the command has started executing. We should string the command together with an echo of a randomly generated message, and our on_data handler should check for that message and then submit stdin. It should track some state indicating it's sent stdin, to prevent it from being sent multiple times. So in the case where you're using sudo with a password, the on_data handler will first notice the password prompt and send the password, then once sudo has successfully escalated, it will run the echo, and then the on_data will see the message indicating it's time to send stdin. We can either vary this behavior based on whether you're using sudo or we can always include the echo, depending on which seems more sensible in the actual implementation. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319291.1564682997000.47396.1565213100105%40Atlassian.JIRA.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow I filed a PR against net-ssh with some improvements to known_hosts parsing. There's more work to be done to only parse it once, but this is a substantial improvement anyway. https://github.com/net-ssh/net-ssh/pull/682 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.315226.1562163484000.13408.1562889900200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow I've found a couple things. The first is that net-ssh's parsing of known_hosts is inherently quite slow (~300ms with 20k lines). The other is that net-ssh parses the known_hosts file once for every host being targeted. The first issue is relatively easy to fix, but the latter requires a bigger restructure. 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.315226.1562163484000.13215.1562885220158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow It's also only using one core on my machine. That's a limitation of Ruby, unfortunately. But it doesn't seem to be a computationally intensive task in my case, since it's still running very quickly. I found a potentially related issue: https://github.com/net-ssh/net-ssh/issues/567 If I cat my known_hosts file into itself a few times, Bolt takes more than twice as long to run. Does the host you're running from have a particularly large known_hosts file? Weirdly, this seems to even be the case if I run with --no-host-key-check set... 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.315226.1562163484000.13059.1562882580098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow I tested on 50 nodes and a simple command run took ~3.3 seconds. The same thing in pssh takes ~0.8 seconds and ~6.6 seconds in ansible. This is with four cores and concurrency set to 50 for all of them. Is it possible that Bolt is using a different, slower authentication method? I'm not sure how that would account for such a large difference though. Unfortunately, since it seems to be an environmental issue of some sort, it's hard to say what might be going on... 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.315226.1562163484000.11683.1562798220395%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow This is really interesting, thanks for the report. Do you notice the same slowness when using bolt command run as well, or is it specific to tasks? I wonder if the difference could be related to having to scp the task file... I wouldn't be surprised if Bolt were a little slower in this case, but 80 seconds is extremely 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315226.1562163484000.9838.1562713800094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1451 Automatically call apply_prep before `resources` step in YAML plans Issue Type: Improvement Assignee: Unassigned Created: 2019/07/02 9:29 AM Priority: Normal Reporter: Nick Lewis Currently, if the user needs to apply_prep before a resources step in a YAML plan, they need to have an eval step that calls it. This is a bit unnatural in a YAML plan and requires some more knowledge before successfully using the resources step. We should figure out some way to automatically call apply_prep on the user's behalf, potentially either the first time a resources step is encountered or every time a resources step is encountered. We could also add a parameter to the resources step to toggle whether or not to apply_prep beforehand. Add Comment
Jira (BOLT-1406) out::message doesn't work inside without_default_logging
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1406 out::message doesn't work inside without_default_logging Issue Type: Bug Assignee: Unassigned Created: 2019/06/18 9:38 AM Priority: Normal Reporter: Nick Lewis Currently, without_default_logging makes a flatly disables all event processing for the human outputter. This winds up also skipping the message event that is used by out::message. Given a core use case of out::message is to disable default output and substitute your own, this is a significant issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1406) out::message doesn't work inside without_default_logging
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1406 out::message doesn't work inside without_default_logging Change By: Nick Lewis 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.312979.1560875893000.51501.1560875940619%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1222 Support an "apply" step. 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.302484.1554141988000.44454.1560360421699%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml Change By: Nick Lewis Release Notes Summary: The "puppetfile" config section now supports a "forge" sub-section which can be used to set an alternate Puppet Forge location from which to download modules. 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.311712.1559939792000.44233.1560357420576%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311712.1559939792000.44229.1560357362162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml Change By: Nick Lewis Component/s: DOCS 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.311712.1559939792000.44227.1560357300205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml 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.311712.1559939792000.42614.1560278040446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1261) Common debugging and best practices documents
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1261 Common debugging and best practices documents 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.305719.1555863895000.37345.1559846760288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Change By: Nick Lewis Release Notes Summary: An HTTP proxy can now be specified for `bolt puppetfile install` in bolt.yaml:---puppetfile: proxy: https://proxy.example.com 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.309580.1558449511000.34483.1559691421771%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309580.1558449511000.34469.1559691421202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1327
Expose r10k proxy configuration option
Change By:
Nick Lewis
r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration{noformat}---puppetfile: http_proxy proxy : "." https_proxy: ".." {noformat}questions:What should the configuration option be called?* There should be a new {{puppetfile}} section in config, and this should be called {{proxy}} under that config.
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-1327) Expose r10k proxy configuration option
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Change By: Nick Lewis Component/s: DOCS 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.309580.1558449511000.34456.1559690940381%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option 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.309580.1558449511000.34278.1559685600672%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1327
Expose r10k proxy configuration option
Change By:
Nick Lewis
r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration{ { noformat} } ---puppetfile: http_proxy: "." https_proxy: ".."{ { noformat} } questions:What should the configuration option be called?* There should be a new {{puppetfile}} section in config, and this should be called {{proxy}} under that config.
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-1359) Collect usage data for non-boltlib built-in functions
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1359 Collect usage data for non-boltlib built-in functions 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.310938.155932623.30253.1559326263299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1359) Collect usage data for non-boltlib built-in functions
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1359 Collect usage data for non-boltlib built-in functions Issue Type: Improvement Assignee: Unassigned Created: 2019/05/31 11:10 AM Priority: Normal Reporter: Nick Lewis We now ship several modules besides boltlib in bolt-modules. These include ctrl, file, out and system. Each of those modules has functions, but we don't collect usage data for any of those functions in the same way we do for boltlib functions. We should. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1359) Collect usage data for non-boltlib built-in functions
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1359 Collect usage data for non-boltlib built-in functions Change By: Nick Lewis 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.310938.155932623.30254.1559326263365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1345) Add navigation to bolt website
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1345 Add navigation to bolt website 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.310324.1559062195000.29198.1559259420578%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1325) Provide a way to send a message to the outputter
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1325 Provide a way to send a message to the outputter Change By: Nick Lewis Currently, the Puppet logging functions (notice, info, etc) call the logger directly. This means the messages are no longer sent to console below warn-level. We should add Bolt-specific versions of these functions a function that generate "log" events that are handled by allows the plan to send a message to the user via the outputter. The human outputter should print the messages to stdout , and the json outputter should ignore them, and the logger outputter outputters should forward ignore them to the logger . 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
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1325
Send Puppet logging functions to the outputter
Change By:
Nick Lewis
Release Notes Summary:
This introduces a new function {{out::message()}}, which can be used to print a message to the user during a plan.
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.309516.1558393815000.26072.1559161380806%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1325 Send Puppet logging functions to the outputter 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.26071.1559161380759%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1325) Provide a way to send a message to the outputter
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1325 Provide a way to send a message to the outputter Change By: Nick Lewis Summary: Send Puppet logging functions Provide a way to send a message to the outputter 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.309516.1558393815000.26077.1559161381006%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1355) Bolt can't run some tasks over SSH when csh is the login shell
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1355 Bolt can't run some tasks over SSH when csh is the login shell Issue Type: Bug Assignee: Unassigned Created: 2019/05/29 11:52 AM Priority: Normal Reporter: Nick Lewis This issue was encountered by a user in Slack. When a user has csh as their login shell, Bolt fails to run tasks that use environment variables as input, because the syntax it uses for passing environment variables is invalid in csh. Specifically, we pass them as PT_foo=bar /path/to/task, and PT_foo=bar is interpreted as the name of the command to run. We should investigate what is necessary to support running on csh. Add Comment This message was sent by
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 (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 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 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-1341) Support version 4 terraform state files in terraform inventory plugin
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1341 Support version 4 terraform state files in terraform inventory plugin Change By: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310025.155865782.19719.1558657860413%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 created an issue Puppet Task Runner / BOLT-1341 Support version 4 terraform state files in terraform inventory plugin Issue Type: Improvement Assignee: Unassigned Created: 2019/05/23 5:30 PM Priority: Normal Reporter: Nick Lewis Terraform 0.12 changes the terraform statefile format, breaking the terraform inventory plugin. We should check the version field and handle the new format appropriately. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1338) Add file::exists and file::readable functions
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1338 Add file::exists and file::readable functions 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309952.155864478.19382.1558644900155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1338) Add file::exists and file::readable functions
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1338
Add file::exists and file::readable functions
Change By:
Nick Lewis
Release Notes Summary:
Added two new functions bundled with Bolt, {{file::exists}} and {{file::readable}}. These test whether a given file exists and is readable, respectively.
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.309952.155864478.19383.1558644900205%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1338) Add file::exists and file::readable functions
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1338 Add file::exists and file::readable functions Issue Type: Improvement Assignee: Unassigned Created: 2019/05/23 1:53 PM Priority: Normal Reporter: Nick Lewis When working with local files in a plan, it's helpful to be able to verify whether they exist and are readable before trying to use them. For example, setting up a new host might involve copying over whichever of a set of files are present on the local machine. We should have built-in functions for checking the existence and readability of a local file. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1338) Add file::exists and file::readable functions
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1338 Add file::exists and file::readable functions Change By: Nick Lewis 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.309952.155864478.19379.1558644840482%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis commented on BOLT-1325 Re: Send Puppet logging functions to the outputter I agree. We just did a bunch of work to split the concepts of "output" and "logging" in Bolt, and I think this ticket would conflate them again, but this time for users. print() or similar seems much more straightforward. 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.309516.1558393815000.18990.1558633680256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis commented on BOLT-1325 Re: Send Puppet logging functions to the outputter I started looking at it and yes I ran into the issue with their being hardwired. The problem with swapping out the logging system entirely is that we actually want log functions from user content to be handled differently than logging built into puppet. Specifically, if the user calls notice then we want to print that message on stdout, but if Puppet calls notice then we want it to be handled by the logger. 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.309516.1558393815000.17837.1558561860193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1325 Send Puppet logging functions to the outputter 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.309516.1558393815000.15384.1558473540359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1329) Delete task wrapper script before running the task
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1329 Delete task wrapper script before running the task Issue Type: Improvement Assignee: Unassigned Created: 2019/05/21 12:08 PM Priority: Normal Reporter: Nick Lewis When running a task over SSH with run-as and using the stdin input method, we write a wrapper script to the target that passes the stdin via a heredoc. That means that if the task invocation has sensitive parameters, they are persisted on disk (albeit in a secured temporary file) for the duration of the task run and only cleaned up after it's finished. We should instead make the script self-deleting by making its first line a call to rm /path/to/the/wrapper/script. Since the script will already have been loaded by the shell, we can safely delete it and continue executing. That will significantly reduce the amount of time that parameters exist on disk, as it will only be between the time we write the script and the time we run the script. Add Comment
Jira (BOLT-1326) Exclude large files from apply/fact plugin bundles
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1326 Exclude large files from apply/fact plugin bundles Change By: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309519.1558394027000.13477.1558394100425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1326) Exclude large files from apply/fact plugin bundles
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1326 Exclude large files from apply/fact plugin bundles Issue Type: New Feature Assignee: Unassigned Created: 2019/05/20 4:13 PM Priority: Normal Reporter: Nick Lewis When gathering facts and applying a catalog, we bundle the contents of the files and lib directories of every module and send them to the target, to ensure that whatever plugins the catalog might need are present. When the user has modules that include, for instance, large binary files, this process is extremely slow. Because those files are quite unlikely (or at least seldom) to be used by apply, we should provide a way to exclude them from the bundle. This could either be a user-maintained blacklist of files or we could automatically exclude files over a certain size (100k?) and provide the user a way to indicate that they should be included when they're necessary. Add Comment
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1325 Send Puppet logging functions to the outputter Issue Type: Improvement Assignee: Unassigned Created: 2019/05/20 4:10 PM Priority: Normal Reporter: Nick Lewis Currently, the Puppet logging functions (notice, info, etc) call the logger directly. This means the messages are no longer sent to console below warn-level. We should add Bolt-specific versions of these functions that generate "log" events that are handled by the outputter. The human outputter should print the messages to stdout, the json outputter should ignore them, and the logger outputter should forward them to the logger. Add Comment This message was sent by
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1325 Send Puppet logging functions to the outputter Change By: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.13467.1558393861228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Change By: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309059.1558038203000.9695.1558038240509%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Issue Type: Improvement Assignee: Unassigned Created: 2019/05/16 1:23 PM Priority: Normal Reporter: Nick Lewis We should collect a data point about whether users are using a Boltdir, a local bolt.yaml, or ~/.puppetlabs/bolt. We should be able to include that as a custom dimension on the screen view that we send in the CLI. On the google analytics side, this can probably be tracked as a session-level metric, as a single user might have multiple projects potentially following different patterns, and we would like to know about that. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1264
Allow puppetdb plugin to set host and name independently
Change By:
Nick Lewis
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately. The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.If a fact isn't set for a node, the config setting for that fact should not be set.
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"
Jira (BOLT-1302) Build packages for Fedora 30
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1302 Build packages for Fedora 30 Issue Type: Improvement Assignee: Unassigned Created: 2019/05/13 11:25 AM Priority: Normal Reporter: Nick Lewis Fedora 30 was released on April 29, 2019. We currently build puppet-bolt packages for Fedora 28 and 29, so we should add support for 30. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title
Nick Lewis created an issue
Puppet Task Runner / BOLT-1300
Update install docs to point to puppet-enterprise-tools repo
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/05/09 11:52 AM
Priority:
Normal
Reporter:
Nick Lewis
We now have a puppet-enterprise-tools repo on {yum,apt} .puppet.com that can be used to install Bolt safely without interfering with the puppet-agent package on a PE-managed node. We currently have a note warning PE users not to setup the repo and to install the packages individually. That workflow means they can't easily upgrade their version of bolt, but it's necessary to avoid accidentally clobbering their puppet-agent with a newer version. Now that we have the puppet-enterprise-tools repo, we can refer PE users to that, so they can get the same benefits of having updates easily available through their package manager.
Add Comment
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1300 Update install docs to point to puppet-enterprise-tools repo Change By: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.29457.1557427980517%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1299) YAML plan converter wraps single-line evals in with() if they end with a newline
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1299 YAML plan converter wraps single-line evals in with() if they end with a newline Change By: Nick Lewis 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.308039.1557423656000.29276.1557423720111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1299) YAML plan converter wraps single-line evals in with() if they end with a newline
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1299
YAML plan converter wraps single-line evals in with() if they end with a newline
Change By:
Nick Lewis
Release Notes Summary:
{{bolt plan convert}} no longer wraps single-line eval steps in a {{with()}} statement unnecessarily.
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.308039.1557423656000.29280.1557423780217%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1299) YAML plan converter wraps single-line evals in with() if they end with a newline
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1299 YAML plan converter wraps single-line evals in with() if they end with a newline 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.308039.1557423656000.29277.1557423720163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1299) YAML plan converter wraps single-line evals in with() if they end with a newline
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1299 YAML plan converter wraps single-line evals in with() if they end with a newline Change By: Nick Lewis 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 https://groups.google.com/d/msgid/puppet-bugs/JIRA.308039.1557423656000.29278.1557423720211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1299) YAML plan converter wraps single-line evals in with() if they end with a newline
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1299 YAML plan converter wraps single-line evals in with() if they end with a newline Issue Type: Bug Assignee: Unassigned Created: 2019/05/09 10:40 AM Priority: Normal Reporter: Nick Lewis The multi-line string formats in YAML (> and |) add a newline to the end of the string, regardless of whether it's a single line or multiple lines. That causes the plan converter to treat a single line eval as though it were multiple lines, and wrap it in with() unnecessarily. This detection should check for whether the string actually contains multiple lines, not just whether it ends in a newline character. Add Comment This message was
Jira (BOLT-1268) Inventory is loaded for actions that do not use it.
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1268 Inventory is loaded for actions that do not use it. 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.306168.1556123455000.27296.1557341640442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1268) Inventory is loaded for actions that do not use it.
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1268 Inventory is loaded for actions that do not use it. Change By: Nick Lewis Issue Type: New Feature 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 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.306168.1556123455000.24795.1557247260345%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-901 Improve Plan Logging with apply Change By: Nick Lewis Release Notes Summary: `bolt apply` and the `apply` function from plans will now show log messages for changes and failures that happened while applying the Puppet code. 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-901) Improve Plan Logging with apply
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-901 Improve Plan Logging with apply Change By: Nick Lewis Release Notes: Enhancement 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-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
Problem I want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting * All actions (plan start/finish, step start/finish, node start/result) are handed to the outputter as an event stream. * {{--verbose}} becomes an option for the outputter not the logger. * "verbose" is now defined to mean node-level results are included in the output when using the human format. "verbose" has no meaning for the JSON format. * Plans default to non-verbose, everything else defaults to verbose. {{ \ --no-verbose}} is accepted as an addition to {{--verbose}} * "plan logging" becomes an outputter concept, rather than an executor concept * {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter * Human outputter without verbose prints starting action and summary for action messages. * Human outputter prints full node-level result with {{--verbose}} * For {{bolt apply}} _without_ verbose, human outputter only prints a summary of the run * For {{bolt apply}} _with_ verbose, human outputter prints logs from each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet". * All output from this outputter can go to stdout (currently messages go to stderr for plans)JSON outputter: * When in non-plan mode behaves as it does currently. * Logs entire JSON format of {{apply}} result on stderr for each node at {{--verbose}} * This outputter can show intermediate results on stderr in human format, but doesn't have to for this ticketLog output: * The default console log level is now "warn". No "human-oriented" output should come from the logger except for warnings and errors. * Log files still default to "info". * {{\-\-debug}} still sets debug level for console logger, {{\-\-verbose}} does not affect the logger at all * A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the loggerPuppet log functions: * Eventually these should be handled by the outputter rather than the logger directly, but this is left to a later ticket.apply_prep/get_resources: * These probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
Problem I want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting * All actions (plan start/finish, step start/finish, node start/result) are handed to the outputter as an event stream. * {{--verbose}} becomes an option for the outputter not the logger. * "verbose" is now defined to mean node-level results are included in the output when using the human format. "verbose" has no meaning for the JSON format. * Plans default to non-verbose, everything else defaults to verbose. {{--no-verbose}} is accepted as an addition to {{--verbose}} * "plan logging" becomes an outputter concept, rather than an executor concept * {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter * Human outputter without verbose prints starting action and summary for action messages. * Human outputter prints full node-level result with {{--verbose}} * For {{bolt apply}} _without_ verbose, human outputter only prints a summary of the run * For {{bolt apply}} _with_ verbose, human outputter prints logs from each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet". * All output from this outputter can go to stdout (currently messages go to stderr for plans)JSON outputter: * When in non-plan mode behaves as it does currently. * Logs entire JSON format of {{apply}} result on stderr for each node at {{--verbose}} * This outputter can show intermediate results on stderr in human format, but doesn't have to for this ticketLog output: * The default console log level is now "warn". No "human-oriented" output should come from the logger except for warnings and errors. * Log files still default to "info". * {{ \ - \ -debug - }} still sets debug level for console logger, {{-verbose}} does not affect the logger at all * A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the loggerPuppet log functions: * Eventually these should be handled by the outputter rather than the logger directly, but this is left to a later ticket.apply_prep/get_resources: * These probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
Problem I want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting * All actions (plan start/finish, step start/finish, node start/result) are handed to the outputter as an event stream. * {{--verbose}} becomes an option for the outputter not the logger. * "verbose" is now defined to mean node-level results are included in the output when using the human format. "verbose" has no meaning for the JSON format. * Plans default to non-verbose, everything else defaults to verbose. {{--no-verbose}} is accepted as an addition to {{--verbose}} * "plan logging" becomes an outputter concept, rather than an executor concept * {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter * Human outputter without verbose prints starting action and summary for action messages. * Human outputter prints full node-level result with {{--verbose}} * For {{bolt apply}} _without_ verbose, human outputter only prints a summary of the run * For {{bolt apply}} _with_ verbose, human outputter prints logs from each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet". * All output from this outputter can go to stdout (currently messages go to stderr for plans)JSON outputter: * When in non-plan mode behaves as it does currently. * Logs entire JSON format of {{apply}} result on stderr for each node at {{--verbose}} * This outputter can show intermediate results on stderr in human format, but doesn't have to for this ticketLog output: * The default console log level is now "warn". No "human-oriented" output should come from the logger except for warnings and errors. * Log files still default to "info". * {{\-\-debug}} still sets debug level for console logger, {{ \ - \- verbose}} does not affect the logger at all * A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the loggerPuppet log functions: * Eventually these should be handled by the outputter rather than the logger directly, but this is left to a later ticket.apply_prep/get_resources: * These probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting * All actions (plan start/finish, step start/finish, node start/result) are handed to the outputter as an event stream.* {{--verbose}} becomes an option for the outputter not the logger.* "verbose" is now defined to mean node-level results are included in the output when using the human format. "verbose" has no meaning for the JSON format.* Plans default to non-verbose, everything else defaults to verbose. {{ \ - \ -no \ -verbose}} is accepted as an addition to {{--verbose}}* "plan logging" becomes an outputter concept, rather than an executor concept , used by the json outputter initially * {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* For {{bolt apply}} _without_ verbose, human outputter only prints a summary of the run* For {{bolt apply}} _with_ verbose, human outputter prints logs from each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet".* All output from this outputter can go to stdout (currently messages go to stderr for plans)JSON outputter:* When in non-plan mode behaves as it does currently.* Logs entire JSON format of {{apply}} result on stderr for each node at {{--verbose}}* This outputter can show intermediate results on stderr in human format, but doesn't have to for this ticketLog output:* The default console log level is now "warn". No "human-oriented" output should come from the logger except for warnings and errors.* Log files still default to "info".* {{--debug - }} still sets debug level for console logger, {{- - verbose}} does not affect the logger at all* A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the loggerPuppet log functions:* Eventually these should be handled by the outputter rather than the logger directly, but this is left to a later ticket.apply_prep/get_resources:* These probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions (plan start/finish, step start/finish, node start/result) are handed to the outputter as an event stream.* {{--verbose}} becomes an option for the outputter not the logger.* "verbose" is now defined to mean node-level results are included in the output when using the human format. "verbose" has no meaning for the JSON format.* Plans default to non-verbose, everything else defaults to verbose. {{ \ - \ -no \ -verbose}} is accepted as an addition to {{--verbose}}* "plan logging" becomes an outputter concept, rather than an executor concept, used by the json outputter initially* {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* For {{bolt apply}} _without_ verbose, human outputter only prints a summary of the run* For {{bolt apply}} _with_ verbose, human outputter prints logs from each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet".* All output from this outputter can go to stdout (currently messages go to stderr for plans)JSON outputter:* When in non-plan mode behaves as it does currently.* Logs entire JSON format of {{apply}} result on stderr for each node at {{--verbose}}* This outputter can show intermediate results on stderr in human format, but doesn't have to for this ticketLog output:* The default console log level is now "warn". No "human-oriented" output should come from the logger except for warnings and errors.* Log files still default to "info".* {{--debug}} still sets debug level for console logger, {{--verbose}} does not affect the logger at all* A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the loggerPuppet log functions:* Eventually these should be handled by the outputter rather than the logger directly, but this is left to a later ticket.apply_prep/get_resources:* These probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions and plan output function ( notice plan start / warm finish, step start / etc finish, node start/result ) are handed to the outputter as an event stream .* {{--verbose}} becomes an option for the outputter not the logger.* By default " single actions verbose " {{bolt command run}} ({{bolt task run}} as opposed is now defined to {{bolt plan run}}) mean node-level results are run verbosely included in the output when using the human format . "verbose" has no meaning for the JSON format.* Plans default to _non_-verbose, everything else defaults to verbose. {{--no-verbose}} is accepted as an option addition to override this behavior. {{--verbose}} * "plan logging" becomes and an outputter concept , rather than an executor concept, used by the json outputter initially* {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* With For {{bolt apply }} _without_ verbose, human outputter only prints a summary of entire the run without verbose * With For {{ --verbose bolt apply }} apply _with_ verbose, human outputter prints logs from the each report showing at least changes. This is probably notice level messages and above, maybe excluding messages where the source is "Puppet". * All output from this outputter can go to stdout (currently messages go to stderr for plans) JSON outputter:* When in non-plan mode behaves are as it does currently.* When in plan mode logs only the plan Logs entire JSON format of {{apply}} result to stdout. on stderr for each node at {{--verbose}} * When in plan mode and verbose mode sends This outputter can show intermediate results to on stderr in human format, but doesn't have to for this ticketLog output:* The default console log level is now "warn" . (perhaps through No "human-oriented" output should come from the logger except for warnings and errors . notice?) * logs entire jsonformat of apply result on stderr Log files still default to "info".* {{--debug}} still sets debug level for each node at console logger, {{--verbose}} does not affect the logger at all * A "logger outputter" should consume the event stream and translate each event to appropriate log messages that are passed to the logger Puppet log functions:* Eventually these should be handled by the outputter rather then than the logger directly , but this is left to a later ticket.apply_prep/get_resources:* these These probably need to have specific events the
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Nick Lewis
ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions and plan output function(notice/warm/etc) are handed to the outputter.* {{--verbose}} becomes an option for the outputter not the logger.* By default "single actions" {{bolt command run}} ( {{bolt task run}} as opposed to {{bolt plan run}} ) are run with verbosely. {{-- verbose}} {{-- no-verbose}} becomes and is an option to override this behavior.* "plan logging" becomes and outputter concept used by the json outputter initially* {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* With apply human outputter only prints summary of entire run without verbose* With {{--verbose}} apply human outputter prints logs from the report showing at least changes.JSON outputter:* When in non-plan mode behaves are it does currently.* When in plan mode logs only the plan result to stdout.* When in plan mode and verbose mode sends intermediate results to stderr.(perhaps through logger.notice?)* logs entire jsonformat of apply result on stderr for each node at {{--verbose}}Puppet log functions:* Eventually these should be handled by the outputter rather then the logger directly but this is left to a later ticket.apply_prep/get_resources:* these probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}
Add Comment
Jira (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Nick Lewis Component/s: DOCS 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-1219) Bump bolt-vanagon puppet dependency to 6.4.0
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1219 Bump bolt-vanagon puppet dependency to 6.4.0 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1219) Bump bolt-vanagon puppet dependency to 6.4.0
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1219 Bump bolt-vanagon puppet dependency to 6.4.0 Issue Type: Task Assignee: Unassigned Created: 2019/03/29 10:34 AM Priority: Normal Reporter: Nick Lewis Puppet 6.4.0 is needed for YAML plans, so we need to add that dependency to the package. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1219) Bump bolt-vanagon puppet dependency to 6.4.0
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1219 Bump bolt-vanagon puppet dependency to 6.4.0 Change By: Nick Lewis 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Nick Lewis 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-1218) Improve documentation for Simple plans
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1218 Improve documentation for Simple plans 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1193) Analytics for simple plan usage
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1193 Analytics for simple plan usage Change By: Nick Lewis 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1193) Analytics for simple plan usage
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1193 Analytics for simple plan usage 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1190) Fix scope for run_plan
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1190
Fix scope for run_plan
Change By:
Nick Lewis
Release Notes Summary:
Variables defined in scope in a plan will no longer be visible to sub-plans called via {{run_plan}}.
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-1190) Fix scope for run_plan
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1190 Fix scope for run_plan Change By: Nick Lewis 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1190) Fix scope for run_plan
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1190 Fix scope for run_plan 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1197 Allow $nodes as second positional arg for run_plan() Change By: Nick Lewis 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.
