Jira (BOLT-1541) Bolt docs improvement regarding example code
Title: Message Title Alex Dreyer assigned an issue to Heston Hoffman Puppet Task Runner / BOLT-1541 Bolt docs improvement regarding example code Change By: Alex Dreyer Assignee: Heston Hoffman Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.349117.1583793508000.71621.1590610680102%40Atlassian.JIRA.
Jira (PUP-10397) Remove facts and vars from ScriptCompiler scope
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-10397 Remove facts and vars from ScriptCompiler scope Change By: Alex Dreyer Release Notes: Bug Fix Release Notes Summary: Removes node specific values from the scope of script compiles since they don't happen in the context of a node. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.351426.1585328999000.45290.1587651180239%40Atlassian.JIRA.
Jira (PUP-10379) Add new Puppet::Node::Environment subclass that will also load the current directory as a module
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-10379 Add new Puppet::Node::Environment subclass that will also load the current directory as a module Change By: Alex Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.350706.158473000.45285.158765127%40Atlassian.JIRA.
Jira (PUP-6553) Environment compiler and app_management language need to support hiera lookups
Title: Message Title Alex Dreyer commented on PUP-6553 Re: Environment compiler and app_management language need to support hiera lookups oddly we're working on adding facts to plans right now and would prefer this behavior. Close it. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.110079.1450450499000.15847.1584564840031%40Atlassian.JIRA.
Jira (PUP-10138) Task Resource Type that behaves like an improved file->exec
Title: Message Title
Alex Dreyer updated an issue
Puppet / PUP-10138
Task Resource Type that behaves like an improved file->exec
Change By:
Alex Dreyer
A common pattern in puppet is to ensure a script file is present then execute that script. Now that users are writing scripts as tasks for use with bolt and PE it's desirable to reuse these tasks during enforcement runs. Users should be able to refer to a task by name, explicitly pass parameters. The provider should handle downloading the task and any required files and executing it according to the task spec. {noformat}task{ 'running a task': task => 'task::name' # namevar? parameters => {p1 => foo, } , creates => '/foo/bar' } {noformat}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "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
Jira (PUP-10138) Task Resource Type that behaves like an improved file->exec
Title: Message Title Alex Dreyer commented on PUP-10138 Re: Task Resource Type that behaves like an improved file->exec I think it would need the same constraints as execs do around when the task actually gets run. I think caching the task file between runs is preferable but not a hard requirement. That is what pxp-agent does. The location should be hidden from the user though. The task resource should download the task from the same puppet master it gets files from. 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.334977.1573665969000.45405.1574722440132%40Atlassian.JIRA.
Jira (PUP-8076) language specification needs to be updated with changes from feature_puppet-tasks
Title: Message Title Alex Dreyer commented on PUP-8076 Re: language specification needs to be updated with changes from feature_puppet-tasks No we haven't but formalizing the features of the plan language is something I'm starting 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.217205.1508413541000.41864.1574358480165%40Atlassian.JIRA.
Jira (PUP-10138) Task Resource Type that behaves like an improved file->exec
Title: Message Title
Alex Dreyer created an issue
Puppet / PUP-10138
Task Resource Type that behaves like an improved file->exec
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/11/13 9:26 AM
Priority:
Normal
Reporter:
Alex Dreyer
A common pattern in puppet is to ensure a script file is present then execute that script. Now that users are writing scripts as tasks for use with bolt and PE it's desirable to reuse these tasks during enforcement runs. Users should be able to refer to a task by name, explicitly pass parameters. The provider should handle downloading the task and any required files and executing it according to the task spec.
task{ 'running a task':
task => 'task::name' # namevar?
parameters => {
p1 => foo,
}
}
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title Alex Dreyer commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows It was specifically about saving the runspace between commands on winrm if we're going to on local. If we're not doing that I don't have any concerns. 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.314131.1561529132000.76411.1567005480317%40Atlassian.JIRA.
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title Alex Dreyer commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows Would that be implemented for winrm too? I'm concerned about state being left around in some cases but not others. We also originally had concerns about us not being able to manage that state reliably, 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.314131.1561529132000.75037.1566935940292%40Atlassian.JIRA.
Jira (BOLT-1478) Scripts without explicit interpreters don't work
Title: Message Title Alex Dreyer commented on BOLT-1478 Re: Scripts without explicit interpreters don't work Not executing files by default on windows is intentional based on feedback from the windows team it was decided that known handlers are often set up for GUI interactions and should not be just run. 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.317565.156386822.61963.1566255000756%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Alex Dreyer commented on BOLT-1384 Re: Inventory command I don't think just removing the final line is a good long term solution. We intended to solve multiple use cases with the fix we added one of which was predicting what target a bolt command would run on. In that case the count is useful. In general the default "human" output for bolt is not intended to be stable for consumption from bash scripts which is why we've discussed a "oneline" format in the past. If we do add oneline support for this feature we should make sure to add some information beyond the 'name' to force the user to use cut in the initial release otherwise we'll likely break the output in the future. 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.312167.1560296026000.52730.1565651700226%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Alex Dreyer commented on BOLT-1384 Re: Inventory command This seems like a usecase for the often discussed `--format oneline` 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.312167.1560296026000.52590.1565649120314%40Atlassian.JIRA.
Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1487 Make it easier for users to know and turn off analytics at install time Change By: Alex Dreyer Release Notes Summary: Print a warning for new users before sending any analytics. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318117.1564082501000.47524.1565218320948%40Atlassian.JIRA.
Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1487 Make it easier for users to know and turn off analytics at install time Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318117.1564082501000.47522.1565218260149%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Alex Dreyer commented on BOLT-1384 Re: Inventory command Does --format=json 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312167.1560296026000.42173.1564777020136%40Atlassian.JIRA.
Jira (BOLT-1449) Load Task based Plugins from the modulepath
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1449 Load Task based Plugins from the modulepath Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314983.1562079167000.34467.1564422600510%40Atlassian.JIRA.
Jira (BOLT-1449) Load Task based Plugins from the modulepath
Title: Message Title Alex Dreyer commented on BOLT-1449 Re: Load Task based Plugins from the modulepath This will end up needing a PUP ticket. 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.314983.1562079167000.34466.1564422600504%40Atlassian.JIRA.
Jira (BOLT-1207) Bolt should inform users when there is a new version available
Title: Message Title Alex Dreyer commented on BOLT-1207 Re: Bolt should inform users when there is a new version available I don't think bolt update check will improve our upgrade rate. If you think to check you're probably already upgrading. I think this either needs to be a CLI message or it's probably not worth doing. 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.301658.1553614758000.32653.1564156260155%40Atlassian.JIRA.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Alex Dreyer commented on BOLT-1433 Re: get_resources does not work with resource objects. Henrik Lindberg I agree we'll need to load the resource types. I'm not exactly sure what you mean by the "work" though. One of our longer term goals is to make bolt more resource aware. During a plan you should be able to discover resources and track changes made to those resources. The get_resources function is the first step towards this. 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.314362.1561649732000.32616.1564155060449%40Atlassian.JIRA.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Change By: Alex Dreyer Release Notes Summary: Bolt will now send report how the boltdir was determined to analytics information about which type of project directory . IE is being used the user default, from a dir with bolt . yaml, from a dir called Boltdir, or explicitly specified 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.309059.1558038203000.29115.1563985800376%40Atlassian.JIRA.
Jira (BOLT-1410) Add plugin analytics
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1410 Add plugin analytics Change By: Alex Dreyer Release Notes Summary: Bolt will now send an analytics event when the built in inventory plugins are used. Release Notes: Not Needed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313047.1560895161000.28275.1563924120139%40Atlassian.JIRA.
Jira (BOLT-1455) out::message messages don't print when format=json
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1455
out::message messages don't print when format=json
Change By:
Alex Dreyer
{{out:message}} calls should be delegated to the logger by the json 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.315274.1562178132000.5687.1562180408934%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1453) Add facts_collection plugin
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1453 Add facts_collection plugin Issue Type: New Feature Assignee: Unassigned Created: 2019/07/02 12:58 PM Priority: Normal Reporter: Alex Dreyer Currently apply_prep runs facter on targets. Users should be able to add and configure their own facts collection plugins in bolt.yaml and/or inventory.yaml Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1452) Add plugin hook to manage agent installation
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1452 Add plugin hook to manage agent installation Issue Type: New Feature Assignee: Unassigned Created: 2019/07/02 12:51 PM Priority: Normal Reporter: Alex Dreyer Currently bolt runs the puppet_agent::install task and exposes no options for how the agent is installed. We should add a new plugin hook puppet_libraries? that will allow users to replace the default behavior. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1449) Load Task based Plugins from the modulepath
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1449 Load Task based Plugins from the modulepath Issue Type: New Feature Assignee: Unassigned Created: 2019/07/02 7:52 AM Priority: Normal Reporter: Alex Dreyer Users should be able to implement plugin hooks as tasks that are loaded from the modulepath and configure those plugins in bolt.yaml. Implementation: The plugin name is the same as the module name. Bolt should look for a task name matching the hook name to run.(ie my_plugin::inventory_targets) Plugins have metadata at the top level of the module bolt_plugins.json bolt_plugins.json has a config key that describes the schema of the plugins bolt.yaml configuration. If there is a config key than a configuration hash will be passed to all hooks as the metaparameter _config _boltdir will be passed as a metaparameter to the plugin tasks. Hook Formats: inventory_targets: arbitrary plugin specific parameters(based on task's metadata) inventory_config: arbitrary plugin specific parameters(based on task's metadata) createkeys: no parameters encrypt: encrypted_value: encoded encrypted value ie ENC[GPG] decrypt: plaintext_value: base 64 encoded plain text value to encrypt.
Jira (BOLT-1449) Load Task based Plugins from the modulepath
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1449
Load Task based Plugins from the modulepath
Change By:
Alex Dreyer
Users should be able to implement plugin hooks as tasks that are loaded from the modulepath and configure those plugins in bolt.yaml. h2. Implementation : * The plugin name is the same as the module name.* Bolt should look for a task name matching the hook name to run.(ie my_plugin::inventory_targets)* Plugins have metadata at the top level of the module {{ bolt_plugins bolt_plugin .json}}* {{ bolt_plugins bolt_plugin .json}} has a {{config}} key that describes the schema of the plugins {{bolt.yaml}} configuration.* If there is a config key than a configuration hash will be passed to all hooks as the metaparameter {{_config}}* {{_boltdir}} will be passed as a metaparameter to the plugin tasks. * plugin tasks will only support running on {{localhost}} and should use the same PAL/executor as the task plugin h2. Hook Formats : h3. inventory_targets : arbitrary plugin specific parameters(based on task's metadata) h3. inventory_config : arbitrary plugin specific parameters(based on task's metadata) h3. validate_inventory_configarbitrary plugin specific parametersIf no hook is provided the parameters should be validated against the inventory_config task metadata.h3. createkeys : no parameters h3. encrypt : encrypted_value: encoded encrypted value ie ENC[GPG] h3. decrypt : plaintext_value: base 64 encoded plain text value to encrypt. h2. QuestionsDo we need to version the hook formats immediately?Can a module be a plugin without a {{bolt_plugin.json}}Should we support {{bolt_plugin.yaml}}? No this should not happen unless we want to support task metadata.yaml
Add Comment
Jira (BOLT-1410) Add plugin analytics
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1410 Add plugin analytics Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313047.1560895161000.2082.1562005020209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1408) Task plugins
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1408
Task plugins
Change By:
Alex Dreyer
Release Notes Summary:
The {{task}} plugin now allows you to run a task to discover targets or lookup configuration information in the version 2 inventory file.
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.313043.1560894346000.766.1561742220323%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1408) Task plugins
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1408 Task plugins Change By: Alex Dreyer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313043.1560894346000.763.1561742160292%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1168) Add catch_errors and better handling to apply_prep
Title: Message Title Alex Dreyer commented on BOLT-1168 Re: Add catch_errors and better handling to apply_prep I think so. We should verify and perhaps mention that in the apply_prep 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.298893.1551982151000.64125.1561665240396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-414) Run a task with different parameters per target
Title: Message Title Alex Dreyer commented on BOLT-414 Re: Run a task with different parameters per target Writing a plan that runs multiple tasks in sequence is slow since you have to wait for the task to finish on one target before starting it on the next. This could be solved with concurrency but it also relates to hiera data bindings. 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.242960.1522085962000.64002.1561661280204%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Encrypted parameters for tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-235 Encrypted parameters for tasks Change By: Alex Dreyer Summary: Encrypteded Encrypted parameters for tasks 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.223860.1511432259000.63992.1561661041080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Encrypteded parameters for tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-235 Encrypteded parameters for tasks Change By: Alex Dreyer Summary: Create encrypted variables in Encrypteded parameters for tasks 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.223860.1511432259000.63985.1561661040754%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Create encrypted variables in tasks
Title: Message Title Alex Dreyer commented on BOLT-235 Re: Create encrypted variables in tasks I think this is about encrypted parameters to a task rather then connection information to the target. 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.223860.1511432259000.63980.1561660980553%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1433 get_resources does not work with resource objects. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314362.1561649732000.63731.1561655880254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1433
get_resources does not work with resource objects.
Change By:
Alex Dreyer
We document {{get_resources(localhost, Package)}} as an example of how to use get_resources and the function itself is defined to accept Resource objects in addition to strings. However Resource Types are not loaded during a plan so unless you quote the resource name and pass it as a string the plan will error.{{"Evaluation Error: Resource type not found: Package[...]}} Users should be able to use core types like {{Package}} and {{File}} or any custom types available on the module path with {{get_resources}} which may change how these objects behave more generally in the plan language.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1433 get_resources does not work with resource objects. Issue Type: New Feature Assignee: Unassigned Created: 2019/06/27 8:35 AM Priority: Normal Reporter: Alex Dreyer We document get_resources(localhost, Package) as an example of how to use get_resources and the function itself is defined to accept Resource objects in addition to strings. However Resource Types are not loaded during a plan so unless you quote the resource name and pass it as a string the plan will error. "Evaluation Error: Resource type not found: Package[...] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1432) Examples on Bolt Site
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1432 Examples on Bolt Site Issue Type: New Feature Assignee: Unassigned Created: 2019/06/26 2:16 PM Priority: Normal Reporter: Alex Dreyer The Bolt site should have an examples section that is less structured/ordered than the hands on lab. Each example should have a markdown file and it's own module. We should document how to contribute examples. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows I think a note or warning in the modulepath docuementation makes sense too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.62029.1561566960662%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title Alex Dreyer commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows This feels like a bug, we should verify in slack that no one is relying on this behavior though. If not I don't think we need to expose a shell-command option yet. 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.314131.1561529132000.61802.1561562520484%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows Making modulepath case insensitive on windows would make project directories incompatible across platforms which seems worse. Also modules, tasks and the rest of the puppet objects won't be so it seems better for users to learn that puppet is case sensitive early. We may want to consider checking and warning when a path only exists in case sensitive form. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.59410.1561473300516%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1424) Vault plugin
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1424 Vault plugin Issue Type: New Feature Assignee: Unassigned Created: 2019/06/24 12:44 PM Priority: Normal Reporter: Alex Dreyer Users should be able to lookup passwords or other credential information for targets from Vault. We should document loading ssh private keys from vault in addition to a password example. 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 Alex Dreyer commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Rob Braden We really don't want users to remain on older versions of bolt. I don't want to loudly broadcast direct rpm installs since that will make it harder for less sophisticated users to upgrade. 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.58481.1561405020583%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1409) Remove 'lookups' from 'target_lookups'
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1409
Remove 'lookups' from 'target_lookups'
Change By:
Alex Dreyer
Release Notes Summary:
This deprecates the {{target-lookups}} key in the experimental inventory file v2. Users should migrate any {{target-lookups}} entries to {{targets}} and move the {{plugin}} key in each entry to {{_plugin}}. d
Release Notes:
Deprecation
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.313045.1560895034000.58404.1561403040296%40Atlassian.JIRA.
For more options, visit
Jira (BOLT-1408) Task plugins
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1408 Task plugins Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313043.1560894346000.56966.1561143060679%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Alex Dreyer commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo A related problem was reported by Reid Vandewiele who described how users who do not want to add a repository for installing bolt struggle to find the correct package in the tangled mess of directories in yum.puppet.com. We should probably host the new "puppet-tools" repository at a new domain to solve this problem too. 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.56810.1561137601912%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1406) out::message doesn't work inside without_default_logging
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1406 out::message doesn't work inside without_default_logging Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312979.1560875893000.56752.1561135800559%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1408) Task plugins
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1408 Task plugins Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313043.1560894346000.56746.1561135740835%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1408) Task plugins
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-1408 Task plugins Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313043.1560894346000.56748.1561135740939%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1270) Bolt should have an encrypted data store
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1270 Bolt should have an encrypted data store Change By: Alex Dreyer Release Notes Summary: Adds an a hiera eyaml compatible pkcs7 plugin and support for embedding eyaml data in the inventory. 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.306226.1556137243000.56270.1561075560192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1409) Remove 'lookups' from 'target_lookups'
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1409 Remove 'lookups' from 'target_lookups' Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313045.1560895034000.55421.1561049520415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1405) Allow users to set {{$environment}} for apply blocks
Title: Message Title
Alex Dreyer commented on BOLT-1405
Re: Allow users to set {{$environment}} for apply blocks
I think we generally don't want people to treat $environment specially in plans. So most of the behavior you described(except perhaps always being set) makes sense. I don't think plans should inherit environment just like they don't inherit other scope(anymore).
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.312966.1560869911000.52126.1560891780151%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1405) Allow users to set {{$environment}} for apply blocks
Title: Message Title
Alex Dreyer commented on BOLT-1405
Re: Allow users to set {{$environment}} for apply blocks
I don't think thats the case. We'd just have to check for a $environment variable when we're deserializing the plan scope for catalog compilation and name the environment after it when creating the temporary environment. It seems like expected behavior for plans where puppet environments are not really a thing.
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.312966.1560869911000.51977.1560886800148%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1405) Allow users to set {{$environment}} for apply blocks
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1405
Allow users to set {{$environment}} for apply blocks
Change By:
Alex Dreyer
Users should be able to set `$environment` for apply blocks so they can use existing hierarchies that reference environment.Possible implementations:Interface 1:{ { noformat} } apply($nodes, environment => 'foo'){ { noformat} } interface 2:{noformat}$environment = 'foo'apply($nodes){noformat}
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-1405) Allow users to set {{$environment}} for apply blocks
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1405
Allow users to set {{$environment}} for apply blocks
Change By:
Alex Dreyer
Users should be able to set `$environment` for apply blocks so they can use existing hierarchies that reference environment. Possible implementations: Interface 1:{{ noformat}} apply($nodes, environment => 'foo') {{noformat }}interface 2:{noformat}$environment = 'foo'apply($nodes){noformat}
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-1398) I want to see what nodes are in an inventory group
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1398
I want to see what nodes are in an inventory group
Change By:
Alex Dreyer
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.We should find what use cases current users have around displaying inventory. A workaround for now is to use a plan that returns the targets{noformat}plan resolve_targets( TargetSpec $nodes) { return(get_targets($nodes))}{noformat}
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-1405) Allow users to set {{$environment}} for apply blocks
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-1405
Allow users to set {{$environment}} for apply blocks
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/06/18 7:58 AM
Priority:
Normal
Reporter:
Alex Dreyer
Users should be able to set `$environment` for apply blocks so they can use existing hierarchies that reference environment. Interface 1: apply($nodes, environment => 'foo') interface 2: noformat $environment = 'foo' apply($nodes) noformat
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1397) The wait_until_available() function should return (or make accessible) details of why it timed out.
Title: Message Title Alex Dreyer commented on BOLT-1397 Re: The wait_until_available() function should return (or make accessible) details of why it timed out. This probably means tracking the last error received from each host and making it available in the details of the timeout error Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.312526.1560550967000.48290.1560551700178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1386) I need a workspace for files during the duration of a plan
Title: Message Title Alex Dreyer commented on BOLT-1386 Re: I need a workspace for files during the duration of a plan Henrik Lindberg That makes sense for reading files and accessing them from file resources/file_upload. 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.312278.1560378682000.46151.1560439740159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1386) I need a workspace for files during the duration of a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1386 I need a workspace for files during the duration of a plan Change By: Alex Dreyer Some plans build and distribute artifacts. These plans are hard to write because bolt does not have a `file_download` function or any natural space to store such artifacts. The project dir should provide a workspace that allows plans a central location to write and read data from.questions:1. Should this workspace persist between plans run in the same project?2. How can we ensure that files in the workspace are addressable in a way that doesn't conflict with modules. 3. How can 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
Jira (BOLT-1386) I need a workspace for files during the duration of a plan
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1386 I need a workspace for files during the duration of a plan Issue Type: New Feature Assignee: Unassigned Created: 2019/06/12 3:31 PM Priority: Normal Reporter: Alex Dreyer Some plans build and distribute artifacts. These plans are hard to write because bolt does not have a `file_download` function or any natural space to store such artifacts. The project dir should provide a workspace that allows plans a central location to write and read data from. questions: 1. Should this workspace persist between plans run in the same project? 2. How can we ensure that files in the workspace are addressable in a way that doesn't conflict with modules. Add Comment
Jira (BOLT-1118) Add a command that lists available modules and their versions
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1118
Add a command that lists available modules and their versions
Change By:
Alex Dreyer
As a bolt user, I need the ability to call up a list of the modules available in my workspace project . This will allow me to determine the names and versions of available modules along with their order of precedence.h2. Desired OutcomeA command similar to {{puppet module list}} that displays each module available in the Bolt environment.
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-1385) Update device integration tests
Title: Message Title Alex Dreyer commented on BOLT-1385 Re: Update device integration tests David Schmitt This is the bolt side ticket if you want to link it to the resource_api testing ticket. 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.312249.156036499.44721.1560365100394%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1385) Update device integration tests
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1385 Update device integration tests Issue Type: Task Assignee: Unassigned Created: 2019/06/12 11:43 AM Priority: Normal Reporter: Alex Dreyer Once puppet 6.5.0 is released with a fixed version of the resource_api we should update the device integration tests to: 1. Not update the rsapi gem that is installed on the puppet_6 agent target 2. Use the latest release of resource_api gem release in bolts gemfile 3. Run the device integration tests agasint the default run_on: localhost. Make sure the localhost case is using the latest release of the resource_api from bolt's gemfile. Add Comment This message was sent by Atlassian
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311712.1559939792000.42066.1560268920154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9747) Bolt provides too many attributes to remote transports
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-9747 Bolt provides too many attributes to remote transports Change By: Alex Dreyer From https://groups.google.com/a/puppet.com/forum/#!topic/team-network-automation/bEiFEudGyrc and private slack convo with [~alex]Bolt provides a lot of attributes to remote transports that the Resource API is not prepared to handle. Change the resource api transport layer to silently discard any attributes passed in as connection_info from the list of "default" attributes bolt provides if they do not match up the transport is not prepared to receive them.The following keys come from uri parsing in bolt and are likely to be used in transport schema 's schema but may not always . * For each discarded attribute that matches the list they should be filtered out when not present in the schema(from https://github.com/puppetlabs/puppet-resource_api#usable-within-the-schema emit with password added.):uri - Use when you need to specify a info message specific URL to connect to . All of the following keys will be computed from the uri if possible. In the future more url parts may be computed from the URI as well. * For each discarded attribute that matches host - Use to specify and IP or address to connect to.port - The port the list in transport should connect to.protocol - Use to specify which protocol the transport should use for example http, https ://github , ssh or tcpuser - The user the transport should connect as . com/puppetlabs/puppet password - resource_api#non the password to use when connectingThe following keys are meta keys bolt uses and should not be included in transport schemasrun - usable on - within This is used by bolt to determine which target to proxy to. Transports should not rely on this key.remote - the transport - schema emit a debug message This is used to determine which transport to load . It should always be the transport class name "declassified". remote- * For every other discarded attribute emit a warning message Any key starting with remote- is reserved for future use . These keys are reserved for future URI parsing use but not currenlty exposed.path - reserved as a uri partquery - reserved as a uri part Add Comment
Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1376 Support puppetfile -> forge -> baseurl setting in bolt.yaml Issue Type: New Feature Assignee: Unassigned Created: 2019/06/07 1:36 PM Priority: Normal Reporter: Alex Dreyer In order to use an internal forge mirror bolt needs to support the baseurl setting for r10k. This setting should be exposed in bolt.yaml under the puppetfile section. puppetfile: forge: baseurl: https://artifactory.internal.tld/api/puppet/forge
Jira (BOLT-1365) run_command should accept a list of acceptable exitcodes
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1365 run_command should accept a list of acceptable exitcodes Issue Type: New Feature Assignee: Unassigned Created: 2019/06/05 2:14 PM Priority: Normal Reporter: Alex Dreyer This comes up frequently with trying to run puppet agent -t but is useful in some other circumstances too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1363) Singular version of TargetSpec data type
Title: Message Title Alex Dreyer commented on BOLT-1363 Re: Singular version of TargetSpec data type Henrik Lindberg Without fundamentally changing how we interact with targets it's not possible. If I pass in a string 'foo' to a TargetSpec get_targets} could resolve that string to a single target in inventory, a group with any number of targets or a target that is not part of the inventory. We could validate what it resolves to before the plan is called but that plan could update the inventory for example by adding targets to an empty group. 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.311260.1559685174000.34988.1559747401649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1363) Singular version of TargetSpec data type
Title: Message Title Alex Dreyer commented on BOLT-1363 Re: Singular version of TargetSpec data type We can't use a simple type alias for this since a single string may refer to a group that represents multiple targets. For now the best workaround is to call `get_targets` at the top of the plan and verify that it returns a single result. In the future the best solution is for the cli call `get_targets` when a string is passed from the CLI to a `Target` parameter to solve this problem. A `get_target` function that ensures a string refers to a single target may make this easier to use in subplans. 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.311260.1559685174000.34316.1559686620182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1362) Support Plan Language Datatypes in tasks
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1362 Support Plan Language Datatypes in tasks Issue Type: New Feature Assignee: Unassigned Created: 2019/06/04 10:14 AM Priority: Normal Reporter: Alex Dreyer In many cases it's useful to interact with the plan language datatypes from a task for example to pass Targets to a task or use a task to discover Targets from a task. We should allow the plan language datatypes to be serialized and passed to a task as parameters We should deserialize these objects when returned from a task. The supported task helper libraries should support automatically deserializing these into native objects with plan language methods and attributes exposed We should support using these types in task Questions: How to balance serialization to limit bloat/size of the object(for example are facts serialized with a target? Is a target serialized with a result?) What does this mean for other UIs?
Jira (BOLT-1361) Docs for plan parameters are confusing
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-1361
Docs for plan parameters are confusing
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/06/04 9:50 AM
Priority:
Normal
Reporter:
Alex Dreyer
The docs show passing a TargetSpec spec parameter to a task. This only works when the TargetSpec does not include and realized `Target` objects. This example should be expanded to show targetting the `TargetSpec` only. We should document how to pass an array of target names to a task as well.
$names = get_targets($nodes).map |$n| { $n.name }
$run_task($nodes, configure_mesh, $names)
https://puppet.com/docs/bolt/latest/writing_plans.html#concept-2302
Jira (BOLT-1356) Make example strings documentation for a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1356 Make example strings documentation for a plan 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310714.1559175692000.33209.1559665440666%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1356) Make example strings documentation for a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1356 Make example strings documentation for a plan Change By: Alex Dreyer The canary plan should include doc strings that can be used to test and develop strings integrations. This should include:1. summary2. full description3. parameter descriptions4. return type 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.310714.1559175692000.33201.1559665380673%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1356) Make example strings documentation for a plan
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1356 Make example strings documentation for a plan Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310714.1559175692000.33205.1559665380840%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-836) Support Hiera lookup() in plans outside of apply blocks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-836 Support Hiera lookup() in plans outside of apply blocks Change By: Alex Dreyer h2. Feature RequestIt would be handy to support the hiera lookup() function within a plan.h2. Open QuestionWhat goes into the hierarchy for a plan? Without facter how are those values set? h2. Usecasesh4. Lookup different values to use the same plan in different environments or contextsAs a plan author i need to store data about how to execute the plan that may be environment or deployment specific. These settings would be looked up from the "perspective" of the bolt controller node. Example: may need different API keys, credentials, etc to use for API calls. Example 2: may be deploying in a different manner based on a setting in a config that is easy to switch.h4. Use hiera to lookup task parameters for different targetsAs a plan author i need to perform actions differently depending on certain facts and/or attributes of a node. These facts may be gather by the `facts` task. From these facts/attributes i then need to lookup() data to determine how the action should be run. These facts would be looked up from the "perspective" of specific targets. Example: I'm deploying a software pacakge against a variety of hosts, some may be 32-bit some 64-bit. I need to deploy different versions of software to the 32-bit systems. I would run a 'facts' task to determine architecture, then choose which software package to copy and install. The data hierarchy would be used to uniquely specify which software package to utilize.h2. Learning from spike* currently just exposing hiera allows backends to work without interpolation as long as all interpolation is based on $facts and $trusted. The fact that those are set during plan execution feels wrong and may be a bug.* We probably need the ability for users to specify a separate hiearchy for the plan level so we don't limit interpolation options.* There is value in exposing backends so that hiera-eyaml can be used but this problem may be solved by supporting eyaml in inventory. h1 Questions for commentors* What levels of heirarchy would you use at the plan level?* Would there be any fact like interpolations in the hierarchy? What values would be used.* Do you expect values from plan level data to be automatically set anywhere with data bindings like classes in manifests.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Alex Dreyer Comment: Is this about part of the module path User has this Bolt project folder:`C:\DATA\workshop` with a bolt.yaml in itand subsequently the modulepath becomes c:/data/workshop/modulesHowever no tasks/plans are ever found there.If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it worksBolt needs to be completely case insensitive on Windows, otherwise this breaks everything Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.23577.1559078100975%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Alex Dreyer Bolt won’t handle folder names with one or more uppercase characters in the name incorrectly, when they are part of the modulepath. I encountered this while doing a Bolt Workshop at KPN.If the modulepath has a capitalized foldername in it, not Tasks or Plans are found in that module. It is as if the module is not there. User has this Bolt project folder:`C:\DATA\workshop` with a bolt.yaml in itand subsequently the modulepath becomes c:/data/workshop/modulesHowever no tasks/plans are ever found there.If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it worksBolt needs to be completely case insensitive on Windows, otherwise this breaks everything Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows Is this about part of the module path User has this Bolt project folder: `C:\DATA\workshop` with a bolt.yaml in it and subsequently the modulepath becomes c:/data/workshop/modules However no tasks/plans are ever found there. If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it works Bolt needs to be completely case insensitive on Windows, otherwise this breaks everything Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.23575.1559078100882%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Alex Dreyer commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo My understanding from the original meeting was that we wanted a single repo that we could document for all users to prevent PE users from accidentally adding the FOSS puppet platform repo. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.22844.1559067420673%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1337) Make .filter called on a ResultSet return a ResultSet
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1337 Make .filter called on a ResultSet return a ResultSet Change By: Alex Dreyer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.22323.1559062500262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1330) Create a Bolt demo that can be run with little oversight based
Title: Message Title Alex Dreyer commented on BOLT-1330 Re: Create a Bolt demo that can be run with little oversight based I don't think demo-magic is going to be best tool for interactive demos. I suspect we want something we write ourselves that supports readline. 1. prints some instructions. 2. reads the command the user enters. Validates that command against the expected command. 3. prints a warning if the command is incorrect 4. runs the command 5. validates that the exit code is as expected. 6. asks the user for confirmation or if they want to run another command. 7. moves 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.309698.1558539239000.16585.1558540500329%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1332) Add 'pause' function to
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1332 Add 'pause' function to Change By: Alex Dreyer Summary: Add 'pause' function to demo-magic 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.309700.1558539389000.16576.1558540320309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1331) Add 'retry' functionality to script
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1331 Add 'retry' functionality to script Change By: Alex Dreyer Summary: Add 'retry' functionality to demo-magic script 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.309699.1558539258000.16573.1558540260898%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1330) Create a Bolt demo that can be run with little oversight based
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1330 Create a Bolt demo that can be run with little oversight based Change By: Alex Dreyer Summary: Create a Bolt demo that can be run with little oversight based on demo-magic 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.309698.1558539239000.16567.1558540260611%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1270) Bolt should have an encrypted data store
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1270 Bolt should have an encrypted data store Change By: Alex Dreyer Assignee: Nick Maludy Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306226.1556137243000.14943.1558464000382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1327
Expose r10k proxy configuration option
Change By:
Alex Dreyer
r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration as {{ module_proxy 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
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Alex Dreyer
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.{noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)} query_result_or_error = catch(errors) || { }{ noformat}
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
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Alex Dreyer
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.{noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query() }{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Issue Type: New Feature Assignee: Unassigned Created: 2019/05/21 7:38 AM Priority: Normal Reporter: Alex Dreyer r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration as module_proxy? questions: What should the configuration option be called? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Alex Dreyer 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.309321.1558130157000.11504.1558130460183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/05/16 2:22 PM
Priority:
Normal
Reporter:
Alex Dreyer
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling run_plan with _catch_errors => true but sometimes this is less readable. Proposed solution: A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.
$result_or_error = catch_errors([kind1, kind2]) ||{
run_task(task1)
run_task(task2)
run_task(task3)
}
Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1297 Bolt should raise a nice error if the private key file doesn't exist Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.9140.1558029060285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-836) Support Hiera lookup() in plans outside of apply blocks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-836 Support Hiera lookup() in plans outside of apply blocks Change By: Alex Dreyer Summary: Support Hiera lookup() in plans outside of apply blocks 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.275693.1536882656000.8823.1558022280357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1166) Windows compatibility for orchestrator_client-ruby persistent http connections
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1166 Windows compatibility for orchestrator_client-ruby persistent http connections Change By: Alex Dreyer A new feature was introduced with https://github.com/puppetlabs/orchestrator_client-ruby/pull/19 that allowed persistent HTTP connections. The implementation has a dependency on https://github.com/drbrain/net-http-persistent which is an unmaintained project that is currently not compatible with Bolt on windows. This feature was released to Rubygems with an increment in the minor version from (from 0.3.x to 0.4.x) along with the work in https://tickets.puppetlabs.com/browse/BOLT-1076 In order to satisfy BOLT-1076, the persistent http connection was implemented such that it only uses the net-http-persistent gem on non-windows. Look in to windows compatability. The docs for how to configure orchestrator client are inaccurate now too. They should be updated as part of this work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1166) Windows compatibility for orchestrator_client-ruby persistent http connections
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1166 Windows compatibility for orchestrator_client-ruby persistent http connections 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298616.1551895531000.7954.1557955680969%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1222
Support an "apply" step.
Change By:
Alex Dreyer
We should be able to handle simple apply actions in simple plans.* `apply_prep` should be implicitly called on targets at least once in the plan.* It should support a data format of resource declaration. Questions Observations : should we use * must be an array or hash? so we can have manifest ordering * having type and title together on one line is preferable {noformat}---steps: # + This allows us to maintain manifest ordering which may Can there be useful a parameter called "type" . # - need to come up with safe keyword for resource_type - description: "single resource in array"resources: - _type type : classtitle: "foo::bar"param1: foonoop: true - description: "single resource in array" # Allows resources : to be easily scannable. - # Similar to step syntax where the step type : class or resource type is stored by the presence of a key. title: # Won't with with " foo::bar parameters " type if one exists. param1: foonoop: true - resources:- package: nginx- package: ssh- file: /tmp/foo parameters:content: "hello world" - description: "single resource in array"resources: - type: classtitle: "foo::bar"parameters: param1: foo noop: true# Using refs may be confusing when people move to puppet code# Using refs forces users to understand some weird capitalization rules - description: "Use ref's as the key"Package['nginx']:File['/var/...']: content: $foo - description: "Use ref's as the key"- ref: Package['nginx']- ref: File['/var/...']content: $foo# No ordering is unacceptable - description: "single resource in hash by name"resources: foo::bar:_type: classparam1: foobefore: "File['/etc/fop']"noop: true# No ordering is unacceptable - description: "single resource in nested hash"resources: class:foo::bar: param1: class noop: true{noformat}
Add Comment
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1222
Support an "apply" step.
Change By:
Alex Dreyer
We should be able to handle simple apply actions in simple plans.* `apply_prep` should be implicitly called on targets at least once in the plan.* It should support a data format of resource declaration.Questions:should we use an array or hash? {noformat}---steps: # + This allows us to maintain manifest ordering which may be useful # - need to come up with safe keyword for resource_type - description: "single resource in array"resources: - _type: classtitle: "foo::bar"param1: foonoop: true - description: "single resource in array"resources: - type: classtitle: "foo::bar"param1: foonoop: true - resources:- package: nginx- package: ssh- file: /tmp/foo parameters:content: "hello world" - description: "single resource in array"resources: - type: classtitle: "foo::bar"parameters: param1: foo noop: true# Using refs may be confusing when people move to puppet code# Using refs forces users to understand some weird capitalization rules - description: "Use ref's as the key"Package['nginx']:File['/var/...']: content: $foo - description: "Use ref's as the key"- ref: Package['nginx']- ref: File['/var/...']content: $foo# No ordering is unacceptable - description: "single resource in hash by name"resources: foo::bar:_type: classparam1: foobefore: "File['/etc/fop']"noop: true# No ordering is unacceptable - description: "single resource in nested hash"resources: class:foo::bar: param1: class noop: true{noformat}
Add Comment
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Alex Dreyer commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo @nick.walker Does this meet your expectations? 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.6627.1557933480678%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
