Jira (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Michael Smith Release Notes Summary: Bolt no longer requires the puppet_agent module be installed in PE to run 'apply' actions via Orchestrator. 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-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-815) Mark bolt_shim file content arguments as sensitive
Title: Message Title Michael Smith commented on BOLT-815 Re: Mark bolt_shim file content arguments as sensitive Let's plan a Z-release of bolt_shim. 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-817) Support an array of directories for modulepath in config
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-817 Support an array of directories for modulepath in config Change By: Alex Dreyer 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 (PUP-9339) Refresh only resources do not get a status event in the report
Title: Message Title Kris Bosland created an issue Puppet / PUP-9339 Refresh only resources do not get a status event in the report Issue Type: Bug Assignee: Unassigned Created: 2018/12/04 3:45 PM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Kris Bosland Refresh only resources, like reboot or some execs, do not create a status event in the report. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9312) puppet package provider fails when reading from registry
Title: Message Title Glenn Sarti commented on PUP-9312 Re: puppet package provider fails when reading from registry Merged into 5.5.x at; https://github.com/puppetlabs/puppet/commit/2b27922b79df7e4f93126d5b301ff18c72918105 Passed CI at; 15fbb8f465bd283a3f0028c5323a49d398fd9467 includes these changes Last known good build of puppet-agent on 5.5.x: Built at: 4 Dec 2018 9:52:59 PUPPET_AGENT_VERSION: 5.5.8.79.g239dafa PUPPET_AGENT_COMMIT: 239dafac020ca6a697bf2c5ac1fb4e548e9b06a4 PUPPET_AGENT_SHORT_COMMIT: 239dafac0 FACTER_COMMIT: 79c5167a0f50a6a837c84d054f373075eab41ea8 PUPPET_COMMIT: 15fbb8f465bd283a3f0028c5323a49d398fd9467 HIERA_COMMIT: 932e32a6730ccb49f800d9c4d7c7b581b30b6680 PXPAGENT_COMMIT: b1fd8b3ac8ef6583a7cb4156c5c4f1e19738f118
Jira (BOLT-815) Mark bolt_shim file content arguments as sensitive
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-815 Mark bolt_shim file content arguments as sensitive 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-815) Mark bolt_shim file content arguments as sensitive
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-815 Mark bolt_shim file content arguments as sensitive 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-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-510 I want to name nodes in inventory separately from their URL/hostname Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-978) Package Bolt for Fedora 28/29
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-978 Package Bolt for Fedora 28/29 Change By: Michael Smith Summary: Package Bolt for Fedora 27/ 28/29 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-953) Add file_upload support to BoltSpec
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-953 Add file_upload support to BoltSpec Change By: Michael Smith Issue Type: Task New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-963) Add group membership key to Target, and `group` accessor function
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-963 Add group membership key to Target, and `group` accessor function Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-952) Update developer docs to send files array
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-952 Update developer docs to send files array Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-897) Document a workaround for resolving IPs from PuppetDB
Title: Message Title Michael Smith commented on BOLT-897 Re: Document a workaround for resolving IPs from PuppetDB This is a limitation of --query, I don't know any workarounds or clear ways to address it. 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-612) Some docs only list unix paths, not Windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-612 Some docs only list unix paths, not Windows Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-610) Make transport API public and allow custom transport configuration
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-610 Make transport API public and allow custom transport configuration Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-920) Bolt unable to connect with ecdsa key
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-920 Bolt unable to connect with ecdsa key Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-504) I want to assign targets to an inventory group in my plan
Title: Message Title Lucy Wyman commented on BOLT-504 Re: I want to assign targets to an inventory group in my plan Should this be part of the Dynamic Inventory epic? I don't think it's duplicated there. 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-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Michael Smith 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-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Michael Smith Labels: 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-963) Add group membership key to Target, and `group` accessor function
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-963
Add group membership key to Target, and `group` accessor function
Change By:
Lucy Wyman
* * As a* * bolt plan author* * I want* * to be able to set a conditional based on a target's inventory group membership* * So that* * I can make decisions based on which groups the target is a part of.There are 2 parts to this:1. A target needs to 'know' which groups it's a part of and2. The groups key needs to be surfaced to the user.I think this makes the most sense as an attribute on the {{Bolt::Target}} object, similar to {{features}}, with a function that will get the groups a target is in from the inventory and another function {{groups}} which will be callable by the user from a plan.Questions:1. Is this a 'good idea' / something we want? It was a feature request in slack, and I think makes sense, but isn't something we've discussed yet as a team2. How should the target collect the list of groups it's in? How does it 'refresh' if the group membership changes? Does it get recalculated for every {{groups}} call?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-952) Update developer docs to send files array
Title: Message Title Lucy Wyman commented on BOLT-952 Re: Update developer docs to send files array This is still out of date 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-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Michael Smith commented on BOLT-510 Re: I want to name nodes in inventory separately from their URL/hostname Forgot to add pre-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-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-510 I want to name nodes in inventory separately from their URL/hostname Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-510 I want to name nodes in inventory separately from their URL/hostname Change By: Michael Smith Labels: docs Release Notes Summary: Aliases can now be added to a node in inventory as an alternate name whereby you may refer to that node. 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-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-510 I want to name nodes in inventory separately from their URL/hostname Change By: Michael Smith Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-510 I want to name nodes in inventory separately from their URL/hostname Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1010) Handle exceptions when parsing target URI
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1010 Handle exceptions when parsing target URI Issue Type: Bug Affects Versions: BOLT 1.4.0 Assignee: Unassigned Created: 2018/12/04 11:35 AM Priority: Normal Reporter: Cas Donoghue Currently exceptions raised in `Addressable::URI.parse` ( https://github.com/puppetlabs/bolt/blob/5bcdeaed91da4d62910619678d75ae667551f2cb/lib/bolt/target.rb#L56-L64 ) are not caught when initializing a `Target` object. Exceptions should be caught and transformed to a bolt specific error. Example: cas@cas-ThinkPad-T460p:~/working_dir/bolt/Boltdir/modules/test/tasks$ bolt command run whoami -n invalid:port bundler: failed to load command: bolt (/home/cas/working_dir/bolt/.bundle/ruby/2.5.0/bin/bolt) Addressable::URI::InvalidURIError: Invalid port number: "port" /home/cas/working_dir/bolt/.bundle/ruby/2.5.0/gems/addressable-2.5.2/lib/addressable/uri.rb:1373:in `port='
Jira (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-986) Plan executor run orchestrator plan_tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-986 Plan executor run orchestrator plan_tasks Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1009) plan-executor should finish plans
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1009 plan-executor should finish plans Issue Type: Sub-task Assignee: Unassigned Created: 2018/12/04 10:11 AM Priority: Normal Reporter: Alex Dreyer The plan executor should send a plan-finish command to orchestrator with the plan result when it is done running. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1008) implement applicator for plan executor
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1008 implement applicator for plan executor Issue Type: Sub-task Assignee: Unassigned Created: 2018/12/04 10:11 AM Priority: Normal Reporter: Alex Dreyer The plan-executor should have it's own implementation of the bolt applicator that raises not implemented errors for all methods. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1007) Implement new executor for plan-exeutor
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1007 Implement new executor for plan-exeutor Change By: Alex Dreyer The plan executor should have it's own implementation of the bolt executor. It should expose the same API to plan functions but should use the orchestrator transport only. It should bypass the "plan_start" command normally handled by the orchestrator client. Out of scope- configuring the puppetdb client- passing ssh/winrm connection info to orhcestrator. Only the hostname of nodes should be passed. 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
Jira (BOLT-1007) Implement new executor for plan-exeutor
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1007 Implement new executor for plan-exeutor Issue Type: Sub-task Assignee: Unassigned Created: 2018/12/04 10:09 AM Priority: Normal Reporter: Alex Dreyer The plan executor should have it's own implementation of the bolt executor. It should expose the same API to plan functions but should use the orchestrator transport only. Out of scope configuring the puppetdb client passing ssh/winrm connection info to orhcestrator. Only the hostname of nodes should be passed. Add Comment
Jira (BOLT-923) Orchestrator Client gem seems to be unsupported on Windows
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-923 Orchestrator Client gem seems to be unsupported on Windows Change By: David Kramer 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-756) Bolt crashes with invalid puppetdb config
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-756 Bolt crashes with invalid puppetdb config Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-830) Running a script via PCP fails on Windows
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-830 Running a script via PCP fails on Windows Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-987) Add CLI front end to plan executor
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-987 Add CLI front end to plan executor Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-724) Ability to specify Puppetfile in config and CLI
Title: Message Title Michael Smith commented on BOLT-724 Re: Ability to specify Puppetfile in config and CLI Our suggested solution for using a local one is to add an empty bolt.yaml to your control repo. I know this has some downsides around pulling inventory from a user directory. Config needs a bit of work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-565) Apply from Plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-565 Apply from Plans Change By: David Kramer Epic Status: To Do Done 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-969) bolt-server clears its tmpdir during cache purging
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-969 bolt-server clears its tmpdir during cache purging Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-938) Account for more than one entry in bolt.yaml puppetdb.server_urls parameter
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-938 Account for more than one entry in bolt.yaml puppetdb.server_urls parameter Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-997) puppet_agent::install doesn't match on RedhatEnterpriseServer platform
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-997 puppet_agent::install doesn't match on RedhatEnterpriseServer platform Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-938) Account for more than one entry in bolt.yaml puppetdb.server_urls parameter
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-938
Account for more than one entry in bolt.yaml puppetdb.server_urls parameter
Change By:
David Kramer
Bolt allows you to configure connection to PuppetDB in its {{bolt.yaml}} file. E.g.{code:title=bolt.yaml}---puppetdb: server_urls: ["pdb1.tld", "pdb2.tld"]{code}However, only the first element of the {{server_urls}} array is respected.We should either print warnings about additional elements being ignored, or else implement a fall-back algorithm for using additional urls when the first url fails. The fall-back algorithm can be cribbed from the puppetdb terminus 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 post to this group, send email to
Jira (BOLT-986) Plan executor run orchestrator plan_tasks
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-986 Plan executor run orchestrator plan_tasks Change By: Michael Smith Plans that use run_* functions on pcp nodes should work after this ticket.* The orchestrator should use whitelist certs to authenticate plan_task and plan_finish requests. Those tasks should be saved as the API User.(make new comidi app for all bolt-executor endpoints* The plan-executor should be configurable to connect to the correct orchestrator and use the correct client certs* tasks should be run with the "plan_task" endpoint.* this should pass hostname of the target as node-name regardless of the targets "transport".* commands/scripts/file-uploads should use the bolt-shim task.* All task runs should be logged in the plan-executor.* apply statements should error with not implemented.* When a plan finishes the plan result should be posted back to orchestrator. This should happen even if no actions are run through the Orchestrator as part of the plan. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-986) Plan executor run orchestrator plan_tasks
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-986 Plan executor run orchestrator plan_tasks Change By: Michael Smith Plans that use run_* functions on pcp nodes should work after this ticket.* The orchestrator should use whitelist certs to authenticate plan_task and plan_finish requests. Those tasks should be saved as the API User.(make new comidi app for all bolt-executor endpoints* The plan-executor should be configurable to connect to the correct orchestrator and use the correct client certs* tasks should be run with the "plan_task" endpoint.* this should pass hostname of the target as node-name regardless of the targets "transport".* commands/scripts/file-uploads should use the bolt-shim task.* All task runs should be logged in the plan-executor.* apply statements should error with not implemented.* When a plan finishes the plan result should be posted back to orchestrator. This That should happen even if no actions are run through the Orchestrator as part of the plan. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1006) Add top-level comidi route for bolt-server
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1006 Add top-level comidi route for bolt-server Change By: Alex Dreyer In order to authenticate using certs, we want to authenticate with bolt-related endpoints using those certs generally to avoid threading certs intricately through orchestrator. We should create a new top-level route for plan_task and plan_finish endpoints that the plan-executor will call. The API user should be the only user allowed to post plan_task or plan_finish commands through this route since it will bypass the same user check of the normal commands. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (BOLT-986) Plan executor run orchestrator plan_tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-986 Plan executor run orchestrator plan_tasks Change By: Alex Dreyer Plans that use run_* functions on pcp nodes should work after this ticket.* The orchestrator should use whitelist certs to authenticate plan_task and plan_finish requests. Those tasks should be saved as the API User. (make new comidi app for all bolt-executor endpoints * The plan-executor should be configurable to connect to the correct orchestrator and use the correct client certs* tasks should be run with the "plan_task" endpoint.* this should pass hostname of the target as node-name regardless of the targets "transport".* commands/scripts/file-uploads should use the bolt-shim task.* All task runs should be logged in the plan-executor.* apply statements should error with not implemented.* When a plan finishes the plan result should be posted back to orchestrator. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this
Jira (BOLT-986) Plan executor run orchestrator plan_tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-986 Plan executor run orchestrator plan_tasks Change By: Alex Dreyer Plans that use run_* functions on pcp nodes should work after this ticket.* The orchestrator should use whitelist certs to authenticate plan_task and plan_finish requests. Those tasks should be saved as the API User. * The plan-executor should be configurable to connect to the correct orchestrator and use the correct client certs* tasks should be run with the "plan_task" endpoint.* this should pass hostname of the target as node-name regardless of the targets "transport".* commands/scripts/file-uploads should use the bolt-shim task.* apply statements should error with not implemented.* All task runs should be logged in the plan-executor. * apply statements should error with not implemented.* When a plan finishes the plan result should be posted back to orchestrator. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received
Jira (BOLT-1006) Add top-level comidi route for bolt-server
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1006 Add top-level comidi route for bolt-server Issue Type: Sub-task Assignee: Unassigned Created: 2018/12/04 9:35 AM Priority: Normal Reporter: Lucy Wyman In order to authenticate using certs, we want to authenticate with bolt-related endpoints using those certs generally to avoid threading certs intricately through orchestrator. We should create a new top-level route for plan_task and plan_finish endpoints that the plan-executor will call. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Michael Smith commented on BOLT-940 Re: apply_prep doesn't work with pcp nodes and released puppet_agent I misread the description: the goal wasn't necessarily to get a puppet_agent release with our tasks out. When running apply_prep over PCP, we can skip the puppet_agent tasks and go directly to collecting facts because we know the agent is installed. 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.
