Jira (BOLT-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools 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 (PUP-8269) Application management 'plan' not working
Title: Message Title Michael Smith updated an issue Puppet / PUP-8269 Application management 'plan' not working 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-8269) Application management 'plan' not working
Title: Message Title Michael Smith updated an issue Puppet / PUP-8269 Application management 'plan' not working Change By: Michael Smith Release Notes Summary: Fixed before release. Release Notes: Not Needed 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 assigned an issue to Jacob Helwig Puppet / PUP-7685 puppet resource user may show double groups Change By: Jacob Helwig Assignee: Jacob Helwig 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 updated an issue Puppet / PUP-8269 Application management 'plan' not working Change By: Michael Smith Fix 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 (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 tasks with noop- showing what tasks are available- showing docs for a specific task- showing what plans are available.- remove "Unstructured JSON"- Update parameters section to make it clear that typed parameters need to use --params
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
Jira (BOLT-32) Add ability to enumerate available plans
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-32
Add ability to enumerate available plans
Change By:
Alex Dreyer
Release Notes Summary:
This adds a {{bolt plan show}} command that will list the available plans in the current modulepath
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-32) Add ability to enumerate available plans
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-32 Add ability to enumerate available plans 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-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop 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-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 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 tasks with noop- showing what tasks are available- showing docs for a specific task- showing what plans are available. - remove "Unstructured JSON"- Update parameters section to make it clear that typed parameters need to use --params
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
Jira (BOLT-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-119
Implement `--noop` commandline flag and API support for noop tasks
Change By:
Michael Smith
Release Notes Summary:
Bolt now accepts a --noop CLI option that can be used with 'task run'. When passed - and if the task metadata specifies {"supports_noop":true} - Bolt will pass a _noop=true parameter to the task (and/or set a PT__noop environment variable depending on input_method) to request that the task runs in noop mode.
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-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 Sprint: Bolt 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-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 Sub-team: Bolt Team: Direct Change 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 needs updates for the new pcp and winrm 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 tasks with noop- showing what tasks are available- showing docs for a specific task- showing what plans are available.
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-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 Component/s: DOCS 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 Michael Smith commented on BOLT-125 Re: Support WinRM over SSL Michelle Fredette I've added release notes to this for the Bolt 0.12.0 release. 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-271) Update Hands on Lab to use metadata features
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-271
Update Hands on Lab to use metadata features
Change By:
Alex Dreyer
Now that we've added more metadata support into bolt we should update the (hands on lab)[https://github.com/puppetlabs/tasks-hands-on-lab] to take advantage of it.h2 . Lesson 6downloading tasks should be updated to include a {{bolt task show}} and a step after the repo is checked out and after r10k is run. Before the package task is run there should be a {{bolt task show package}} to display the parameters so entering them is less magical.A step should be added at the end to list the installed plans and run the canary::random planh2 . New Lesson 8A new lesson should be added between Writing plans and Writing advanced plans "Writing tasks with metadata". - writing a task with parameter descriptions and showing how that powers {{task show}}- writing a task with parameter types and showing how that powers parameter validation- writing and running a task that {{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-125) Support WinRM over SSL
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-125 Support WinRM over SSL Change By: Michael Smith Release Notes Summary: Bolt now supports WinRM over SSL, and defaults to that mode. It accepts the --insecure option to skip SSL.As part of that support, new configuration options are provided for the WinRM transport via the Bolt config file: insecure: skip SSL cacert: path to a CA certificate for SSL authentication 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-272) Docs updates for 0.12.0
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-272 Docs updates for 0.12.0 Issue Type: Task Assignee: Unassigned Created: 2017/12/19 2:25 PM Priority: Normal Reporter: Alex Dreyer A couple of docs pages need to be updated for 0.12.0 The configuring bolt page needs updates for the new pcp and winrm configuration options. The (Running tasks and plans page)https://puppet.com/docs/bolt/0.x/running_tasks_and_plans_with_bolt.html running tasks with noop showing what tasks are available showing docs for a specific task showing what plans are available. Add Comment
Jira (BOLT-258) Configuration options for the PCP transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-258 Configuration options for the PCP transport Change By: Michael Smith Release Notes Summary: The connections settings for orchestrator can now be specified in the bolt config file instead of being read from client-tools/orchestrator.conf. The bolt config can also specify which environment tasks should be loaded from in orchestrator. New configuration options for the PCP transport are available via Bolt's config file: service-url: The url of the orchestrator API cacert: The path to the CA certificate token-file: The path to the token file task-environment: The environment orchestrator should load task code from 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-258) Configuration options for the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-258
Configuration options for the PCP transport
Change By:
Michael Smith
The orchestrator pcp transport should be configurable from the bolt configuration file.example{code}pcp: service-url: ca-cert cacert : token-file: task-environment:{code}service-url, cacert and token-file should be passed to the OrchestratorClient when it's created. If they are nil or not present they should not passed so defaults in the client library can be used.environment should be passed added to the task command body.User story for environmentWhen a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks. Users should be able to configure what environment is sent to orchestrator as part of the task command with the {{task-environment}} configuration option in the pcp section of bolt.yml
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 assigned an issue to Michael Smith Puppet / PUP-8269 Application management 'plan' not working Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Change By: Michael Smith Release Notes Summary: Release notes for BOLT-125 and BOLT-270 will be corrected. Release Notes: Not Needed 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-271) Update Hands on Lab to use metadata features
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-271 Update Hands on Lab to use metadata features Change By: Alex Dreyer Sub-team: bolt Team: Direct Change Sprint: Bolt 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-271) Update Hands on Lab to use metadata features
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-271 Update Hands on Lab to use metadata features Issue Type: Task Assignee: Unassigned Created: 2017/12/19 2:21 PM Priority: Normal Reporter: Alex Dreyer Now that we've added more metadata support into bolt we should update the (hands on lab)https://github.com/puppetlabs/tasks-hands-on-lab to take advantage of it. h2 Lesson 6 downloading tasks should be updated to include a bolt task show and a step after the repo is checked out and after r10k is run. Before the package task is run there should be a bolt task show package to display the parameters so entering them is less magical. A step should be added at the end to list the installed plans and run the canary::random plan h2 New Lesson 8 A new lesson should be added between Writing plans and Writing advanced plans "Writing tasks with metadata". writing a task with parameter descriptions and showing how that powers task show writing a task with parameter types and showing how that powers parameter validation writing and running a task that supports_noop
Jira (BOLT-125) Support WinRM over SSL
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-125 Support WinRM over SSL Change By: Michael Smith Component/s: DOCS 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools 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-258) Configuration options for the PCP transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-258 Configuration options for the PCP transport Change By: Michael Smith Component/s: DOCS 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Change By: Michael Smith Sprint: Bolt 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-270
Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Change By:
Michael Smith
{{puppet-job,app,task,db,code}} all use {{cacert}}. For consistency with that and other common tools (curl) we should change the option from {{ca-cert}} to {{cacert}} .{{ca-cert}} is was added for the winrm transport in Bolt 0.11.0. This will be a breaking change to change it to {{cacert}}. BOLT-258 also added {{ca-cert}} for the PCP and WinRM transport , which should also be changed to {{cacert}} configs .
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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Change By: Michael Smith Component/s: DOCS 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Change By: Michael Smith Labels: docs 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Change By: Michael Smith Labels: docs 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-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-270 Bolt should use cacert (not ca-cert) for consistency with other Puppet tools Issue Type: Bug Affects Versions: BOLT 0.11.0 Assignee: Unassigned Created: 2017/12/19 2:12 PM Fix Versions: BOLT 0.12.0 Priority: Normal Reporter: Michael Smith puppet-job,app,task,db,code all use cacert. For consistency with that and other common tools (curl) we should change the option from ca-cert to cacert. ca-cert is was added for the winrm transport in Bolt 0.11.0. This will be a breaking change to change it to cacert. BOLT-258 also added ca-cert for the PCP transport, which should also be changed to cacert. Add Comment
Jira (PUP-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Larissa Lane commented on PUP-8122 Re: I18n strings that include repeated lists of sentence fragments can be hard to translate Great, thanks Eric Delaney 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-258) Configuration options for the PCP transport
Title: Message Title Michael Smith commented on BOLT-258 Re: Configuration options for the PCP transport I made a change to Alex's docs comment: the final code uses ca-cert (not cacert). 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-8226) Warning in manifest causing invalid byte sequence error on Redhat 7 server
Title: Message Title
Maggie Dreyer commented on PUP-8226
Re: Warning in manifest causing invalid byte sequence error on Redhat 7 server
TL;DR: This seems like a weird edge case that is easily avoidable, but at the moment, there doesn't seem to be a comprehensive solution short of placing the "magic comment" on all our files (though I'd like a second opinion from Past Haus after the holidays).
I've confirmed what I mentioned in my previous comment, that # interpolation correctly handles UTF-8 characters being placed inside an ASCII string, while format string % interpolation does not. We use format string interpolation in strings that are marked for translations with {}, because # interpolation will occur _before the string is sent through the translation tooling, and the English string key will no longer match what is in the translation file. However, it is more verbose, so we try not to use it anywhere else, preferring #. That is why we don't see these kinds of errors in general: in most places where a translation is being placed inside an ASCII untranslated string, we are using #. The bug in this ticket occurred because we intend the string in question to be translated and therefore used % interpolation, but no translation exists yet, so the string was left as ASCII and exploded upon interpolation.
I tried to use setKCode in our JRuby set up, but while it compiled and ran, the setting did not appear to do anything, and did not fix this issue. JRuby appears to only partially respect the setting even under the best circumstances (it has been implemented mostly based on specific users' complaints, for their specific use cases). I also investigated the JVM file.encoding setting, with no success. The most reliable way to completely remove the issue definitely seems to be the "magic comment" approach, with the caveat that user code may still cause problems if combined with the weird interpolation scenario outlined above.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to
Jira (BOLT-269) winrm tests are causing a ruby segfault
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-269
winrm tests are causing a ruby segfault
Change By:
Alex Dreyer
Occurrences:This has happened in the ruby 2.0.0 tests on C:/projects/bolt/spec/bolt/node/winrm_spec.rb:336 https://ci.appveyor.com/project/puppetlabs/bolt/build/0.1.0.928-master/job/52t58tfkllmjs7bi This has happened in the ruby 2.0.0 tests on C:/projects/bolt/spec/bolt/node/winrm_spec.rb:118 https://ci.appveyor.com/project/puppetlabs/bolt/build/0.1.0.907-master/job/e19eye397rosh7r1 example backtrace {code}...C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/power_shell.rb:174: [BUG] Segmentation faultruby 2.0.0p648 (2015-12-16) [i386-mingw32]-- Control frame information ---c:0060 p: s:0282 e:000281 CFUNC :inspectc:0059 p:0013 s:0279 e:000276 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/power_shell.rb:174c:0058 p:0040 s:0273 e:000272 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/psrp/receive_response_reader.rb:45c:0057 p:0010 s:0269 e:000268 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/wsmv/receive_response_reader.rb:66c:0056 p:0049 s:0266 e:000265 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/wsmv/receive_response_reader.rb:121 [FINISH]c:0055 p: s:0263 e:000262 CFUNC :eachc:0054 p:0033 s:0260 e:000259 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/wsmv/receive_response_reader.rb:119c:0053 p:0057 s:0256 e:000255 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/wsmv/receive_response_reader.rb:65c:0052 p:0034 s:0250 e:000249 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/psrp/receive_response_reader.rb:41c:0051 p:0060 s:0243 e:000242 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/power_shell.rb:173c:0050 p:0090 s:0237 e:000236 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/power_shell.rb:126c:0049 p:0027 s:0231 e:000230 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/base.rb:168c:0048 p:0006 s:0229 e:000228 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/retryable.rb:37c:0047 p:0027 s:0224 e:000223 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/base.rb:166c:0046 p:0034 s:0221 e:000220 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/base.rb:129c:0045 p:0015 s:0213 e:000212 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/base.rb:81c:0044 p:0056 s:0207 e:000205 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-fs-1.1.1/lib/winrm-fs/core/file_transporter.rb:213c:0043 p:0023 s:0200 e:000199 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-fs-1.1.1/lib/winrm-fs/core/file_transporter.rb:81c:0042 p:0034 s:0198 e:000197 METHOD C:/Ruby200/lib/ruby/2.0.0/benchmark.rb:281c:0041 p:0031 s:0190 e:000189 METHOD C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-fs-1.1.1/lib/winrm-fs/core/file_transporter.rb:79c:0040 p:0047 s:0179 e:000178 BLOCK
Jira (BOLT-258) Configuration options for the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-258
Configuration options for the PCP transport
Change By:
Michael Smith
The orchestrator pcp transport should be configurable from the bolt configuration file.example{code}pcp: service-url: ca-cert: token-file: task- environment:{code}service-url, cacert and token-file should be passed to the OrchestratorClient when it's created. If they are nil or not present they should not passed so defaults in the client library can be used.environment should be passed added to the task command body.User story for environmentWhen a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks. Users should be able to configure what environment is sent to orchestrator as part of the task command with the {{task-environment}} configuration option in the pcp section of bolt.yml
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 Unassigned Puppet Task Runner / BOLT-262 When orchestrator skips a task it does not produce a useful error in bolt Change By: Michael Smith Assignee: Michal Ruzicka 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-258) Configuration options for the PCP transport
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-258 Configuration options for the PCP transport Change By: Michael Smith Assignee: Lucy Wyman 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 (PUP-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8268
Install packages using beaker-puppet's puppet5 methods
Change By:
Josh Cooper
Modify the AIO 010_Install.rb step to call beaker's new {{install_from_build_data_url}} method to install puppet-agent on each host. This should work for all supported platforms including those without a package manager. We should add a gem dependency (from the acceptance Gemfile) on beaker-puppet since we're directly relying on methods provided by that gem. Also need to bump our beaker-hostgenerator dependency because we rely on {{packaging_platform}} when installing the package.
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 Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-32 Add ability to enumerate available plans 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 (PUP-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8268
Install packages using beaker-puppet's puppet5 methods
Change By:
Josh Cooper
Modify the AIO 010_Install.rb step to call beaker's new {{install_from_build_data_url}} method to install puppet-agent on each host. This should work for all supported platforms including those without a package manager. We should add a gem dependency (from the acceptance Gemfile) on beaker-puppet since we're directly relying on methods provided by that gem.
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 Josh Cooper updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Josh Cooper Comment: Use newer puppet5 installation methods when installing puppet-agent and puppetserver packages. 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
Josh Cooper updated an issue
Puppet / PUP-8268
Install packages using beaker-puppet's puppet5 methods
Change By:
Josh Cooper
Modify the AIO 010_Install.rb step to call beaker's new {{install_from_build_data_url}} method to install puppet-agent on each host. This should work for all supported platforms including those without a package manager.
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 moved an issue Puppet / PUP-8269 Application management 'plan' not working Change By: Thomas Hallgren Affects Version/s: PE Irving Key: ORCH PUP - 2170 8269 Project: Orchestration Puppet 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 Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-32 Add ability to enumerate available plans 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-269) winrm tests are causing a ruby segfault
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-269 winrm tests are causing a ruby segfault Issue Type: Bug Assignee: Unassigned Created: 2017/12/19 1:34 PM Priority: Normal Reporter: Alex Dreyer Occurrences: This has happened in the ruby 2.0.0 tests on C:/projects/bolt/spec/bolt/node/winrm_spec.rb:336 https://ci.appveyor.com/project/puppetlabs/bolt/build/0.1.0.928-master/job/52t58tfkllmjs7bi ...C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/power_shell.rb:174: [BUG] Segmentation fault ruby 2.0.0p648 (2015-12-16) [i386-mingw32] – Control frame information --- c:0060 p: s:0282 e:000281 CFUNC :inspect c:0059 p:0013 s:0279 e:000276 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/shells/power_shell.rb:174 c:0058 p:0040 s:0273 e:000272 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/psrp/receive_response_reader.rb:45 c:0057 p:0010 s:0269 e:000268 BLOCK C:/projects/bolt/.bundle/ruby/2.0.0/gems/winrm-2.2.3/lib/winrm/wsmv/receive_response_reader.rb:66 c:0056 p:0049 s:0266 e:000265 BLOCK
Jira (BOLT-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks 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-262) When orchestrator skips a task it does not produce a useful error in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-262 When orchestrator skips a task it does not produce a useful error in bolt Change By: Alex Dreyer Release Notes Summary: Bolt didn't handle skipped results from orchestrator. They now appear as errors with a type `puppetlabs.tasks/skipped-node`. This error will likely change in the future. Release Notes: Bug Fix 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 Alex Dreyer updated an issue Puppet Task Runner / BOLT-262 When orchestrator skips a task it does not produce a useful error in bolt 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-155) Show list of available tasks with bolt task show
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-155
Show list of available tasks with bolt task show
Change By:
Michael Smith
Release Notes Summary:
Bolt will not now list which tasks are available on the module path with {{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-155) Show list of available tasks with bolt task show
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-155
Show list of available tasks with bolt task show
Michelle Fredette this requires a docs update to: https://puppet.com/docs/bolt/0.x/running_tasks_and_plans_with_bolt.html
We should have a section for viewing which plans and tasks are available and the documentation for show. I guess we can make a separate ticket covering the three new feature tickets.
Change By:
Alex Dreyer
Release Notes Summary:
Bolt will not list which tasks are available on the module path with {{bolt task show}}
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
Jira (BOLT-258) Configuration options for the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-258 Configuration options for the PCP transport Michelle Fredette https://puppet.com/docs/bolt/0.x/bolt_configuration_options.html needs to be updated for this: PCP: service-url: The url of the orchestrator API cacert: The path to the CA certificate token-file: The path to the token file task-environment: The environment orchestrator should load task code from Change By: Alex Dreyer Release Notes Summary: The connections settings for orchestrator can now be specified in the bolt config file instead of being read from client-tools/orchestrator.conf. The bolt config can also specify which environment tasks should be loaded from in orchestrator. 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
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-155 Show list of available tasks with bolt task show 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-256) Bolt plan printing gets null plan with simple example
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-256 Bolt plan printing gets null plan with simple example Change By: Michael Smith Fix Version/s: BOLT 0.11.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-256) Bolt plan printing gets null plan with simple example
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-256 Bolt plan printing gets null plan with simple example Change By: Michael Smith Affects Version/s: BOLT 0.11.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-256) Bolt plan printing gets null plan with simple example
Title: Message Title Michael Smith commented on BOLT-256 Re: Bolt plan printing gets null plan with simple example Appears to no longer be an issue. 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-258) Configuration options for the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-258 Configuration options for the PCP transport 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-155) Show list of available tasks with bolt task show
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-155 Show list of available tasks with 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 Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks Change By: Michael Smith Assignee: Alex Leonhardt 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 Michael Smith assigned an issue to Alex Leonhardt Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks Change By: Michael Smith Assignee: Michael Smith Alex Leonhardt 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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Eric Sorenson Priority: Critical Major 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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Eric Sorenson assigned an issue to Eric Sorenson Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Eric Sorenson Assignee: Eric Sorenson 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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Eric Sorenson commented on PUP-8258 Re: Cached catalogs settings are ignored if noop is set to true Nick Lewis Josh Cooper do you think there would be other side-effects from putting a spot fix in for this? I am a bit concerned about it because changes to cached catalog interacting with other modes of operation have cropped up a couple of times ( PUP-6660 , PUP-6042 ). 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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Eric Sorenson When using the following configuration options together:```[agent]use_cached_catalog = truenoop = true```Cached catalogs settings are ignored and a new catalog is compiled every run. It is desirable to use both of these items together if your you are controlling the rollout of changes (cached catalogs) and having to do so during change windows (noop); but still want the ability to remediate drift against the original catalog (cached catalogs; `puppet agent -t`). 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 (PDB-3799) Merge 5.1.x -> master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3799 Merge 5.1.x -> master Issue Type: Bug Assignee: Unassigned Created: 2017/12/19 11:29 AM Priority: Normal Reporter: gepetto-bot 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-7861) beaker instructions at ./acceptance/readme seem to be wrong
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7861 beaker instructions at ./acceptance/readme seem to be wrong Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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 (PDOC-195) Could not find object: puppet_classes::_3A_3A
Title: Message Title
Brian Fekete created an issue
Puppet Strings / PDOC-195
Could not find object: puppet_classes::_3A_3A
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/12/19 11:05 AM
Environment:
puppet resource package puppet-strings package { 'puppet-strings': ensure => ['1.1.1'], }
puppet resource package yard package { 'yard': ensure => ['0.9.12'], }
Priority:
Normal
Reporter:
Brian Fekete
When the server is started via puppet strings server,
I can navigate to the modules and their init classes but cannot navigate to other classes within the module. When I click on the link to any other class other than init, the webpage displays:
Could not find object: puppet_classes::_3A_3A
Add Comment
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8249 Certain environments return "invalid byte sequence in " when parsing module PO files Change By: Eric Delaney Assignee: Eric Delaney 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 Sprint: Platform Core Grooming 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 (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 Sub-team: Coremunity 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 Josh Cooper updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Josh Cooper Sub-team: Coremunity 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 Josh Cooper updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Josh Cooper Team: Platform Core 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 Josh Cooper updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Josh Cooper Summary: Install packages using beaker -puppet 's puppet5 methods 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 Josh Cooper commented on PUP-8268 Re: Install packages using beaker-puppet's puppet5 methods Use newer puppet5 installation methods when installing puppet-agent and puppetserver packages. 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's puppet5 methods
Title: Message Title Josh Cooper created an issue Puppet / PUP-8268 Install packages using beaker's puppet5 methods Issue Type: Improvement Assignee: Unassigned Created: 2017/12/19 10:59 AM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message
Jira (PUP-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4543 Document how to run AIO puppet acceptance in acceptance_tests.md Change By: Josh Cooper Sub-team: Coremunity 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-7861) beaker instructions at ./acceptance/readme seem to be wrong
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7861 beaker instructions at ./acceptance/readme seem to be wrong Change By: Josh Cooper Sub-team: Coremunity 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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support
Title: Message Title Josh Cooper created an issue Puppet / PUP-8267 Rewrite acceptance rake tasks to leverage beaker subcommand support Issue Type: Improvement Assignee: Unassigned Created: 2017/12/19 10:57 AM Priority: Normal Reporter: Josh Cooper Rewrite the following acceptance tasks to leverage beaker subcommands: rake ci:test:aio rake ci:test:gem rake ci:test:git rake ci:test:quick
Jira (BOLT-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-268 Investigate using log4r for logging and stdoutoutput in bolt Issue Type: Task Assignee: Unassigned Created: 2017/12/19 10:56 AM Priority: Normal Reporter: Alex Dreyer questions: 1. Does log4r make it easy to handle loggers from puppet? 2. Does log4r make it easy to handle more standard loggers from net::ssh etc 3. Can we generate the output formates we print to stdout with log4r Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7861) beaker instructions at ./acceptance/readme seem to be wrong
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7861 beaker instructions at ./acceptance/readme seem to be wrong Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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-8266) Consolidate PDB testing/setup within Puppet acceptance
Title: Message Title Justin Stoller moved an issue Puppet / PUP-8266 Consolidate PDB testing/setup within Puppet acceptance Change By: Justin Stoller CI Pipeline/s: platform puppetserver Key: SERVER PUP - 2070 8266 Project: Puppet Server 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-8024) Only load module translations when necessary
Title: Message Title Eric Delaney commented on PUP-8024 Re: Only load module translations when necessary After trying to verify that I could produce the problem, I talked with Maggie. The original problem here was that the modules where configuring the config.yaml file incorrectly which caused a slow down. We've ask the modules team to correct the config.yaml file and we've changed the puppet server to not use the config.yaml file at all. So this issue should be addressed. 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-3495) acceptance pre-suite package install method should accept short SHA
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3495 acceptance pre-suite package install method should accept short SHA Change By: Josh Cooper Fix Version/s: PUP 4.10.z 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-3495) acceptance pre-suite package install method should accept short SHA
Title: Message Title Josh Cooper commented on PUP-3495 Re: acceptance pre-suite package install method should accept short SHA We could do this when running git style acceptance. Supporting this for aio depends on other RE improvements. 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-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Josh Cooper commented on PUP-4543 Re: Document how to run AIO puppet acceptance in acceptance_tests.md Will do this after we implement rakefile updates 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-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4543 Document how to run AIO puppet acceptance in acceptance_tests.md Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 4.10.z 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 updated an issue
Puppet Task Runner / BOLT-259
Config file should use .yaml extension
Change By:
Michael Smith
Other tools in the Puppet ecosystem use the {{.yaml}} extension rather than {{.yml}}. We should do the same for the default config file to be more consistent.Accept both {{.yaml}} and {{.yml}}. We should warn if both exist, and prioritize {{.yaml}}. Testing: unit test loading each type, and warning about both.
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 (PDB-3798) (maint) Bump to ezbake 1.7.4
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3798 (maint) Bump to ezbake 1.7.4 Issue Type: Bug Assignee: Unassigned Created: 2017/12/19 10:15 AM Priority: Normal Reporter: gepetto-bot This commit updates to the latest version of ezbake, which will allow clojure projects' repo-target to be interpreted by the packaging repo, ensuring builds get shipped to the correct repos. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-264) Allow run-as configuration option for ssh transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-264
Allow run-as configuration option for ssh transport
Change By:
Alex Dreyer
The ssh transport should allow users to configure {{run-as}} in the configuration file.It should require a string value.It should be overridden with {{--run-as}} flagAs part of this we should remove the {{--sudo}} flag. It should be added back in as something else when we support multiple escalation methods.Testing: unit test that config option ends up passed to ssh transport. We should add an integration test for ssh escalation using the config file or cli option
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
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-264
Allow run-as configuration option for ssh transport
Change By:
Alex Dreyer
The ssh transport should allow users to configure {{run-as}} in the configuration file.It should require a string value.It should be overridden with {{--run-as}} flagAs part of this we should remove the {{--sudo}} flag. It should be added back in as something else when we support multiple escalation methods.Testing: unit test that config option ends up passed to ssh transport.
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
Michael Smith updated an issue
Puppet Task Runner / BOLT-264
Allow run-as configuration option for ssh transport
Change By:
Michael Smith
The ssh transport should allow users to configure {{run-as}} in the configuration file.It should require a string value.It should be overridden with {{--run-as}} flagAs part of this we should remove the {{--sudo}} flag. It should be added back in as something else when we support multiple escalation methods. Testing: unit test that config option ends up passed to ssh transport.<
/span>
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
Michael Smith updated an issue
Puppet Task Runner / BOLT-32
Add ability to enumerate available plans
Change By:
Michael Smith
There is currently no feature in the 4.x loaders to enumerate all instances of a particular kind. We do need to enumerate plans as this is wanted from a UI / info perspective. We probably need to two tickets: one for puppet for the 4.x loader enumeration, and one for an info service that can be used from the UI.This should look like {{bolt task show}} but display a list of plan names.Testing: should test with no plans, some valid plans, some invalid plans via cli spec tests .
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
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-32
Add ability to enumerate available plans
Change By:
Alex Dreyer
There is currently no feature in the 4.x loaders to enumerate all instances of a particular kind. We do need to enumerate plans as this is wanted from a UI / info perspective. We probably need to two tickets: one for puppet for the 4.x loader enumeration, and one for an info service that can be used from the UI. This should look like {{bolt task show}} but display a list of 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 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
Michael Smith updated an issue
Puppet Task Runner / BOLT-32
Add ability to enumerate available plans
Change By:
Michael Smith
There is currently no feature in the 4.x loaders to enumerate all instances of a particular kind. We do need to enumerate plans as this is wanted from a UI / info perspective. We probably need to two tickets: one for puppet for the 4.x loader enumeration, and one for an info service that can be used from the UI.This should look like {{bolt task show}} but display a list of plan names. Should test with no plans, some valid plans, some invalid 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-32) Add ability to enumerate available plans
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-32
Add ability to enumerate available plans
Change By:
Michael Smith
There is currently no feature in the 4.x loaders to enumerate all instances of a particular kind. We do need to enumerate plans as this is wanted from a UI / info perspective. We probably need to two tickets: one for puppet for the 4.x loader enumeration, and one for an info service that can be used from the UI.This should look like {{bolt task show}} but display a list of plan names. Should Testing: should test with no plans, some valid plans, some invalid 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-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 Diagram of bolt output types https://docs.google.com/a/puppet.com/drawings/d/13YgP5aS0Ux3eaFvzr8rwOhYEusPFyEZjOqLtQV3Hrow/edit?usp=sharing 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 Michael Smith updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Michael Smith 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 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)- Log when actions start on nodes- Log the results of each action on each node NOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failedh2. 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
