Jira (BOLT-1443) Add more demos for Bolt at Oscon
Title: Message Title Cas Donoghue assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1443 Add more demos for Bolt at Oscon Change By: Cas Donoghue 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314797.1562011067000.5984.1562199240101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1445) Update plan logging docs to prefer out::message
Title: Message Title Cas Donoghue assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1445 Update plan logging docs to prefer out::message Change By: Cas Donoghue Assignee: Cas Donoghue 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314807.1562014515000.5981.1562199180085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1303) Provide a Bolt Docker Image
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1303 Provide a Bolt Docker Image Change By: Cas Donoghue Release Notes: Not 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308633.1557866171000.5977.1562199060336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1456) bolt debug output shows task input as a ruby hash, not json
Title: Message Title
Ben Ford created an issue
Puppet Task Runner / BOLT-1456
bolt debug output shows task input as a ruby hash, not json
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/07/03 4:58 PM
Priority:
Normal
Reporter:
Ben Ford
For example,
Running '/var/folders/km/cz24f0_j1bs4sh93q82sftp0gq/T/d20190703-40142-1rj497t/swagger_gen_post_usersuser_idplaylistsplaylist_idtracks.rb' with {"endpoint_api"=>"https://api.spotify.com/v1", "token"=>"BQAkqyzq6RUTfZ4-epCjQbXS4zVS57YRCYGd6S2MDIzR7D4hjSfXN2PNgUWR4m7Guei4jIWfRqJQxklo88NyjPTGodWmVpcC8Yf2JeIREPkMFE8TzHcpbPpts9PYYUvN4XFzzN8BSWRe2JxrNs9AdoikJ0eqXj7CM2biNJhDMecOHpWWkQEiFPYk0zbtEybOvEPbBL_R07cIJDd3g3KmgQ1LUu4RUDU", "playlist_id"=>"spotify:playlist:4zHrEyszkWe0Owxw44YjEL", "uris"=>"spotify:track:5osIjZhkEUjH4d2qtGd367", "_task"=>"gen::swagger_gen_post_usersuser_idplaylistsplaylist_idtracks"}
if that output were a JSON hash, then I could easily cut&paste it to the command line to debug my task.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-1222
Support an "apply" step.
Change By:
Cas Donoghue
Release Notes Summary:
Yaml plans now support applying puppet resources with a {{resources}} step.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302484.1554141988000.5955.1562197260555%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1222 Support an "apply" step. Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302484.1554141988000.5950.1562197200206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1222 Support an "apply" step. Change By: Cas Donoghue Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302484.1554141988000.5942.1562197140745%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1303) Provide a Bolt Docker Image
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1303 Provide a Bolt Docker Image Change By: Lucy Wyman Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308633.1557866171000.5901.1562195220443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title
Chris Suszynski updated an issue
Puppet / PUP-9813
Performance of unpacking modules is extremely slow
Change By:
Chris Suszynski
*Puppet Version: any* *Puppet Server Version: any* *OS Name/Version: any*Installing modules from Puppet Forge is extremelly extremely slow. I have found a culprit. It is a{{Puppet::ModuleTool::Tar::Mini}}implementation.The unpack is * 100x times * slower then executing a \ {{tar xzvf}} system command . ! *Steps to reproduce:*Install a module from Puppet Forge and measure a time:{{time puppet module install puppetlabs-stdlib --version 4.25.1}}Then execute:{{time bash -c 'curl [https://forge.puppet.com/v3/files/puppetlabs-stdlib-4.25.1.tar.gz] -o puppetlabs-stdlib-4.25.1.tar.gz && tar xzvf puppetlabs-stdlib-4.25.1.tar.gz'}}*Desired Behavior:*Extraction of downloaded modules should be about the same performance as system tar xzvf command. It might be at most 2x times slower then system command, but preferably should be about the same. * Temporal solution: * To install modules faster i propose to switch to Gnu implementation as a first choice. Al least until Minitar can be much faster.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title
Chris Suszynski updated an issue
Puppet / PUP-9813
Performance of unpacking modules is extremely slow
Change By:
Chris Suszynski
*Puppet Version: any* *Puppet Server Version: any* *OS Name/Version: any*Installing modules from Puppet Forge is extremelly slow. I have found a culprit. It is a{{Puppet::ModuleTool::Tar::Mini}}implementation.The unpack is 100x times slower then executing a \ {{tar xzvf }}system command.*Steps to reproduce:*Install a module from Puppet Forge and measure a time:{{time puppet module install puppetlabs-stdlib --version 4.25.1}}Then execute:{{time bash -c 'curl [https://forge.puppet.com/v3/files/puppetlabs-stdlib-4.25.1.tar.gz] -o puppetlabs-stdlib-4.25.1.tar.gz && tar xzvf puppetlabs-stdlib-4.25.1.tar.gz'}}*Desired Behavior:*Extraction of downloaded modules should be about the same performance as system tar xzvf command. It might be at most 2x times slower then system command, but preferably should be about the same. Temporal solution:To install modules faster i propose to switch to Gnu implementation as a first choice. Al least until Minitar can be much faster.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title
Chris Suszynski created an issue
Puppet / PUP-9813
Performance of unpacking modules is extremely slow
Issue Type:
Bug
Affects Versions:
PUP 6.6.0, PUP 5.5.14, PUP 4.10.12
Assignee:
Unassigned
Components:
Modules
Created:
2019/07/03 3:53 PM
Priority:
Normal
Reporter:
Chris Suszynski
Original Estimate:
2 days
Remaining Estimate:
2 days
Puppet Version: any Puppet Server Version: any OS Name/Version: any Installing modules from Puppet Forge is extremelly slow. I have found a culprit. It is a Puppet::ModuleTool::Tar::Mini implementation. The unpack is 100x times slower then executing a {{tar xzvf }}system command. Steps to reproduce: Install a module from Puppet Forge and measure a time: time puppet module install puppetlabs-stdlib --version 4.25.1 Then execute: time bash -c 'curl https://forge.puppet.com/v3/files/puppetlabs-stdlib-4.25.1.tar.gz -o puppetlabs-stdlib-4.25.1.tar.gz && tar xzvf puppetlabs-stdlib-4.25.1.tar.gz' Desired Behavior: Extraction of downloaded modules should be about the same performance as system tar xzvf command. It might be at most 2x times slower then system command, but preferably should be about the same.
Jira (PDB-3729) Invalid JSON example for puppetdb.conf
Title: Message Title Adrian Walker commented on PDB-3729 Re: Invalid JSON example for puppetdb.conf This is still an issue with the latest version Windows PDK 1.10.0. https://puppet.com/download-puppet-enterprise-client-tools Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.192006.1495207428000.5880.1562194020138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1455) out::message messages don't print when format=json
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1455
out::message messages don't print when format=json
Change By:
Alex Dreyer
{{out:message}} calls should be delegated to the logger by the json outputter.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315274.1562178132000.5687.1562180408934%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Branan Riley updated an issue Puppet Task Runner / BOLT-1339 Build pe-bolt-server for redhatfips-7-x86_64 Change By: Branan Riley Sprint: Skeletor Kanban 20190703 , Skeletor Kanban 20190717 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309966.155865044.5661.1562179803066%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Branan Riley updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Branan Riley Sprint: Skeletor Kanban 20190619, Skeletor Kanban 20190703 , Skeletor Kanban 20190717 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.5640.1562179802862%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title Branan Riley updated an issue Puppet Task Runner / BOLT-1403 Prepare bolt-server for bolt_shim removal Change By: Branan Riley Sprint: Skeletor Kanban 20190619, Skeletor Kanban 20190703 , Skeletor Kanban 20190717 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312897.1560810439000.5665.1562179803086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Sean McDonald assigned an issue to Unassigned Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Sean McDonald Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.5594.1562179560117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1455) out::message messages don't print when format=json
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1455 out::message messages don't print when format=json Issue Type: Bug Assignee: Unassigned Created: 2019/07/03 11:22 AM Priority: Normal Reporter: 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 http
Jira (BOLT-1328) AWS inventory discovery integration
Title: Message Title Tom Beech commented on BOLT-1328 Re: AWS inventory discovery integration By default the aws-sdk-ec2 gem will return all instances, even if they're not running. Since non-running instaces do not have a public ip address or dns name, we probably want to filter these out. Another approach is to use the private ip address and dns name for any non-running instances, but I'm not sure how useful this is. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309594.1558455992000.5360.1562175240099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-1425
Document orchestrator client config options relevant to bolt
Change By:
Cas Donoghue
Release Notes Summary:
The {{job-poll-timeout}} and {{job-poll-interview}} options for the {{PCP}} transport are now configurable in bolt.yaml.
Release Notes:
Enhancement
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313858.1561422568000.5192.1562172180205%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1425 Document orchestrator client config options relevant to bolt Change By: Lucy Wyman Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313858.1561422568000.5170.1562171700221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title
Cyril Cordoui created an issue
Puppet Task Runner / BOLT-1454
Bolt is super slow
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/07/03 7:18 AM
Priority:
Normal
Reporter:
Cyril Cordoui
When running bolt on a couple of servers, tasks are super slow to execute. With a simple shell (or python) doing only an echo it takes more than 80 seconds to run on 100 servers, whereas other tools are nearly twenty times faster:
# ansible -f100 -oi inventory.ini -a '/bin/echo "{\"hello\":\"Tha world\"}"' srvs > /dev/null
ansible -f100 -oi inventory.ini -a srvs > /dev/null 14.38s user 14.77s system 366% cpu 7.964 total
# ansible -oi inventory.ini -a '/bin/echo "{\"hello\":\"Tha world\"}"' srvs > /dev/null
ansible -oi inventory.ini -a '/bin/echo "{\"hello\":\"Tha world\"}"' srv 11.70s user 9.47s system 144% cpu 14.626 total
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved to MODULES-9459* custom remote facts go to {{lib/puppet/remote_facts/TRANSPORT/NAME.rb}}, and can be deployed through any module* custom remote facts never get loaded on the server* puppet device and friends load all custom remote facts for the current transport* custom remote facts directly interact with the transport and can modify the facts hash at will (add/delete/modify)* custom remote facts need to ensure they do not interfere with each other{code:ruby}# lib/puppet/remote_facts/cisco_ios/ifspeeds.rbrequire 'puppet/resource_api/transport'require 'puppet_x/customer/site/cisco_ios_utility'Puppet::ResourceApi::Transport.register_fact(:cisco_ios) do |context, facts| facts[:ifspeeds] = PuppetX::Customer::Site::CiscoIosUtility.parse_ifspeeds(context.transport.run_command('show interfaces'))end{code}The example adds a custom fact for {{cisco_ios}} devices that parses out some information from the {{show interfaces}} command using a helper method from {{puppet_x/customer/site/cisco_ios_utility}}.Note how the transport name and fact implementation is passed into {{Puppet::ResourceApi::Transport.register_fact}} to be stored and used when required.Similar to https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport.rb#L43-L50 when collecting facts for a remote target, the Resource API needs to load all remote_facts files for that transport and remember the discovered fact blocks. Once that is done, the transport wrapper (https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport/wrapper.rb#L31-L35) can retrieve the actual facts from the device, and apply all the collected custom remote facts to the facts hash before returning the result: {code:ruby} def factscontext = Puppet::ResourceApi::PuppetContext.new(@schema)facts = @transport.facts(context)Puppet::ResourceApi::Transport.custom_facts(@schema.name).each do |custom_fact_block| custom_fact_block.call(context, facts)endfacts end{code}
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved to MODULES-9459* custom remote facts go to {{lib/puppet/remote_facts/TRANSPORT/NAME.rb}}, and can be deployed through any module* custom remote facts never get loaded on the server* puppet device and friends load all custom remote facts for the current transport* custom remote facts directly interact with the transport and can modify the facts hash at will (add/delete/modify)* custom remote facts need to ensure they do not interfere with each other{code:ruby}# lib/puppet/remote_facts/cisco_ios/ifspeeds.rbrequire 'puppet/resource_api/transport'require 'puppet_x/customer/site/cisco_ios_utility'Puppet::ResourceApi::Transport.register_fact(:cisco_ios) do |context, facts| facts[:ifspeeds] = PuppetX::Customer::Site::CiscoIosUtility.parse_ifspeeds(context.transport.run_command('show interfaces'))end{code} The example adds a custom fact for {{cisco_ios}} devices that parses out some information from the {{show interfaces}} command using a helper method from {{puppet_x/customer/site/cisco_ios_utility}}.Note how the transport name and fact implementation is passed into {{Puppet::ResourceApi::Transport.register_fact}} to be stored and used when required.Similar to https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport.rb#L43-L50 when collecting facts for a remote target, the Resource API needs to load all remote_facts files for that transport and remember the discovered fact blocks. Once that is done, the transport wrapper (https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport/wrapper.rb#L31-L35) can retrieve the actual facts from the device, and apply all the collected custom remote facts to the facts hash before returning the result:{code:ruby} def factscontext = Puppet::ResourceApi::PuppetContext.new(@schema)facts = @transport.facts(context)Puppet::ResourceApi::Transport.custom_facts(@schema.name).each do |custom_fact_block| custom_fact_block.call(context, facts)endfacts end{code}
Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1910 Mountpoint fact only shows tmpfs and physical mounts Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Fix Version/s: FACT 3.13.3 Fix Version/s: FACT 3.12.5 Fix Version/s: FACT 3.11.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1926 ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Fix Version/s: FACT 3.13.3 Fix Version/s: FACT 3.12.5 Fix Version/s: FACT 3.11.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Fix Version/s: FACT 3.13.3 Fix Version/s: FACT 3.12.5 Fix Version/s: FACT 3.11.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1916) facter fails to parse routing table
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1916 facter fails to parse routing table Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Fix Version/s: FACT 3.13.3 Fix Version/s: FACT 3.12.5 Fix Version/s: FACT 3.11.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1888) 'os.release' values not correct for VZ7
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1888 'os.release' values not correct for VZ7 Change By: Gheorghe Popescu Fix Version/s: FACT 3.11.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278967.1538669961000.4746.1562157180530%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved to MODULES-9459 * custom remote facts go to {{lib/puppet/remote_facts/TRANSPORT/NAME.rb}}, and can be deployed through any module* custom remote facts never get loaded on the server* puppet device and friends load all custom remote facts for the current transport* custom remote facts directly interact with the transport and can modify the facts hash at will (add/delete/modify)* custom remote facts need to ensure they do not interfere with each other{code:ruby}# lib/puppet/remote_facts/cisco_ios/ifspeeds.rbrequire 'puppet/resource_api/transport'require 'puppet_x/customer/site/cisco_ios_utility'Puppet::ResourceApi::Transport.register_fact(:cisco_ios) do |context, facts| facts[:ifspeeds] = PuppetX::Customer::Site::CiscoIosUtility.parse_ifspeeds(context.transport.run_command('show interfaces'))end{code}
Add Comment
This message was sent by Atlassi
Jira (FACT-1888) 'os.release' values not correct for VZ7
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1888 'os.release' values not correct for VZ7 Change By: Mihai Buzgau Fix Version/s: FACT 3.13.3 Fix Version/s: FACT 3.12.5 Fix Version/s: FACT 3.11.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278967.1538669961000.4736.1562157060415%40Atlassian.JIRA. For more options, visit https://groups.
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Change By: Gheorghe Popescu Release Notes Summary: The facter gemspec was pinned to ruby 2.1.7 which is causing gem installation errors.Changed the pinned version to 2.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307213.1556842594000.4666.1562156100169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Change By: Gheorghe Popescu 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307213.1556842594000.4662.1562156040227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Change By: Gheorghe Popescu Release Notes: Not 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307213.1556842594000.4658.1562155980176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1926 ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5 Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.4654.1562155740204%40Atl
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307213.1556842594000.4650.1562155620328%40Atlassian.JIRA. For more options, visit https://
Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1910 Mountpoint fact only shows tmpfs and physical mounts Change By: Gheorghe Popescu Fix Version/s: FACT 3.13.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299364.1552075723000.4645.1562155440248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-1910 Mountpoint fact only shows tmpfs and physical mounts Change By: Gheorghe Popescu Fix Version/s: FACT 3.12.z Fix Version/s: FACT 3.11.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299364.1552075723000.4642.1562155440233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1443) Add more demos for Bolt at Oscon
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1443 Add more demos for Bolt at Oscon 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314797.1562011067000.4626.1562153340047%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1398 I want to see what nodes are in an inventory group Change By: Lucy Wyman Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312528.1560553204000.4625.1562153280096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1933) Include more chassis IDs in facter
Title: Message Title George Mrejea assigned an issue to George Mrejea Facter / FACT-1933 Include more chassis IDs in facter Change By: George Mrejea Assignee: George Mrejea Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314629.1561725724000.4616.1562152860108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9649) Backport certname mismatch to 5.5.x and 6.0.x (PUP-8213)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9649 Backport certname mismatch to 5.5.x and 6.0.x (PUP-8213) Change By: Gheorghe Popescu Release Notes: Not 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305706.1555715621000.4588.1562152080164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1932) facter does not pick primary network interface properly on FreeBSD or OpenBSD
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1932 facter does not pick primary network interface properly on FreeBSD or OpenBSD Change By: Mihai Buzgau Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314338.1561645641000.4501.1562146680205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1932) facter does not pick primary network interface properly on FreeBSD or OpenBSD
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1932 facter does not pick primary network interface properly on FreeBSD or OpenBSD Change By: Mihai Buzgau Sprint: PR - Triage 2019-07-10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314338.1561645641000.4504.1562146680216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1933) Include more chassis IDs in facter
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1933 Include more chassis IDs in facter Change By: Mihai Buzgau Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314629.1561725724000.4494.1562146620330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1933) Include more chassis IDs in facter
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1933 Include more chassis IDs in facter Change By: Mihai Buzgau Sprint: PR - Triage 2019-07-10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314629.1561725724000.4496.1562146620338%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Sebastian Miclea Release Notes Summary: Fixed reading of crontabs using Puppet for Solaris 11. Now crontabs for all users are listed when running 'puppet resource cron' Release Notes: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.4413.1562143980228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.4406.1562143860183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.4401.1562143800418%40At
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.4393.1562143740293%40Atlassian.JIRA. For more options, visit ht
Jira (PUP-9706) Removing user on Solaris 11 with altered managehome
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9706 Removing user on Solaris 11 with altered managehome Change By: Gheorghe Popescu Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.y Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9688) User resource sets password on every puppet agent run (Windows)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9688 User resource sets password on every puppet agent run (Windows) Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306584.1556533521000.4383.1562143680261%40Atlassian.JIRA. For more opt
Jira (PUP-9649) Backport certname mismatch to 5.5.x and 6.0.x (PUP-8213)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9649 Backport certname mismatch to 5.5.x and 6.0.x (PUP-8213) Change By: Gheorghe Popescu Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 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. V
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs Change By: Gheorghe Popescu Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 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 Go
Jira (PUP-9639) Windows package resource does not remove trailing whitespace
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9639 Windows package resource does not remove trailing whitespace Change By: Gheorghe Popescu Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 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.co
Jira (PUP-9587) Serial execution with puppet device and ciscopuppet fails
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9587 Serial execution with puppet device and ciscopuppet fails Change By: Gheorghe Popescu Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.301168.1553201857000.4348.1562143380256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8664) rpm package provider is too specific
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-8664 rpm package provider is too specific Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246189.1524007177000.4343.1562143320167%40Atlassian.JIRA. For more options, visit https://groups.
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-6488 Gem provider should allow alternative gem command; should not rely on $PATH Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.140954.1468271833000.4333.1562143200291%40Atlassian.JIRA.
Jira (PUP-4930) Provide helpful error message when provider does not have instances defined
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-4930 Provide helpful error message when provider does not have instances defined Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.90662.1438016947000.4328.1562143140337%40Atlassian.JIRA. F
Jira (PUP-1082) pip provider should handle multiple pips/pythons
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-1082 pip provider should handle multiple pips/pythons Change By: Gheorghe Popescu Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21416.1387220789000.4320.1562143080825%40Atlassian.JIRA. For more options, visit http
