Jira (PUP-7542) Puppet Config
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7542 Puppet Config Change By: Kenn Hussey Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7931) Support HTTPS Compression on report upload
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Change By: Kenn Hussey Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-920) Add catalog application information to report
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-920 Add catalog application information to report Change By: Kenn Hussey Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7545) Improve the reporting from agent runs
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7545 Improve the reporting from agent runs Change By: Kenn Hussey Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-351) Update help with tasks and examples on inventory file.
Title: Message Title Kate Lopresti commented on BOLT-351 Re: Update help with tasks and examples on inventory file. Reviewed and added to help. https://puppet.com/docs/bolt/0.x/inventory_file_generating.html Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-351) Update help with tasks and examples on inventory file.
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-351 Update help with tasks and examples on inventory file. Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-361) Gather facts from puppetdb
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-361 Gather facts from puppetdb Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-360) Store facts for targets in inventory
Title: Message Title Alex Dreyer moved an issue Puppet Task Runner / BOLT-360 Store facts for targets in inventory Change By: Alex Dreyer Key: PE BOLT - 23716 360 Project: Puppet Enterprise [Internal] Task Runner Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-57) Download a file
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-57 Download a file Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-57) Download a file
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-57 Download a file Change By: Alex Dreyer Sprint: Discover/Design Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-260) Should be easier to pass typed data on CLI
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-260
Should be easier to pass typed data on CLI
Change By:
Alex Dreyer
It's common to want to support boolean and integer types, which currently require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time.Handling for different target types:- The default behavior is a type that accepts a String.- If the target accepts a Boolean, Integer, Float, Number, or Enum, type specified in the plan is assignable to String do not attempt to coerce parse the value using Puppet's type conversion . e.g. {{Boolean('true')}}. - If the target type specified is a Variant of scalars, not assignable to String attempt to use each type conversion in the scalar in order. If one succeeds, use parse it as JSON and pass it on to puppet . If none succeed, it cannot be parsed raise a useful error. Questions:- Should we try to handle Regexp?- Should we bother handling Variants?
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Alex Dreyer Sprint: Discover/Design Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-359) Minifact plan
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-359 Minifact plan Issue Type: New Feature Assignee: Unassigned Created: 2018/02/27 3:32 PM Priority: Normal Reporter: Alex Dreyer This plan should accept a targetspec nodes. It should run the facter_task::shell task on all ssh nodes and update their facts in inventory It should run the facter_task::win task on all winrm nodes and update their facts in inventory The facter_task modules should get a facter::win and facter:shell task to handle gathering facts when the puppet run The facter::win and shell tasks should be updated check if facter is available an run facter returning all facts if possible. If facter is not available they should return the os structured fact similiar to what minifact already does. Add Comment
Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title
Reid Vandewiele commented on PDB-2634
Re: PQL & Hashes: Provide hash projection capability for facts & resource params
inventory[facts.sshrsakey, facts.sshecdsakey] { facts.os.family = "RedHat" and facts.os.release.major = "7" }
Seems like a pretty reasonable thing to query for, right? This is honestly the closest I think I can get today.
#!/bin/bash
query='
facts[certname,name,value] {
(
name = "sshrsakey" or
name = "sshecdsakey"
)
and inventory {
facts.os.family = "RedHat" and
facts.os.release.major = "7"
Jira (PUP-7326) Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts
Title: Message Title Ethan Brown assigned an issue to Unassigned Puppet / PUP-7326 Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8488) Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate
Title: Message Title
Eric Delaney commented on PUP-8488
Re: Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate
Looking through the modules, it appears that the only place that we stub out microsoft_windows? we're also stubbing windows?
./puppetlabs-inifile/spec/unit/puppet/type/ini_setting_spec.rb:Puppet.features.stub(:microsoft_windows?) { false }
./puppetlabs-inifile/spec/unit/puppet/type/ini_setting_spec.rb:Puppet::Util::Platform.stub(:windows?) { false }
./puppetlabs-inifile/spec/unit/puppet/type/ini_setting_spec.rb:Puppet.features.stub(:microsoft_windows?) { true }
./puppetlabs-inifile/spec/unit/puppet/type/ini_setting_spec.rb:Puppet::Util::Platform.stub(:windows?) { true }
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-7115) Un-vendor semantic_puppet gem for Puppet 6
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7115 Un-vendor semantic_puppet gem for Puppet 6 Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-352) Transport config format in config file differs from inventory file
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-352 Transport config format in config file differs from inventory file Change By: Michael Smith Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-352) Transport config format in config file differs from inventory file
Title: Message Title Michael Smith commented on BOLT-352 Re: Transport config format in config file differs from inventory file Kate Lopresti be warned that this will mean another overhaul of the inventory file docs. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-2634 PQL & Hashes: Provide hash projection capability for facts & resource params Change By: Owen Rodabaugh CS Priority: Normal Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8486) Warning for undefined variables is slow in jruby
Title: Message Title Patrick Carlisle commented on PUP-8486 Re: Warning for undefined variables is slow in jruby Based on further conversation with Henrik outside of this ticket I think this can be fixed by adding a catch in our code somewhere so it doesn't fall back to raising an exception. I'm investigating. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-332) Target objects should store state of the Targets
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-332 Target objects should store state of the Targets Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-347) Running Bolt incorrectly states that only powershell scripts are supported on Windows
Title: Message Title Kate Lopresti commented on BOLT-347 Re: Running Bolt incorrectly states that only powershell scripts are supported on Windows Thanks! Publishing topic, closing ticket. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-347) Running Bolt incorrectly states that only powershell scripts are supported on Windows
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-347 Running Bolt incorrectly states that only powershell scripts are supported on Windows Change By: Kate Lopresti Fix Version/s: Bolt 0.16.4 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-347) Running Bolt incorrectly states that only powershell scripts are supported on Windows
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-347 Running Bolt incorrectly states that only powershell scripts are supported on Windows Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8486) Warning for undefined variables is slow in jruby
Title: Message Title Josh Cooper commented on PUP-8486 Re: Warning for undefined variables is slow in jruby Henrik Lindberg We should always be doing perf measurements for compiler code against jruby. Soon it will be the only supported server stack. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-338) Local transport for bolt
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-338 Local transport for bolt Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-358) pcp transport config in Bolt config file doesn't work
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-358 pcp transport config in Bolt config file doesn't work Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-352) Transport config format in config file differs from inventory file
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-352 Transport config format in config file differs from inventory file Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-212) Add support for @todo tag
Title: Message Title Eric Putnam commented on PDOC-212 Re: Add support for @todo tag This has been requested by many community members Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-347) Running Bolt incorrectly states that only powershell scripts are supported on Windows
Title: Message Title Michael Smith commented on BOLT-347 Re: Running Bolt incorrectly states that only powershell scripts are supported on Windows Added some code formatting. Looks good now. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-221) Release 2.1.0
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-221 Release 2.1.0 Issue Type: Task Assignee: Unassigned Created: 2018/02/27 1:39 PM Priority: Normal Reporter: Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-347) Running Bolt incorrectly states that only powershell scripts are supported on Windows
Title: Message Title Kate Lopresti commented on BOLT-347 Re: Running Bolt incorrectly states that only powershell scripts are supported on Windows Michael Smith Here's what I've got so far for changing https://puppet.com/docs/bolt/0.x/running_bolt_commands.html#running-scripts Your thoughts? Original: On *nix, Bolt ensures that the script is executable on the remote system before executing it. For remote Windows systems, Bolt supports only PowerShell. Draft: On *nix, Bolt ensures that the script is executable on the remote system before executing it. For remote Windows systems, Bolt supports the extensions .ps1, .rb, and .pp. To enable other file extensions, add them to your Bolt config, as follows: winrm: extensions: [.py, .pl] Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-220) Release 2.0.0
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-220 Release 2.0.0 Issue Type: Task Assignee: Unassigned Created: 2018/02/27 1:38 PM Priority: Normal Reporter: Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-219) Puppet Strings 2.1.0
Title: Message Title Eric Putnam moved an issue Puppet Strings / PDOC-219 Puppet Strings 2.1.0 Change By: Eric Putnam Key: MODULES PDOC - 6695 219 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-358) pcp transport config in Bolt config file doesn't work
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-358 pcp transport config in Bolt config file doesn't work Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-358) pcp transport config in Bolt config file doesn't work
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-358 pcp transport config in Bolt config file doesn't work Issue Type: Bug Affects Versions: Bolt 0.16.4 Assignee: Unassigned Created: 2018/02/27 1:33 PM Priority: Normal Reporter: Michael Smith The service-url setting seems to be ignored if I put it in the pcp section of bolt.yaml. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-218) Puppet Strings 1.2.0
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-218 Puppet Strings 1.2.0 Issue Type: Epic Assignee: Unassigned Created: 2018/02/27 1:19 PM Priority: Normal Reporter: Eric Putnam Describes content of version 1.2.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDOC-217) add Eric Putnam as a gem owner
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-217 add Eric Putnam as a gem owner Issue Type: Story Assignee: Jesse Scott Created: 2018/02/27 1:11 PM Priority: Normal Reporter: Eric Putnam Please add Eric Putnam (putnam.e...@gmail.com) as an owner of the puppet-strings gem for releasing. https://rubygems.org/gems/puppet-strings Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Kate Lopresti commented on BOLT-337 Re: Nodes in inventory groups should accept "host:port" syntax Added to release notes under New Features Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8491) Move essential functions from stdlib to puppet
Title: Message Title R.I.Pienaar commented on PUP-8491 Re: Move essential functions from stdlib to puppet I'd love to see these move too they seem like the most basic things one would want in a modern language I think to_json and to_yaml would be great - perhaps with some changes so there's a optional flag to enable the pretty version of json. likewise loadjson and loadyaml (renamed for consistency I guess?) The things like downcase, upcase, capitalize, lstrip, rstrip, strip, chop, chomp and such basic string manipulation ones. Also min, max, flatten, sort and unique - these are unfortunately all v3 functions. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-263) log bolt results to a log file
Title: Message Title Michael Smith assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-263 log bolt results to a log file Change By: Michael Smith Assignee: Michael Smith Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-336) Treat --nodes as the nodes parameter for run plan
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-336 Treat --nodes as the nodes parameter for run plan Change By: Michael Smith Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8497) move the length() function from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-8497 move the length() function from stdlib to puppet Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8497) move the length() function from stdlib to puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8497 move the length() function from stdlib to puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/02/27 11:42 AM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-8491) Move essential functions from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8491 Move essential functions from stdlib to puppet Change By: Henrik Lindberg The most essential functions in stdlib should be moved to puppet code base.* empty* keys* values* join* flatten * length (instead of deprecated 'size') This is of particular value when running scripts. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8492) Move the empty() function from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8492 Move the empty() function from stdlib to puppet Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8496 move keys() and values() functions from stdlib to puppet Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8488) Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate
Title: Message Title Eric Putnam updated an issue Puppet / PUP-8488 Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate Change By: Eric Putnam Convert usage of [Puppet.features.microsoft_windows?|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/feature/base.rb#L17] to [Puppet::Util::Platform.windows?|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/ windows platform .rb #L7 ] where appropriate.We need to be careful when reviewing the usages, its ok to mock the usage of Puppet.features.microsoft_windows? however we should NOT be mocking out the Puppet::Util::Platform.windows?, so care must be taken to ensure the things we convert make sense and that we continue to have the proper testing coverage. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-357 bolt-inventory-pdb omits confusing error with no arguments Issue Type: Bug Affects Versions: Bolt 0.16.4 Assignee: Unassigned Created: 2018/02/27 10:56 AM Priority: Normal Reporter: Michael Smith When bolt-inventory-pdb is run with no arguments, it emits Error: -inventory is a required option. -inventory is not a valid option. This should state that an input file is required. It's a positional parameter. Add Comment
Jira (PUP-8488) Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate
Title: Message Title Eric Putnam updated an issue Puppet / PUP-8488 Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate Change By: Eric Putnam Convert usage of [ Puppet.features.microsoft_windows? |https://github.com/puppetlabs/puppet/blob/master/lib/puppet/feature/base.rb#L17] to [ Puppet::Util::Platform.windows? |https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows.rb] where appropriate.We need to be careful when reviewing the usages, its ok to mock the usage of Puppet.features.microsoft_windows? however we should NOT be mocking out the Puppet::Util::Platform.windows?, so care must be taken to ensure the things we convert make sense and that we continue to have the proper testing coverage. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it,
Jira (PUP-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8496
move keys() and values() functions from stdlib to puppet
Change By:
Henrik Lindberg
Sub-team:
Language
Release Notes Summary:
The functions {{keys()}} and {{values()}} has moved from stdlib to puppet.
Team:
Platform Core
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post
Jira (PUP-8492) Move the empty() function from stdlib to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8492
Move the empty() function from stdlib to puppet
Change By:
Henrik Lindberg
Release Notes Summary:
The {{empty()}} function has moved from stdlib to puppet , and now also supports answering if a {{Binary}} value is empty (has zero bytes) .
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8488) Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate
Title: Message Title Eric Putnam commented on PUP-8488 Re: Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate e.g. https://github.com/puppetlabs/puppetlabs-inifile/blob/master/spec/unit/puppet/type/ini_setting_spec.rb https://github.com/puppetlabs/puppetlabs-hocon/blob/master/lib/puppet/type/hocon_setting.rb#L15 https://github.com/puppetlabs/puppetlabs-registry/blob/master/spec/unit/puppet/provider/registry_value_spec.rb#L6 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8496
move keys() and values() functions from stdlib to puppet
Change By:
Henrik Lindberg
The functions {{keys()}} and {{values()}} from stdlib should be moved to puppet and the 4.x function API.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-8496 move keys() and values() functions from stdlib to puppet Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8496) move keys() and values() functions from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8496 move keys() and values() functions from stdlib to puppet Change By: Henrik Lindberg Summary: move keys() function and values() functions from stdlib to puppet Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8496) move keys() function from stdlib to puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8496 move keys() function from stdlib to puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/02/27 10:38 AM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-343) Document Bolt with Orchestrator
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-343 Document Bolt with Orchestrator Change By: Michael Smith Add an introductory section about using Bolt with Orchestrator.Note that it will try to inherit config if puppet-task is already setup, can override with Bolt configuration.Bolt must be installed on Puppet Masters as a module. puppet-task user needs to have permission to run the Bolt task (part of Bolt-as-a-module), which grants essentially full root access on nodes for which it's allowed.Runs 1 Orchestrator job per call to run_task/run_command/run_script/file_upload. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-354) Extendable metadata for Bolt
Title: Message Title Carl Caum commented on BOLT-354 Re: Extendable metadata for Bolt Gert Drapers You might want to track this ticket too. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-260) Should be easier to pass typed data on CLI
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-260
Should be easier to pass typed data on CLI
Change By:
Michael Smith
A common pattern being established in plans is to pass an array of nodes. Our example at https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters did that by passing a comma-separated list, which doesn't work at all. It's also common to want to support boolean and integer types, which currently also require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time. One challenging example of this is from our plan docs Handling for different target types : {{Variant[String[1], Array[String[1]]] $backends}} with - The default behavior is a CLI arg of {{backends=kermit type that accepts a String . myorg.com,gonzo.myorg.com}} could either be - If the target accepts a string Boolean , Integer, Float, Number, or an array of 2 items Enum, attempt to coerce the value using Puppet's type conversion . Also {{backends=kermit e . myorg g . com {{Boolean('true') }} could be .- If the target is a string or an array Variant of 1 item scalars, attempt to use each type conversion in the scalar in order . We'll need If one succeeds, use it. If none succeed, error.Questions:- Should we try to decide how to handle that. Regexp?- Should we bother handling Variants?
Add Comment
This
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Michael Smith commented on BOLT-260 Re: Should be easier to pass typed data on CLI We've done something specific to handle arrays of targets. This ticket can be updated to handling scalar types only. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: David Kramer Sprint: Discover/Design Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: Alex Dreyer * Bolt should accept a pql query as a target in addition to a list of nodes.* On the commandline the user should pass --query | instead of a --nodes query when they want to use puppetdb as the target source* Bolt should make this query to puppetdb and collect certnames from the top level of results. These certnames should be used as the list of nodes to act on* Bolt should error if both --nodes and --query are specified or query is specified twice* Bolt should accept -q as a short form of the --query flag* Bolt should use the[ puppetdb client config](https://docs.puppet.com/puppetdb/5.1/pdb_client_tools.html#example-configuration-file-pe-client-tools) to connect to puppetdb if it does not yet have it's own config file Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-167 I want to pass a pql query instead of a list of nodes. Change By: Alex Dreyer * Bolt should accept a pql query as a target in addition to a list of nodes.* On the commandline the user should pass --query | instead of a --nodes query when they want to use puppetdb as the target source* Bolt should make this query to puppetdb and collect certnames from the top level of results. These certnames should be used as the list of nodes to act on* Bolt should error if both --nodes and --query are specified or query is specified twice * Bolt should use the[ puppetdb client config](https://docs.puppet.com/puppetdb/5.1/pdb_client_tools.html#example-configuration-file-pe-client-tools) to connect to puppetdb if it does not yet have it's own config file Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
Jira (BOLT-171) Bolt should be able to use puppet-server as a task store
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-171 Bolt should be able to use puppet-server as a task store Change By: Alex Dreyer Sprint: Discover/Design Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-356) Option to ignore local tasks when using pcp transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Change By: Michael Smith When targeting only orchestrator nodes run_* functions should not error or validate params. when the task is not installed locally. When the task is installed locally and only targets orchestrator nodes we should not validate parameters. When the targets include non-orchestrator nodes we should validate parameters and fail the entire function call if validation fails or the task isn't present without executing on any targets. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-356) Option to ignore local tasks when using pcp transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Change By: Alex Dreyer Sprint: Bolt Kanban When targeting only orchestrator nodes run_* functions should not error or validate params. when the task is not installed locally.When the task is installed locally and only targets orchestrator nodes we should not validate parameters.When the targets include non-orchestrator nodes we should validate parameters and fail the entire function call if validation fails or the task isn't present without executing on any targets. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport Issue Type: New Feature Assignee: Unassigned Created: 2018/02/27 9:33 AM Priority: Normal Reporter: Alex Dreyer When targeting only orchestrator nodes run_* functions should not error or validate params. when the task is not installed locally. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-343) Document Bolt with Orchestrator
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-343 Document Bolt with Orchestrator Change By: David Kramer Sprint: Discover/Design Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-355) I want to store facts on a target in inventory
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-355 I want to store facts on a target in inventory Issue Type: New Feature Assignee: Unassigned Created: 2018/02/27 9:19 AM Priority: Normal Reporter: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-354) Extendable metadata for Bolt
Title: Message Title Yasmin Rajabi commented on BOLT-354 Re: Extendable metadata for Bolt Steve Quin thanks yeah, he sent me his doc we are meeting later today. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-345) Bolt should provide a better summary of failures
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-354) Extendable metadata for Bolt
Title: Message Title Steve Quin commented on BOLT-354 Re: Extendable metadata for Bolt Yasmin Rajabi & Carl Caum Just a heads up, Gert's in PDX this week, worth grabbing him. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-354) Extendable metadata for Bolt
Title: Message Title Yasmin Rajabi commented on BOLT-354 Re: Extendable metadata for Bolt Carl Caum thanks, my first thought is we wouldn't want it to be arbitrary since interacting with the file probably should be the same throughout the 3 experiences? but good to discuss with the team Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Change By: Alex Dreyer Fix Version/s: Bolt 0.16.4 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-354) Extendable metadata for Bolt
Title: Message Title Carl Caum commented on BOLT-354 Re: Extendable metadata for Bolt Yasmin Rajabi Yep. I'll put something together Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-354) Extendable metadata for Bolt
Title: Message Title Carl Caum commented on BOLT-354 Re: Extendable metadata for Bolt FYI Scott Walker, Dave Johnston, and Steve Quin. Let's use this ticket to discuss what we'll need from the metadata schema in tasks. Yasmin Rajabi and Alex Dreyer, my thinking is that if we allow for the current schema to allow for arbitrary data to be added to the metadata.json file, then the Puppet Discovery team can build our own schema. Thoughts? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-354) Extendable metadata for Bolt
Title: Message Title Yasmin Rajabi commented on BOLT-354 Re: Extendable metadata for Bolt Alex Dreyer ^^ Carl Caum we should meet with the teams and understand the requirements. late this week or early next week? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-354) Extendable metadata for Bolt
Title: Message Title Carl Caum created an issue Puppet Task Runner / BOLT-354 Extendable metadata for Bolt Issue Type: Story Assignee: Yasmin Rajabi Created: 2018/02/27 9:02 AM Priority: Normal Reporter: Carl Caum When I'm building an integration with Bolt tasks And that integration requires metadata not currently in the task schema I want the metadata schema to be easily extended for my needs So that the new metadata can be added to new and existing tasks without breaking Bolt Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Eric Delaney Method Found: Needs Assessment Inspection Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8459) ENC acceptance tests didn't catch regression
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8459) ENC acceptance tests didn't catch regression
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8495) Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Title: Message Title
Kolbjørn Barmen created an issue
Puppet / PUP-8495
Ubuntu 16.10 _AND NEWER_ use systemd provider as default
Issue Type:
Bug
Affects Versions:
PUP 4.10.10
Assignee:
Unassigned
Created:
2018/02/27 7:46 AM
Environment:
Ubuntu
Priority:
Normal
Reporter:
Kolbjørn Barmen
Puppet Version: Puppet Server Version: OS Name/Version: Detection of systemd fails on Ubuntu releases higher than 16.10 Desired Behavior: disabling/enabling services should work as normal also on Ubuntu 17.04 and up. As one can see here: https://github.com/puppetlabs/puppet/commit/ef342d4ced9bf7aa0489005119bf80a298d094f2 Ubuntu is only supported up to 16.10 - why is this hardcoded in like this, instead of saying Ubuntu with releases from 15.04 and up use systemd, while those below use sysc-rc - the problem is now that puppet tries to use sysv-rc on Ubuntu 17.04 and up as well. Actual Behavior: ubuntu1710 ~ # puppet resource service ipmievd enable='false' dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files;Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! Notice: /Service[ipmievd]/enable: enable changed 'true' to 'false' service { 'ipmievd': enable => 'true', } ubuntu1710 ~ # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.10 Release: 17.10 Codename: artful ubuntu1710 ~ #
Jira (PUP-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Thomas Hallgren commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original I added a reference to PUP-7571 for some background on why things are as they are in the puppet code-base. It might be good to also involve Josh Cooper in the discussions. What should happen, is that the current gem stays as it is and replaces the vendored one at an appropriate time (probably in 6.0). Puppet agent should ship the same gem. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title R.I.Pienaar commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet is 1.0.1, I have no idea why the 0.1.2 one is there, its just a headache Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Thomas Hallgren commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original If puppet agent ships version 0.1.2, then that's another problem that should be dealt with. It's very old. The version discussed here is version 1.0.1. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title R.I.Pienaar commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original Puppet Agent ships both, it would be better if there was just one /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/semantic_puppet-0.1.2 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-8486) Warning for undefined variables is slow in jruby
Title: Message Title Henrik Lindberg commented on PUP-8486 Re: Warning for undefined variables is slow in jruby We need supported code paths to be fast and still handle when people just call scope and do not handle the error case. We found that a throw is much faster than a raise. At the point (in scope) where a variable is referenced it cannot be determined what a missing var should result in - hence the gymnastics of a throw followed by an exception if the throw was unhandled. Change is certainly possible, but it must be considered API. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Thomas Hallgren commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original I think this is based on a misunderstanding. The difference was initiated as a path of least resistance to retain backward compatibility in Puppet until we deemed it appropriate to swap Puppet into the correct behavior by replacing the vendored version with the gem. The gem has the correct behavior and the vendored behavior is definitely not desired in the gem. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8494) Issue based errors are formatted too early and arguments are lost.
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8494 Issue based errors are formatted too early and arguments are lost. Issue Type: Improvement Assignee: Unassigned Created: 2018/02/27 6:39 AM Priority: Normal Reporter: Thomas Hallgren One objective with formalizing all errors and warnings into an IssueCode with an associated argument Hash, is to make it possible to write tests asserting that the correct issues are raised and initialized with the correct arguments (as opposed to checking for specific pre-formatted messages which changes more often and differ from locale to locale). At present though, such tests are impossible because classes like Puppet::ParseErrorWithIssue performs the formatting of the final message when the actual error is instantiated and throws away the arguments in the process. Left is just the formatted message and the issue_code. This must change. Instead of storing a formatted message and the issue_code, the error should store the actual issue and the associated argument hash. The actual formatting of the issue can take place when the message is requested. Add Comment
Jira (BOLT-324) Add automated Bolt testing against Orchestrator
Title: Message Title Michal Ruzicka assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-324 Add automated Bolt testing against Orchestrator Change By: Michal Ruzicka Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.
