Jira (PUP-9646) Return parsed yaml plan without instantiating
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet / PUP-9646 Return parsed yaml plan without instantiating Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9646) Return parsed yaml plan without instantiating
Title: Message Title Lucy Wyman created an issue Puppet / PUP-9646 Return parsed yaml plan without instantiating Issue Type: Task Assignee: Unassigned Created: 2019/04/16 5:11 PM Priority: Normal Reporter: Lucy Wyman In order to convert a YAML plan to Puppet we want to return the parsed yaml plan without actually instantiating the plan, which creates a closure around the plan. We still need to load the plan so want to reuse the same loading functions but call parse_plan instead of instantiate on the generic plan instantiator. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1256) bolt server reports things as failed task run when it couldnt connect
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-1256 bolt server reports things as failed task run when it couldnt connect Issue Type: Bug Assignee: Unassigned Created: 2019/04/16 4:52 PM Environment: the expected behavior is in this ticket https://tickets.puppetlabs.com/browse/PE-25657 however bolt is not correctly reporting the failed task runs leading to incorrect licensing Priority: Normal Reporter: Yasmin Rajabi Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1188) Support experimental v2 inventory format
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1188
Support experimental v2 inventory format
Change By:
Alex Dreyer
To allow faster iteration on inventory bolt should support a v2 inventory format.- inventory files should be loaded as v2 files if they contain a "version: 2" key at the top level.- version 2 inventory should allow all transport config options to override options from the name.(discuss what this means)Requirements- nodes must have a name that gets displayed- You can always refer to a node by it's name and possibly aliases.- The host needs to be set separately from the name.- {{--user}} or {{--transport}} should not override a user passed to {{--nodes}} on the commandline.- If a node is defined in one group with a full hash with name and connection info and referred to as a bare string in another group that bare string should not be used as the URI(this seems hard but possible by deferring evaluation)Solution:- If you have just a string as the node entry that string is used as the URI.- If you pass a string to {{--nodes}} that does not match a group or node name that string will be used as the uri.- The name defaults to the value of the uri if set- The name may be set explicitly in which case a URI does not have to be set.- host, password, user and other uri parts can be set in the transport config but uri will override them- If a node has no config values set and only a name it should error when a transport that requires config attempts to run it . .
Add Comment
This mes
Jira (PUP-8909) Add proxy support
Title: Message Title Josh Cooper commented on PUP-8909 Re: Add proxy support Closing this for now. Will reopen if/when it's needed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-1255) Send release announcements (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1255 Send release announcements (Bolt 1.17.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.17.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.17.0 is now available".
Jira (BOLT-1254) Docs for bolt release (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1254 Docs for bolt release (Bolt 1.17.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) Release notes and docs changes for bolt 1.17.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1252) Update the release spreadsheet (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1252 Update the release spreadsheet (Bolt 1.17.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) Update the release google spreadsheet for Bolt 1.17.0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1248) Bolt 1.17.0 2019-04-18 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1248 Bolt 1.17.0 2019-04-18 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/04/16 1:10 PM Priority: Normal Reporter: Cas Donoghue Bolt 1.17.0 2019-04-18 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1250) Kick off release pipeline (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1250 Kick off release pipeline (Bolt 1.17.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1253) Update homebrew-puppet (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1253 Update homebrew-puppet (Bolt 1.17.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1251) Publish release artifacts (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1251 Publish release artifacts (Bolt 1.17.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) Run the Bolt shipping pipeline. Set REF to 1.17.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel. Add Comment This message was sent by Atlassian JIRA (v7.7.1#
Jira (BOLT-1249) Reconcile git commits, JIRA tickets, and versions (Bolt 1.17.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1249 Reconcile git commits, JIRA tickets, and versions (Bolt 1.17.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/16 1:10 PM Due Date: 2019/04/18 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-18) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (PDB-4340) SPIKE: investigate improving reports / resource events table
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4340 SPIKE: investigate improving reports / resource events table Change By: Robert Roland Assignee: Robert Roland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-9585 Do not output password for user type if it is marked Sensitive Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1592) Networking key/value pair for Interface Speed and Duplex State
Title: Message Title Joseph Oaks commented on FACT-1592 Re: Networking key/value pair for Interface Speed and Duplex State Is there a status on this? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-7138) debug output of sensitive resources or attributes thereof should be redacted
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7138 debug output of sensitive resources or attributes thereof should be redacted Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9630) Prepare release announcement (Puppet Platform 6.4.1)
Title: Message Title Jean Bond commented on PUP-9630 Re: Prepare release announcement (Puppet Platform 6.4.1) lgtm! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1110) Publish schema for bolt configuration files for puppet vscode extension
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1110 Publish schema for bolt configuration files for puppet vscode extension Change By: David Kramer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1154) Evaluate guard conditions in bolt plan functions
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1154 Evaluate guard conditions in bolt plan functions Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-920) Bolt unable to connect with ecdsa key
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-920 Bolt unable to connect with ecdsa key Change By: David Kramer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1038) Add acceptance tests for bundled content
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1038 Add acceptance tests for bundled content Change By: David Kramer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8399) Exec onlyif and unless should support sensitive data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8399 Exec onlyif and unless should support sensitive data Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1243) When a command is not specified on CLI a helpful error message is not raised
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1243 When a command is not specified on CLI a helpful error message is not raised Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Type information not available in plans.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1223
Type information not available in plans.
Change By:
Alex Dreyer
The use of {{type}} to refer to the type of action that created a result object is unable to be exposed as an attribute on the result object since {{type}} is used elsewhere in Puppet.Solution:1. Rename this key to {{action}} and expose it with a method, the values should remain the same.2. Add a {{to_data}} method to all bolt datatypes that return a hash or array equivalent of their json output. This will make the usecase which triggered the initial ticket, the ability to pass the result from one action directly to a task easier. This may or may not include renaming type. Note the "target" in a Result should be the name not the full target hash. Adding to_data to Target is out of scope
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsub
Jira (BOLT-1223) Type information not available in plans.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1223
Type information not available in plans.
Change By:
Alex Dreyer
The use of {{type}} to refer to the type of action that created a result object is unable to be exposed as an attribute on the result object since {{type}} is used elsewhere in Puppet. Possible solutions Solution :1. Rename this key to {{action}} and expose it with a method , the values should remain the same .2. Add a {{to_data}} method to the Result object all bolt datatypes that returns return a hash or array equivalent to the of their json output. This will make the usecase which triggered the initial ticket, the ability to pass the result from one action directly to a task easier. This may or may not include renaming type.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails
Jira (BOLT-1244) SELinux management does not work on localhost
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1244 SELinux management does not work on localhost Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Type information not available in plans.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1223 Type information not available in plans. Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1227) Document how Bolt will use local SSH config
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1227 Document how Bolt will use local SSH config Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1227) Document how Bolt will use local SSH config
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1227 Document how Bolt will use local SSH config Change By: David Kramer h1. The ProblemBolt will use local SSH config under certain circumstances and we should list when and how that works. We also need to determine where in the documentation this is appropriately placed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1225) Link to packaged plans and tasks from running * pages
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1225 Link to packaged plans and tasks from running * pages Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1225) Link to packaged plans and tasks from running * pages
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1225
Link to packaged plans and tasks from running * pages
Change By:
Lucy Wyman
Discovering bundled content isn't clear in our docs, and if a user doesn't run {{bolt [plan|task] show}} after installing they may never find that content. We should add a link and small blurb to https://puppet.com/docs/bolt/latest/bolt_running_plans.html and https://puppet.com/docs/bolt/latest/bolt_running_tasks.html, and maybe https://puppet.com/docs/bolt/latest/inspecting_tasks_and_plans.html linking to https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#packaged-modules and indicating that there is bundled content.Throw some links around
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To
Jira (BOLT-126) Support WinRM with Kerberos
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-126 Support WinRM with Kerberos Change By: Ethan Brown Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1242) run_as on localhost bugs
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1242 run_as on localhost bugs Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1242) run_as on localhost bugs
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1242 run_as on localhost bugs Change By: Lucy Wyman Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9610) Prepare release announcement (Puppet Platform 6.0.8)
Title: Message Title Jean Bond commented on PUP-9610 Re: Prepare release announcement (Puppet Platform 6.0.8) This looks fine to me! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1158) Publish bash helper library
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1158 Publish bash helper library Change By: Alex Dreyer Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9502) codesigning puppet executables on macOS 10.14
Title: Message Title Marshall Taylor commented on PUP-9502 Re: codesigning puppet executables on macOS 10.14 @Gheorghe Popescu I have opened PUP-9645. Thanks for the suggestion. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title
Marshall Taylor updated an issue
Puppet / PUP-9645
User Rights Management SIP issue on MacOS 10.14.x
Change By:
Marshall Taylor
*Puppet Version: 6.4.0* *Puppet Server Version: 6.3.0* *OS Name/Version: MacOS 10.14.3*Since moving to Mojave I have been unable to run puppet agent --test without first booting into Recovery Mode and disabling SIP with 'csrutil disable'. I then boot normally and run puppet to configure my Macs, then boot back into Recovery Mode to reenable SIP. I suspect it's a result of this issue. Below is the output that I get when I attempt to run puppet with SIP enabled on a 10.14.3 system: {noformat} FVF23JIL23KD:~ jdoe$ sudo /opt/puppetlabs/puppet/bin/puppet agent --testPassword:Info: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Loading factsInfo: Caching catalog for fvf23jil23kd.company.comInfo: Applying configuration version 'puppet-production-50e48363285'Notice: Hiera returned role: mac_laptopNotice: /Stage[main]/Main/Notify[Hiera returned role: mac_laptop]/message: defined 'message' as 'Hiera returned role: mac_laptop'Error: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/company_admin.plistError: /Stage[main]/company_mac::Config/User[company_admin]/password: change from [redacted] to [redacted] failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/company_admin.plistError: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/company_admin.plistError: /Stage[main]/company_mac::Config/User[company_admin]/salt: change from '2922d494d507d8228f83cd286788b3bd188bebb507c911424332ae9031a7e804' to '40cb359a1408e382fd1198f86eaa7d3b1ccdb522f105662c0afd916c576872c9' failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/company_admin.plistError: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/laptop_admin.plistError: /Stage[main]/company_mac::Config/User[company_admin]/iterations: change from 74626 to 28328 failed: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/company_admin.plistNotice: /Stage[main]/company_mac::Config/File[/var/company_admin]: Dependency User[company_admin] has failures: trueWarning: /Stage[main]/company_mac::Config/File[/var/company_admin]: Skipping because of failed dependenciesInfo: Stage[main]: Unscheduling all events on Stage[main]Notice: Applied catalog in 13.34 seconds{noformat} Puppet appears unable to manage user rights with SIP enabled.*Desired Behavior:*Puppet client could manage user rights without needing to disable SIP.*Actual Behavior:*(attached)
Jira (PUP-9645) User Rights Management SIP issue on MacOS 10.14.x
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9645 User Rights Management SIP issue on MacOS 10.14.x Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9639) Windows package resource does not remove trailing whitespace
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9639 Windows package resource does not remove trailing whitespace Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9643) Issue in protection against illegal methods in legacy functions
Title: Message Title Henrik Lindberg commented on PUP-9643 Re: Issue in protection against illegal methods in legacy functions That is a change in Ruby itself. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9601 mount resource should trigger 'systemctl daemon-reload' Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9569) Crontab prefetch fails when the filename is not a valid user
Title: Message Title Gheorghe Popescu commented on PUP-9569 Re: Crontab prefetch fails when the filename is not a valid user This issue is not reproducible after the changes made to crontab provider in 5.5.9. Upgrading puppet to a newer version should fix it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9569) Crontab prefetch fails when the filename is not a valid user
Title: Message Title Gheorghe Popescu commented on PUP-9569 Re: Crontab prefetch fails when the filename is not a valid user Jarret Lavallee seems that this issue was solved in newer puppet versions. Tested on 5.5.9 [root@host ~]# puppet --version 5.5.9 [root@host ~]# puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Info: Caching catalog for host.delivery.puppetlabs.net Info: Applying configuration version '1555417727' Notice: /Stage[main]/Main/Node[default]/Cron[logrotate]/ensure: created Error: /Stage[main]/Main/Node[default]/Cron[logrotate]: Could not evaluate: Cannot write the #tmp.khATKA user's crontab: The user does not exist Notice: Applied catalog
Jira (PUP-9643) Issue in protection against illegal methods in legacy functions
Title: Message Title
Thorsten Schlump commented on PUP-9643
Re: Issue in protection against illegal methods in legacy functions
Thank you for your input. Found solution for the issue: replace
subentry[firstargnr].start_with?("#")
by
subentry[firstargnr].start_with?('#')
Sounds like this has been identified as a comment sign previously. Is this a bug or a feature?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are su
Jira (FACT-1906) networking.dhcp fact is blank on RedHat 8 beta
Title: Message Title Denis Susan updated an issue Facter / FACT-1906 networking.dhcp fact is blank on RedHat 8 beta Change By: Denis Susan Release Notes Summary: Issue resolved in 3.13.x Release Notes: Not Needed Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9569) Crontab prefetch fails when the filename is not a valid user
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9569 Crontab prefetch fails when the filename is not a valid user Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
