Jira (BOLT-267) Add ExecutionResult and Target data types
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet Task Runner / BOLT-267 Add ExecutionResult and Target data types Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-267) Add ExecutionResult and Target data types
Title: Message Title Thomas Hallgren commented on BOLT-267 Re: Add ExecutionResult and Target data types Merged to master at e79c8b0. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8265) Remove ExecutionResult and Target from Puppet core
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8265 Remove ExecutionResult and Target from Puppet core Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8265) Remove ExecutionResult and Target from Puppet core
Title: Message Title Thomas Hallgren commented on PUP-8265 Re: Remove ExecutionResult and Target from Puppet core Merged to master at cc9826d. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-259) Config file should use .yaml extension
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-259 Config file should use .yaml extension Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-259) Config file should use .yaml extension
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-259 Config file should use .yaml extension Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-274 Remove '::init' from task names in `bolt task show *` Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title Michelle Fredette commented on BOLT-119 Re: Implement `--noop` commandline flag and API support for noop tasks added release note. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks Change By: Michelle Fredette Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Michael Smith updated an issue Puppet / PUP-8271 init plans in bolt do not load correctly from 'bolt plan show' Change By: Michael Smith Affects Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title
Alex Dreyer updated an issue
Puppet / PUP-8271
init plans in bolt do not load correctly from 'bolt plan show'
Change By:
Alex Dreyer
*Puppet Version: vendored branch = feature_puppet-tasksDescribe your issue in as much detail as possible…Describe steps to reproduce…*Desired Behavior:**Actual Behavior:Given the following plan{code:title=modules/foo/plans/init.pp}plan foo() { notice 'I am the init plan for the foo module'}{code}And I use 'bolt plan show', I get the following.{code}[root@p0dv972ia1yz1v1 ~]# bolt plan show --modulepath ~/modules (at /usr/local/share/gems/gems/bolt-9.9.afe6bdc/vendored/puppet/lib/puppet.rb:130:in `')Error: The code loaded from /root/modules/foo/plans/init.pp produced plan with the wrong name, expected foo::init, actual foo on node p0dv972ia1yz1v1.delivery.puppetlabs.netFailure while reading plans{code}If I attempt to run this plan it works correctly. {code}[root@p0dv972ia1yz1v1 ~]# bolt plan run foo --modulepath ~/modulesNotice: Scope(/foo/plans/init.pp, 2): I am the init plan{code} There is a second related issue where both list_task and list_plan methods return objects that don't remove the {{init}} part of the task and plan names.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-125) Support WinRM over SSL
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-125 Support WinRM over SSL Change By: Michelle Fredette Labels: docs_reviewd docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michelle Fredette commented on BOLT-157 Re: Show documentation for tasks added release note. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: Michelle Fredette Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1592) Networking key/value pair for Interface Speed and Duplex State
Title: Message Title Pat Riehecky commented on FACT-1592 Re: Networking key/value pair for Interface Speed and Duplex State If possible, I'd prefer the speed be an Integer of Mb per sec rather than 'human units' so I can easily to > or < for other matching. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Michelle Fredette commented on BOLT-155 Re: Show list of available tasks with bolt task show Added to command reference and release notes. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-155 Show list of available tasks with bolt task show Change By: Michelle Fredette Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet / PUP-8271 init plans in bolt do not load correctly from 'bolt plan show' Change By: Alex Dreyer Assignee: Thomas Hallgren Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Alex Dreyer commented on PUP-8271 Re: init plans in bolt do not load correctly from 'bolt plan show' It's related in that the way we handle plan names seems to be off. We can fix this by handing the init name in the plan loader. That prevents the error but at that point the name returned by list plan is still wrong. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/loader/puppet_plan_instantiator.rb#L36 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Michael Smith commented on BOLT-274 Re: Remove '::init' from task names in `bolt task show *` Oh, I thought PUP-8271 found something different. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michelle Fredette commented on BOLT-157 Re: Show documentation for tasks are there 2 commands - bolt task show and bolt task show ? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Alex Dreyer commented on BOLT-274 Re: Remove '::init' from task names in `bolt task show *` It doesn't happen in puppet yet. If you deal with the error when an init plan is present the init plan is named module::init Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Michael Smith commented on BOLT-274 Re: Remove '::init' from task names in `bolt task show *` I think Puppet. Some handling for '::init' happens for plans there already, so seems to make sense it would also handle tasks. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8269) Application management 'plan' not working
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-8269 Application management 'plan' not working Change By: Michael Smith Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title Michael Smith commented on PUP-8271 Re: init plans in bolt do not load correctly from 'bolt plan show' list_plans seems to be behaving surprisingly here. This also seems related to BOLT-274, where we think list_tasks should strip '::init' off the returned task names. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8271) init plans in bolt do not load correctly from 'bolt plan show'
Title: Message Title
Zach Reichert created an issue
Puppet / PUP-8271
init plans in bolt do not load correctly from 'bolt plan show'
Issue Type:
Bug
Assignee:
Thomas Hallgren
Created:
2017/12/20 11:36 AM
Priority:
Normal
Reporter:
Zach Reichert
*Puppet Version: vendored branch = feature_puppet-tasks
Describe your issue in as much detail as possible… Describe steps to reproduce…
Desired Behavior:
*Actual Behavior: Given the following plan
modules/foo/plans/init.pp
plan foo() {
notice 'I am the init plan for the foo module'
Jira (BOLT-125) Support WinRM over SSL
Title: Message Title Michelle Fredette commented on BOLT-125 Re: Support WinRM over SSL Added an improvement note and added the config options to the Config options topic. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-125) Support WinRM over SSL
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-125 Support WinRM over SSL Change By: Michelle Fredette Labels: docs_reviewd Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-273) Support noop from plans
Title: Message Title Michael Smith commented on BOLT-273 Re: Support noop from plans I'd probably want to see some logging around actions that are skipped because they don't support noop. May not be that important because it'll take work to make a plan that can run noop correctly and provide useful feedback though. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-273) Support noop from plans
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-273
Support noop from plans
Change By:
Michael Smith
There are two features related to noop support for plans. They are somewhat dependent on each other so I'm including one ticket for now. . h2 . {{--noop}}User story: I want to run a plan in noop mode so I can see what it will do before I run it normally.Add suppport for the {{--noop}} flag at the bolt command level which would run all tasks in the plan in noop. - All tasks that support --noop in the plan should be run in --noop mode.- File uploads, run_command, and run_script should be skipped returning an execution result with empty values.- Tasks that do not support {{--noop}} would be skipped returning an execution result with empty values. . h2 . {{noop_run_task}}User Story: I want to run a task in noop mode from my plan to verify it will run successfully on all nodes before I run it normallyAdd support to the {{run_task}} function to allow specific tasks in a plan to be run in noop mode. There is some concern this would run into the complexity of resource level noop in puppet catalogs but as long as we don't support {{no-noop}} in bolt thats probably not the case.- A task should be run in noop mode if either the plan or the bolt execution requests {{--noop}}- A task should fail if it's called from a plan with {{noop}} and doesn't {{support_noop}}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe
Jira (BOLT-276) Improve the Bolt onboarding experience
Title: Message Title Yasmin Rajabi commented on BOLT-276 Re: Improve the Bolt onboarding experience cc Jenny Mahmoudi Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-276) Improve the Bolt onboarding experience
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-276 Improve the Bolt onboarding experience Issue Type: Story Assignee: Unassigned Created: 2017/12/20 11:01 AM Priority: Normal Reporter: Yasmin Rajabi As a new user getting started with Bolt the documentation and available resources are not enough to get started seamlessly. Things to consider: getting started docs hands on lab pdk self guided training example tasks/plans Things out of scope: technical improvements
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Alex Dreyer
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node (as json result) INFO:- log whenever when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- - log every sub-action taken on a node like changing a task file permissions - log connection information (This is controlled by net:ssh not us) INFO:- Log when bolt starts run execution with object type and first argument(command, script, task or file){{ code}} Starting bolt command run `echo 'hello world'` Starting bolt task run package{{code }}- Log when actions start on nodes- Log the results of from each action on each a node (as json representation) NOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is{{ Running task package }}- log when a run_* call finishes and summarize how many nodes succeeded or failed{{ Ran task package on 34 nodes with 3 failures }} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Alex Dreyer
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node INFO:- log when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log every sub-action taken on a node like changing a task file permissions- log connection informationINFO:- Log when bolt starts run execution with object type and first argument(command, script, task or file){{code}}Starting bolt command run `echo 'hello world'`Starting bolt task run package {{code}}- Log when actions start on nodes- Log results from each action on a node (as json representation)NOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is{{ Running task package }}- log when a run_* call finishes and summarize how many nodes succeeded or failed{{ Ran task package on 34 nodes with 3 failures }} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Alex Dreyer
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node (as json result)INFO:- log whenever an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- - log subactions every sub-action taken on a node like changing a task file permissions - log connection information(This is controlled by net:ssh not us)INFO:- Log when bolt starts run execution with object type and first argument(command, script, task or file){{ Starting bolt command run `echo 'hello world'` }}- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is{{ Running task package }}- log when a run_* call finishes and summarize how many nodes succeeded or failed{{ Ran task package on 34 nodes with 3 failures }} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Alex Dreyer
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node (as json result) INFO:- log whenever an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when bolt starts run execution with object type and first argument(command, script, task or file){{ Starting bolt command run `echo 'hello world'` }}- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is{{ Running task package }}- log when a run_* call finishes and summarize how many nodes succeeded or failed{{ Ran task package on 34 nodes with 3 failures }} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Jenny Mahmoudi commented on BOLT-266 Re: Log run_* actions when called from a plan Alex Dreyer The proposed new notice level makes sense to me. I'm confused about how the info and debug levels are changing, though. 1. It looks like "log when actions are started on nodes" is duplicated in both info and debug - is that intentional? 2. I can't tell for sure what's the same between the current state and proposed changes because some items sound similar but are written with different language. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title
Michael Smith created an issue
Puppet / PUP-8270
PAL task_signature adds 'default' to some type descriptions
Issue Type:
Bug
Affects Versions:
PUP 5.4.0
Assignee:
Unassigned
Created:
2017/12/20 10:46 AM
Priority:
Normal
Reporter:
Michael Smith
Using bolt task show on the following metadata file results in some strange artifacts
{
"description": "Do a thing.",
"parameters": {
Jira (PUP-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Michael Smith assigned an issue to Thomas Hallgren Puppet / PUP-8270 PAL task_signature adds 'default' to some type descriptions Change By: Michael Smith Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michael Smith commented on BOLT-157 Re: Show documentation for tasks I reproduced the task_hash error: it happens when the task isn't found. Worth detecting task.nil? and producing a better error message. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Lucy Wyman commented on BOLT-157 Re: Show documentation for tasks Yeah, I get that as well. I'm not sure what changed (probably we aren't getting 'parameters' back in the Task signature), but https://github.com/puppetlabs/bolt/pull/208/files should fix that Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-272) Docs updates for 0.12.0
Title: Message Title Michael Smith commented on BOLT-272 Re: Docs updates for 0.12.0 It might be a nice addition to highlight that bolt task show will show whether a task supports noop. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michael Smith commented on BOLT-157 Re: Show documentation for tasks Hmm, I can't reproduce it anymore now either. I get bundler: failed to load command: bolt (/Users/michaelsmith/puppetlabs/bolt/.bundle/gems/ruby/2.3.0/bin/bolt) NoMethodError: undefined method `each' for nil:NilClass /Users/michaelsmith/puppetlabs/bolt/lib/bolt/outputter/human.rb:103:in `print_task_info' /Users/michaelsmith/puppetlabs/bolt/lib/bolt/cli.rb:407:in `execute' /Users/michaelsmith/puppetlabs/bolt/exe/bolt:9:in `' /Users/michaelsmith/puppetlabs/bolt/.bundle/gems/ruby/2.3.0/bin/bolt:22:in `load' /Users/michaelsmith/puppetlabs/bolt/.bundle/gems/ruby/2.3.0/bin/bolt:22:in `' which is what I was seeing with minifact.
Jira (BOLT-272) Docs updates for 0.12.0
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-272
Docs updates for 0.12.0
Change By:
Alex Dreyer
A couple of docs pages need to be updated for 0.12.0The (configuring bolt page)[https://puppet.com/docs/bolt/0.x/configuring_bolt.html] needs updates for the new transport configuration options we've added{code}SSH:connect-timeout: How long should bolt wait when establishing connectionstmpdir: The directory to upload and execute temporary files on the targetWINRM:connect-timeout: How long should bolt wait when establishing connections.insecure: When true bolt will use normal http connections for winrm(default: false)tmpdir: The directory to upload and execute temporary files on the target.cacert: The path to the CA certificatePCP:service-url: The url of the orchestrator APIcacert: The path to the CA certificatetoken-file: The path to the token filetask-environment: The environment orchestrator should load task code from{code}The (Running tasks and plans page)[https://puppet.com/docs/bolt/0.x/running_tasks_and_plans_with_bolt.html]New Content:{code}NoopSome tasks may support running in noop mode which allows you to run themwithout making any changes to the target node. To run a task in `noop` modewith bolt use the `--noop` flag. If a task doesn't support running in noop modebolt will error.``bashbolt task run package name=vim action="" />```Discovering tasks with the show actionBolt will can display a list of what tasks are installed in the current module path with the show action.```bashbolt task show```To see documentation for a specifc task pass the task name as an argument to show```bashbolt task show package```Discovering plans with the show actionBolt can display a list of what plans are installed on the current module apthwith the show action. There is no equivalent to `bolt task show ` todisplay documentation for a plan yet.```bashbolt plan show```{code}replace the phrase "unstructured JSON" with simple JSON.New first paragraph in the parameters section : should include information about why a user would use CLI args vs a JSON hash {code} Parameters for tasks can passed to the bolt command as CLI arguments or as a JSON hash. Parameters passed as CLI arguments will always be parsed as strings for other typed you must pass parameters as a JSON hash. {code}
Add Comment
Jira (BOLT-272) Docs updates for 0.12.0
Title: Message Title Alex Dreyer assigned an issue to Michelle Fredette Puppet Task Runner / BOLT-272 Docs updates for 0.12.0 Change By: Alex Dreyer Assignee: Michelle Fredette Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-272) Docs updates for 0.12.0
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-272
Docs updates for 0.12.0
Change By:
Alex Dreyer
A couple of docs pages need to be updated for 0.12.0The (configuring bolt page)[https://puppet.com/docs/bolt/0.x/configuring_bolt.html] needs updates for the new transport configuration options we've added{code}SSH:connect-timeout: How long should bolt wait when establishing connectionstmpdir: The directory to upload and execute temporary files on the targetWINRM:connect-timeout: How long should bolt wait when establishing connections.insecure: When true bolt will use normal http connections for winrm(default: false)tmpdir: The directory to upload and execute temporary files on the target.cacert: The path to the CA certificatePCP:service-url: The url of the orchestrator APIcacert: The path to the CA certificatetoken-file: The path to the token filetask-environment: The environment orchestrator should load task code from{code}The (Running tasks and plans page)[https://puppet.com/docs/bolt/0.x/running_tasks_and_plans_with_bolt.html]New Content:{code}NoopSome tasks may support running in noop mode which allows you to run themwithout making any changes to the target node. To run a task in `noop` modewith bolt use the `--noop` flag. If a task doesn't support running in noop modebolt will error.``bashbolt task run package name=vim action="" />```Discovering tasks with the show actionBolt will can display a list of what tasks are installed in the current module path with the show action.```bashbolt task show```To see documentation for a specifc task pass the task name as an argument to show```bashbolt task show package```Discovering plans with the show actionBolt can display a list of what plans are installed on the current module apthwith the show action. There is no equivalent to `bolt task show ` todisplay documentation for a plan yet.```bashbolt plan show```{code} - remove replace the phrase " Unstructured unstructured JSON" with simple JSON. - Update New first paragraph in the parameters section :Parameters for tasks can passed to make it clear that the bolt command as CLI arguments or as a JSON hash. Parameters passed as CLI arguments will always be parsed as strings for other typed you must pass parameters need to use --params as a JSON hash.
Add Comment
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Lucy Wyman commented on BOLT-157 Re: Show documentation for tasks Misaligned "Use `bolt`" line Newline between parameters without descriptions Default attribute type (Not sure where this is coming from either? How high of a priority is it to fix?) Tasks without metadata error Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-272) Docs updates for 0.12.0
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-272
Docs updates for 0.12.0
Change By:
Alex Dreyer
A couple of docs pages need to be updated for 0.12.0The (configuring bolt page)[https://puppet.com/docs/bolt/0.x/configuring_bolt.html] needs updates for the new transport configuration options we've added{code}SSH:connect-timeout: How long should bolt wait when establishing connectionstmpdir: The directory to upload and execute temporary files on the targetWINRM:connect-timeout: How long should bolt wait when establishing connections.insecure: When true bolt will use normal http connections for winrm(default: false)tmpdir: The directory to upload and execute temporary files on the target.cacert: The path to the CA certificatePCP:service-url: The url of the orchestrator APIcacert: The path to the CA certificatetoken-file: The path to the token filetask-environment: The environment orchestrator should load task code from{code}The (Running tasks and plans page)[https://puppet.com/docs/bolt/0.x/running_tasks_and_plans_with_bolt.html] - running New Content:{code}NoopSome tasks may support running in noop mode which allows you to run themwithout making any changes to the target node. To run a task in `noop` mode with bolt use the `-- noop ` flag. If a task doesn't support running in noop mode bolt will error.``bashbolt task run package name=vim action=""> - showing -noop -n example.com ```Discovering tasks with the show actionBolt will can display a list of what tasks are available installed in the current module path with the show action. - showing docs ```bashbolt task show```To see documentation for a specific specifc task pass the task name as an argument to show - showing ```bashbolt task show package```Discovering plans with the show actionBolt can display a list of what plans are available installed on the current module apthwith the show action . There is no equivalent to `bolt task show ` to display documentation for a plan yet.```bashbolt plan show```{code} - remove "Unstructured JSON"- Update parameters section to make it clear that typed parameters need to use --params
Add Comment
Jira (PUP-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-5206 Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Change By: Jorie Tappa Release Notes Summary: Previously, using the --local option in filebucket would default to using the server's filebucket instead of the actual local filebucket, which would cause errors when querying for files on the local filebucket because they could not be found. (As filebucket was looking in the wrong directory) The behavior has been changed for --local option to now use the clientbucketdir instead of bucketdir. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Melissa Stone Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Sprint: Bolt Irving One Point Oh Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Sprint: Bolt One Point Oh Irving Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-57) Download a file
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-57 Download a file Change By: Alex Dreyer Sprint: Bolt One Point Oh Irving Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-233) Bolt writes parameters to disk, undesirable for sensitive inputs
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-233 Bolt writes parameters to disk, undesirable for sensitive inputs Change By: Alex Dreyer Sprint: Bolt Adoption Blockers Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Alex Dreyer
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when bolt starts run execution with object type and first argument(command, script, task or file) {{ Starting bolt command run `echo 'hello world'` }} - Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is {{ Running task package }} - log when a run_* call finishes and summarize how many nodes succeeded or failed {{ Ran task package on 34 nodes with 3 failures }} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: Alex Dreyer Release Notes Summary: This adds a `bolt task show ` command that will display documentation for using an installed task. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Alex Dreyer commented on BOLT-274 Re: Remove '::init' from task names in `bolt task show *` Should this be fixed in puppet or bolt Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-274 Remove '::init' from task names in `bolt task show *` Change By: Alex Dreyer Sprint: Bolt One Point Oh Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-32) Add ability to enumerate available plans
Title: Message Title Zach Reichert assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-32 Add ability to enumerate available plans Change By: Zach Reichert Assignee: Zach Reichert Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8249
Certain environments return "invalid byte sequence in " when parsing module PO files
Change By:
Eric Delaney
If you load the eputnam-i18ndemo module which has a fact that causes and error that has a Japanese translation, when its run on OSX the error is replaced by "invalid byte sequence in US-ASCII"{code}xh734nh8owpuouo:~ root# puppet module install eputnam-i18ndemoNotice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppet.com ...Notice: Installing -- do not interrupt .../etc/puppetlabs/code/environments/production/modules└─┬ eputnam-i18ndemo (v0.2.0) ├── puppetlabs-stdlib (v4.21.0) └── puppetlabs-translate (v1.1.0)xh734nh8owpuouo:~ root# LANGUAGE=ja_JP puppet factsError: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in US-ASCII{code}Instead of the expected Japanese string (which should look like this pattern){code}assert_match(/Error:.*eputnam-i18ndemo fact: これはeputnam-i18ndemoからのカスタムファクトからのレイズです/, result.stderr, 'missing translation for raise from ruby fact'){code} This also appears, for example, on the Japanese Windows pooler image. If you install the module, then attempt to uninstall it, the uninstall will fail with a similar error, and a trace like the one in the comments.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this
Jira (BOLT-262) When orchestrator skips a task it does not produce a useful error in bolt
Title: Message Title
Michael Smith commented on BOLT-262
Re: When orchestrator skips a task it does not produce a useful error in bolt
Forced a task run to skip all nodes in Orchestrator, and ran:
$ bolt task run echo message=hello -n pcp://foo
Started on foo...
Failed on foo:
Node foo was skipped
{
}
Ran on 1 node in 2.53 seconds
Add Comment
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Matt Dainty commented on PUP-7744 Re: Puppet CA's CRL is prone to duplicate entries Yes, just run into this via SERVER-115 and " doesn't always revoke what you expect" class="issue-link" data-issue-key="PUP-2569" style="color: #3b73af; text-decoration: none"> PUP-2569 and associates. I now have a 8.5 MB CRL that contains ~ 180,000 individual revocations and as many as ~ 500 duplicate revocations for specific certificate serial numbers. I've used puppet cert reinventory to clean down inventory.txt so most of the old certificate serials are forgotten. Is it possible to rebuild the CRL and de-dupe it to just contain one of each serial number as I'm continually hitting the problem documented in SERVER-115 whereby any time I perform a puppet node clean it triggers a CRL rebuild that causes issues for any other connecting client(s), the size of the CRL can't not be contributing to this so the smaller I can make it the better. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-155 Show list of available tasks with bolt task show Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Maggie Dreyer commented on PUP-8249 Re: Certain environments return "invalid byte sequence in " when parsing module PO files So it looks like this boils down to: Loading puppet's translations works in the agent package because we are loading MO files, not PO files. Loading puppet's PO file directly fails too in these environments. A fix to this by David Schmitt seems to have been landed in fast_gettext at https://github.com/grosser/fast_gettext/commit/8b65ff3da69f031e5647f3d58b4d5b9cbd6b229d#diff-557c5de4875541de442e989bf7eda454, bt we can't use any version past 1.1.0 in Puppet, due to the need for Ruby 1.9.3 compatibility. So we have a few options: 1) Document environmental workarounds for each OS (still uncertain if there is one on Windows), and wait to see if users have issues with those constraints. 2) Fork/branch fast_gettext and apply that patch to a version we can use. 3) Ship MO binary files for modules like we do for Puppet. (Note: most other gettext libraries require this format, possibly for this reason, they're super portable.) I'm not familiar enough with module packaging/release to know if this is feasible /cc Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8244) Enable Lint/UselessAssignment rubocop check
Title: Message Title Jacob Helwig commented on PUP-8244 Re: Enable Lint/UselessAssignment rubocop check Merged to master in 2b7b4ed6 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Michael Smith commented on BOLT-155 Re: Show list of available tasks with bolt task show Good question, it seems reasonable to drop the ::init. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-274 Remove '::init' from task names in `bolt task show *` Change By: Michael Smith Affects Version/s: BOLT 0.11.0 Affects Version/s: BOLT 0.12.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8269) Application management 'plan' not working
Title: Message Title Michael Smith assigned an issue to Thomas Hallgren Puppet / PUP-8269 Application management 'plan' not working Change By: Michael Smith Assignee: Michael Smith Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-275) Bolt plan example contains error
Title: Message Title Zach Reichert created an issue Puppet Task Runner / BOLT-275 Bolt plan example contains error Issue Type: Bug Assignee: Unassigned Created: 2017/12/20 8:57 AM Priority: Normal Reporter: Zach Reichert In the documentation https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters The example will not compile, the variant declarations need closing brackets. It should be plan mymodule::my_plan( String[1]$load_balancer, Variant[String[1], Array[String[1]]] $frontends, Variant[String[1], Array[String[1]]] $backends,
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michael Smith commented on BOLT-157 Re: Show documentation for tasks Formatting is weird on 'bolt task show' now: ... Use `bolt task show ` to view details and parameters for a specific task. Also, we should have a newline before that is printed. I'm pulling examples from the orchestration-control repo. I'm also getting no newline between parameters without descriptions: PARAMETERS: - maybe_enum: Optional[Enum['maybe', 'no', 'yes']]- variant_enum: Variant[Enum['maybe', 'no', 'yes'], Boolean] Printing puppet::config seems to add a default attribute to some types, not sure where it comes from puppet::config -
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Lucy Wyman commented on BOLT-155 Re: Show list of available tasks with bolt task show Sweet, created BOLT-274 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1592) Networking key/value pair for Interface Speed and Duplex State
Title: Message Title Jonathan Gazeley commented on FACT-1592 Re: Networking key/value pair for Interface Speed and Duplex State This is something I would definitely benefit from. Our use case is that Nagios monitoring of network link utilisation requires it to know the nominal speed of the link. So far, all our systems have been 1Gbit so we've just hard-coded the value but now we have started using systems with 10Gbit interfaces so we could do with handling this value programmatically. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-32) Add ability to enumerate available plans
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-32 Add ability to enumerate available plans Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7685) puppet resource user may show double groups
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-7685 puppet resource user may show double groups Change By: Jacob Helwig Labels: community Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8269) Application management 'plan' not working
Title: Message Title Thomas Hallgren commented on PUP-8269 Re: Application management 'plan' not working Thanks Michael Smith. I turned your example into a unit test in the updated PR. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: Michael Smith Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-262) When orchestrator skips a task it does not produce a useful error in bolt
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-262 When orchestrator skips a task it does not produce a useful error in bolt Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-32) Add ability to enumerate available plans
Title: Message Title
Zach Reichert commented on BOLT-32
Re: Add ability to enumerate available plans
It looks like the docs reference the ability to make an init plan. If I have a plan like this
plan foo() {
notice 'I am the init plan for the foo module'
}
And I use 'bolt plan show', I get the following.
[root@p0dv972ia1yz1v1 ~]# bolt plan show --modulepath ~/modules
Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions.
(at /usr/local/share/gems/gems/bolt-9.9.afe6bdc/vendored/puppet/lib/puppet.rb:130:in `')
Error: The code loaded from /root/modules/foo/plans/init.pp produced plan with the wrong name, expected foo::init, actual foo on node p0dv972ia1yz1v1.delivery.puppetlabs.net
Failure while reading plans
Jira (PDB-3800) Fix errors in example
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3800 Fix errors in example Issue Type: Bug Assignee: Unassigned Created: 2017/12/20 8:49 AM Priority: Normal Reporter: gepetto-bot .each doesn't change the result to store in the variable. It keeps any changes/output isolated. Need .map to use the result outside of the iterator per the example. Also, no capital on notify. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8249
Certain environments return "invalid byte sequence in " when parsing module PO files
Change By:
Eric Delaney
If you load the eputnam-i18ndemo module which has a fact that causes and error that has a Japanese translation, when its run on OSX the error is replaced by "invalid byte sequence in US-ASCII"{code}xh734nh8owpuouo:~ root# puppet module install eputnam-i18ndemoNotice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppet.com ...Notice: Installing -- do not interrupt .../etc/puppetlabs/code/environments/production/modules└─┬ eputnam-i18ndemo (v0.2.0) ├── puppetlabs-stdlib (v4.21.0) └── puppetlabs-translate (v1.1.0)xh734nh8owpuouo:~ root# LANGUAGE=ja_JP puppet factsError: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in US-ASCII{code}Instead of the expected Japanese string (which should look like this pattern){code}assert_match(/Error:.*eputnam-i18ndemo fact: これはeputnam-i18ndemoからのカスタムファクトからのレイズです/, result.stderr, 'missing translation for raise from ruby fact'){code} This also appears, for example, on the Japanese Windows pooler image. If you install the module, then attempt to uninstall it, the uninstall will fail with a similar error, and a trace like the one in the comments.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this
Jira (PUP-8269) Application management 'plan' not working
Title: Message Title
Michael Smith commented on PUP-8269
Re: Application management 'plan' not working
Running puppet apply with
define plan::node_file() {
file { "/tmp/plan.FkBm7A/${name}.txt":
content => "this is ${name}.txt",
}
}
Plan::Node_file produces Node_file {}
application plan() {
plan::node_file { "node_file_${name}":
export => Node_file["node_file_${name}"]
}
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-262) When orchestrator skips a task it does not produce a useful error in bolt
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-262 When orchestrator skips a task it does not produce a useful error in bolt Change By: Michelle Fredette Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7685) puppet resource user may show double groups
Title: Message Title Jacob Helwig commented on PUP-7685 Re: puppet resource user may show double groups Merged to master in 21fda7d39. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-273) Support --noop from plans
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-273 Support --noop from plans Issue Type: Bug Assignee: Unassigned Created: 2017/12/19 4:22 PM Priority: Normal Reporter: Alex Dreyer There are two features related to noop support for plans. They are somewhat dependent on each other so I'm including one ticket for now. .h2 --noop User story: I want to run a plan in noop mode so I can see what it will do before I run it normally. Add suppport for the --noop flag at the bolt command level which would run all tasks in the plan in noop. All tasks that support --noop in the plan should be run in --noop mode. File uploads, run_command, and run_script should be skipped returning an execution result with empty values. Tasks that do not support --noop would be skipped returning an execution result with empty values. .h2 noop_run_task User Story: I want to run a task in noop mode from my plan to verify it will run successfully on all nodes before I run it normally Add support to the run_task function to allow specific tasks in a plan to be run in noop mode. There is some concern this would run into the complexity of resource level noop in puppet catalogs but as long as we
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: Alex Dreyer Fix Version/s: BOLT 0.12.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-157) Show documentation for tasks
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7685) puppet resource user may show double groups
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-7685 puppet resource user may show double groups Change By: Jacob Helwig Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-273) Support noop from plans
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-273 Support noop from plans Change By: Alex Dreyer Summary: Support -- noop from plans Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Lucy Wyman commented on BOLT-155 Re: Show list of available tasks with bolt task show It looks like `task::init` isn't getting resolved to just `task`: apache::init Allows you to perform apache service functions echo::init exec::init Executes a command on the system facter::init Is that expected? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Sprint: Bolt Irving One Point Oh Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Eric Delaney commented on PUP-8249 Re: Certain environments return "invalid byte sequence in " when parsing module PO files The underlying issue is around how the user's shell environment is set when calling puppet (ruby). The critical pieces are the following: fastgettext looks at LANGUAGE first Ruby looks at LANG to determine the Encoding.default_external So when Ruby gets started you need the following to be successful when setting the language: to have LANGUAGE set (or completely unset) to have LANG set to a language with UTF-8 encoding If LANG doesn't support a UTF-8 encoding then loading the translations files will fail. For example here it succeeds because its UTF-8: gb3gzj87bccsk9d:bin root# LANG=ja_JP.UTF-8 LANGUAGE=ja_JP.UTF-8 puppet facts >/dev/null Error: Facter: error while resolving custom fact "i18ndemo_fact": eputnam-i18ndemo fact: これはeputnam-i18ndemoからのカスタムファクトからのレイズです While all of these fail because we can't open the translation po files successfully: gb3gzj87bccsk9d:bin root# LANG=ja_JP.eucJP LANGUAGE=ja_JP.eucJP puppet facts >/dev/null Error: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in EUC-JP
Jira (BOLT-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-264) Allow run-as configuration option for ssh transport
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-264 Allow run-as configuration option for ssh transport Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-274) Remove '::init' from task names in `bolt task show *`
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-274 Remove '::init' from task names in `bolt task show *` Issue Type: Bug Affects Versions: BOLT 0.11.0 Assignee: Unassigned Created: 2017/12/20 7:07 AM Priority: Minor Reporter: Lucy Wyman $ bolt task show apache::init Allows you to perform apache service functions echo::init exec::init Executes a command on
