Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Sebastian updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Sebastian Attachment: profile.txt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Sebastian commented on PUP-8562 Re: File performance nearly twice as slow after update Alright i attached the output. We are indeed switching the environment via https://github.com/Zetten/puppet-hiera-enc. profile.txt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Sebastian commented on PUP-8562 Re: File performance nearly twice as slow after update R.I.Pienaar mentioned that you maybe expect the graphs or metrics to be wrong. That is not the case, the observed runtime nearly doubled. I can provide a full debug run in private if you want. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg commented on PUP-8240 Re: ERB and EPP templates handle CRLF line endings inconsistently That is so sad... Is the design really that the read is supposed to not preserve line endings? That is bizarre. The posix implementation does not remove CR chars (and I don't think it should) - that is why it works on non-windows. Seems more natural that there would be a special read that strips CR that logic not prepared to handle CRLF line endings should use. While we could change this for the EPP loader, all other modern loaders of code uses read - so an inline template doing the same thing would have the same issue. If we change the Posix read to strip CR then that is a serious performance issue (we need to read and replace them which would mean scanning the read manifest again. To me the proper fix is to modify the Windows implementation so that read is the same as read_preserve_line and that we add another read method read_posix_line_endings that should be used where reads on windows where supposed to get posix line endings (if that is needed anywhere at all?). Or... am I perhaps missing some Ruby quirk around CRLF line endings? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Glenn Sarti commented on PUP-8240 Re: ERB and EPP templates handle CRLF line endings inconsistently The ruby read method is a text reader so it tries to be "helpful" and normalises line endings as LF only. You can force ruby to read it as a binary file ( read(,"rb") ) in which case it reads in a byte stream and can then use the encoding to create the correct text string. A short google search on "file.read ruby CRLF" shows the pain As a side note this has the same behaviour on WRITING text files too (Text vs Binary file), which is a MAJOR pain point for me with Rubocop. When you rubocop auto correct, it doesn't respect the original line endings, so suddenly my files turn to CRLF. Even puppet-lint ran into this issue too, beaker-hostgenerator has a similar issue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title
Russell Knighton updated an issue
Puppet / PUP-8561
Augeas unable to handle escaped quotes within quotes
Change By:
Russell Knighton
*Puppet Version: 5.4.0* *Puppet Server Version: 5.2.0* *OS Name/Version: CentOS 7.4.1708*I am unable to find a way to set the "log_format" variable in nginx.conf using augeas. The problem seems to be the combination of quotes within quotes just doesn't seem to be possible.The desired value I am trying to set exactly is:{noformat}timed_combined '$remote_addr - $remote_user $http_x_unit_id [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_response_time $pipe'{noformat}Take careful note that I need to have the long single quoted string, but that this contains some double quoted strings. I have tried every possible combination I can think of for enclosing in single or double quoted strings in and for escaping then, but I have not successfully managed to set exactly what is required. I have tried so many different possible ways over the last 2 days that I am now convinced I haven't missed something and that this has to be a bug.To describe some of the more obvious steps I have tried, lets store the initial variables like as following:{code:puppet}#The log title:$log_title = 'timed_combined'#Set-up the needed log_format string:$log_format_str = '$remote_addr - $remote_user $http_x_unit_id [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_response_time $pipe'{code}The initial most logical combination of options that I have tried are (elaborated here to try and make it clear):*Attempt 1*Escape the double quotes within the substring, then pass the variable in augeas with escaped quotes:{code:puppet}# Create the combined string$use_log_format = regsubst("${log_title} '${log_format_str}'", '"', '\\"', 'G' ) augeas { 'set-up_log_format':context => "/files${conf_file}/http",changes => ["set log_format \"${use_log_format}\""]}{code}Produces:{noformat}-log_format main '$remote_addr - $remote_user [$time_local] "$request" '- '$status $body_bytes_sent "$http_referer" '- '"$http_user_agent" "$http_x_forwarded_for"';+log_format timed_combined '$remote_addr - $remote_user $http_x_unit_id [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" $request_time $upstream_response_time $pipe';{noformat}*Result:* Produces almost exactly what I want, but unfortunately the escapes have been passed through and retained. The result is confirmed when grep'ing the file:{noformat}root@devsvr2 ~]# grep log_format /etc/nginx/nginx.conflog_format timed_combined '$remote_addr - $remote_user $http_x_unit_id [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" $request_time $upstream_response_time $pipe';{noformat}Maybe I do not need the escapes? Let's try without...*Attempt 2*Don't escape the double quotes within t
Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title
Russell Knighton updated an issue
Puppet / PUP-8561
Augeas unable to handle escaped quotes within quotes
Change By:
Russell Knighton
*Puppet Version: 5.4.0* *Puppet Server Version: 5.2.0* *OS Name/Version: CentOS 7.4.1708*I am unable to find a way to set the "log_format" variable in nginx.conf using augeas. The problem seems to be the combination of quotes within quotes just doesn't seem to be possible.The desired value I am trying to set exactly is:{noformat}timed_combined '$remote_addr - $remote_user $http_x_unit_id [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_response_time $pipe'{noformat}Take careful note that I need to have the long single quoted string, but that this contains some double quoted strings. I have tried every possible combination I can think of for enclosing in single or double quoted strings in and for escaping then, but I have not successfully managed to set exactly what is required. I have tried so many different possible ways over the last 2 days that I am now convinced I haven't missed something and that this has to be a bug.To describe some of the more obvious steps I have tried, lets store the initial variables like as following:{code:puppet}#The log title:$log_title = 'timed_combined'#Set-up the needed log_format string:$log_format_str = '$remote_addr - $remote_user $http_x_unit_id [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_response_time $pipe'{code}The initial most logical combination of options that I have tried are (elaborated here to try and make it clear):*Attempt 1*Escape the double quotes within the substring, then pass the variable in augeas with escaped quotes:{code:puppet}# Create the combined string$use_log_format = regsubst("${log_title} '${log_format_str}'", '"', '\\"', 'G')augeas { 'set-up_log_format':context => "/files${conf_file}/http",changes => ["set log_format \"${use_log_format}\""]}{code}Produces:{noformat}-log_format main '$remote_addr - $remote_user [$time_local] "$request" '- '$status $body_bytes_sent "$http_referer" '- '"$http_user_agent" "$http_x_forwarded_for"';+log_format timed_combined '$remote_addr - $remote_user $http_x_unit_id [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" $request_time $upstream_response_time $pipe';{noformat}*Result:* Produces almost exactly what I want, but unfortunately the escapes have been passed through and retained. The result is confirmed when grep'ing the file:{noformat}root@devsvr2 ~]# grep log_format /etc/nginx/nginx.conflog_format timed_combined '$remote_addr - $remote_user $http_x_unit_id [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" $request_time $upstream_response_time $pipe';{noformat}Maybe I do not need the escapes? Let's try without...*Attempt 2*Don't escape the double quotes within the
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title
Daniel Mcilhagga created an issue
PuppetDB / PDB-3879
node-purge-ttl setting not working in 2017.3
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/03/21 6:38 AM
Priority:
Normal
Reporter:
Daniel Mcilhagga
In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will still searchable by using:
curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool
Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly. Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question.
Add Comment
Jira (PUP-8308) Streamline all package installation steps for puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8308 Streamline all package installation steps for puppet Change By: Kenn Hussey Fix Version/s: PUP 4.10.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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title
Daniel Mcilhagga updated an issue
PuppetDB / PDB-3879
node-purge-ttl setting not working in 2017.3
Change By:
Daniel Mcilhagga
In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will was still searchable by using:{code:java} curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool {code}Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly. Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question.
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
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen assigned an issue to Daniel Mcilhagga PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Charlie Sharpsteen Assignee: Daniel Mcilhagga Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen commented on PDB-3879 Re: node-purge-ttl setting not working in 2017.3 Daniel Mcilhagga The node-purge-ttl is only enforced during a PuppetDB garbage collection sweep. These can be resource intensive, so they don't happen continuously. By default, one happens at startup and then every 60 minutes afterwards, configurable via gc-interval in database.ini. Does the node disappear if you trigger a GC sweep by restarting pe-puppetdb? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-398) Lookup/Hiera spike
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-398 Lookup/Hiera spike Change By: Alex Dreyer I want to connect to a node based on configuration without knowing about the node in inventory a priori. Accept arbitrary targets, look up facts from puppetdb/discovery for them. use lookup to determine connection information based on the facts before connecting.I have a task with 'configuration params' for example ha-proxy socket location that may vary between nodes. I want to look up these parameters from hiera and pass them to run_task for a single target.We should explore how feasible it is use hiera for this by writing a function that can lookup a value in the context of a targets vars and facts and an arbiratry hiera.yaml file- How long does it take to loop over 200 with a more or less full complement of facter facts.- How much memory does it take to store a puppet scope an instance of the hierarchy for each target- What if any pal/lookup functions would make this easier. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-398) Lookup/Hiera spike
Title: Message Title Alex Dreyer commented on BOLT-398 Re: Lookup/Hiera spike Henrik Lindberg I'm guessing there is no invalidation of that cache since a catalog compile is in essence an atomic operation from a snapshot while during a plan the state of a node is likely to meaningfully change. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8558) Remove ability to enable non-strict mode in PMT
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8558 Remove ability to enable non-strict mode in PMT Change By: Jorie Tappa Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-371) Docs for installing Bolt from packages
Title: Message Title Kate Lopresti commented on BOLT-371 Re: Docs for installing Bolt from packages Here's a draft of install instructions: http://docs-preview.webteam.puppet.com/docs/bolt/dev/bolt_installing.html#ariaid-title3 username: puppet.access pswd: fork.left.extra Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8558) Remove ability to enable non-strict mode in PMT
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-8558 Remove ability to enable non-strict mode in PMT Change By: Jorie Tappa Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8558) Remove ability to enable non-strict mode in PMT
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-8558 Remove ability to enable non-strict mode in PMT Change By: Jorie Tappa Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-403) Tag new version (Bolt 0.17.2)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-403 Tag new version (Bolt 0.17.2) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/03/21 9:11 AM Due Date: 2018/03/21 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-03-21) First ensure that the component file in the bolt-vanagon project has the correct component ref. Then go into the 'release-new' hipchat room to make a tag ! tag bolt-vanagon at with Add Comment This message was sent by
Jira (BOLT-404) Build packages (Bolt 0.17.2)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-404 Build packages (Bolt 0.17.2) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/03/21 9:11 AM Due Date: 2018/03/21 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-03-21) You may need to manually kick off the bolt-vanagon pipeline https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_bolt-vanagon_init-van-int_suite-daily-master/ Manually smoke test release candidate packages Prepare release announcement Hand off to RE to ship in release-new hipchat room Add Comment
Jira (BOLT-405) Docs for bolt release (Bolt 0.17.2)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-405 Docs for bolt release (Bolt 0.17.2) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/03/21 9:11 AM Due Date: 2018/03/21 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-03-21) Release notes and docs changes for bolt 0.17.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-402) Do Jenkins gem release (Bolt 0.17.2)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-402 Do Jenkins gem release (Bolt 0.17.2) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/03/21 9:11 AM Due Date: 2018/03/21 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-03-21) Manually kick off Jenkins gem release pipeline for bolt gem: https://cinext-jenkinsmaster-sre-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt_init-multijob_master/ Check the 'PUBLIC' box and enter release version Add Comment
Jira (BOLT-400) Bolt 0.17.2 2018-03-21 Release
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-400 Bolt 0.17.2 2018-03-21 Release Issue Type: Task Assignee: Lucy Wyman Created: 2018/03/21 9:11 AM Priority: Normal Reporter: Lucy Wyman Bolt 0.17.2 2018-03-21 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-401) Reconcile git commits, JIRA tickets, and versions (Bolt 0.17.2)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-401 Reconcile git commits, JIRA tickets, and versions (Bolt 0.17.2) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/03/21 9:11 AM Due Date: 2018/03/20 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-03-21) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-400) Bolt 0.18.0 2018-03-21 Release
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-400 Bolt 0.18.0 2018-03-21 Release Change By: Lucy Wyman Summary: Bolt 0. 17 18 . 2 0 2018-03-21 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-404) Build packages (Bolt 0.18.0)
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-404 Build packages (Bolt 0.18.0) Change By: Lucy Wyman Summary: Build packages (Bolt 0. 17 18 . 2 0 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-401) Reconcile git commits, JIRA tickets, and versions (Bolt 0.18.0)
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-401 Reconcile git commits, JIRA tickets, and versions (Bolt 0.18.0) Change By: Lucy Wyman Summary: Reconcile git commits, JIRA tickets, and versions (Bolt 0. 17 18 . 2 0 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-402) Do Jenkins gem release (Bolt 0.18.0)
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-402 Do Jenkins gem release (Bolt 0.18.0) Change By: Lucy Wyman Summary: Do Jenkins gem release (Bolt 0. 17 18 . 2 0 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-403) Tag new version (Bolt 0.18.0)
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-403 Tag new version (Bolt 0.18.0) Change By: Lucy Wyman Summary: Tag new version (Bolt 0. 17 18 . 2 0 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-405) Docs for bolt release (Bolt 0.18.0)
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-405 Docs for bolt release (Bolt 0.18.0) Change By: Lucy Wyman Summary: Docs for bolt release (Bolt 0. 17 18 . 2 0 ) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8504 Emit deprecation warning for ruby 2.1 and 2.2 Change By: Josh Cooper Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-297) Plan Output
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-297 Plan Output Change By: Yasmin Rajabi Attachment: IMG_0876.jpg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1831) FACTER to return System Locale
Title: Message Title Erwin Hom commented on FACT-1831 Re: FACTER to return System Locale I'm okay with closing this for now. It's possible to configure a system with a system locale as well as a user locale of en-US (or xx-XX). I have been in computer labs where machines were misconfigured for this setting. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8504) Emit deprecation warning for ruby 2.1 and 2.2
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8504 Emit deprecation warning for ruby 2.1 and 2.2 Change By: Maggie Dreyer Release Notes Summary: Ruby versions less than 2.3 are now deprecated and will be removed in Puppet 6. Warnings will be issued when they are used. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-406) WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2
Title: Message Title Ethan Brown created an issue Puppet Task Runner / BOLT-406 WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2 Issue Type: New Feature Affects Versions: BOLT 0.17.0 Assignee: Unassigned Components: WinRM Created: 2018/03/21 10:29 AM Priority: Normal Reporter: Ethan Brown Since it is common to want to return JSON data from tasks, and since it can be problematic to build inline JSON given escaping / formatting rules, there should be a facility always available for task authors to produce JSON from PowerShell. Normally this can be done using PowerShell 3 and above using the ConvertTo-Json and ConvertFrom-Json cmdlets. However, Bolt and PE tasks explicitly support PS2+ so for PS2, a polyfill is necessary to make these cmdlets available. Bolt code already does something similar for its own purposes at https://github.com/puppetlabs/bolt/blob/a53f2f872a82b2a5ba6a4d8961243f2cb7c1ce1f/lib/bolt/transport/winrm/connection.rb#L205-L380 as does the implementation of PE tasks. These facilities just need to be surfaced to end users. Otherwise, if users wish to write PowerShell tasks that support all PowerShell versions, they must build inline JSON strings.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title James Ralston created an issue Puppet / PUP-8566 "puppet config print" needs --quiet option to disable new (default) verbosity Issue Type: New Feature Affects Versions: PUP 5.5.0 Assignee: Unassigned Created: 2018/03/21 10:47 AM Priority: Minor Reporter: James Ralston While the enhancements implemented in PUP-2868 are arguably good, because they make puppet config print less confusing for novice users, making puppet config print unconditionally emit messages to stderr is undesirable, as the extraneous stderr messages can confuse programs which are using puppet config print non-interactively and are parsing the output. Case in point: I have multiple cron jobs that use puppet config print to obtain Puppet configuration information. After upgrading to 5.5.0, I am now receiving messages like this on an hourly basis: From: "(Cron Daemon)" To: r...@example.org Subject: Cron run-parts /etc/cron.hourly Date: Wed, 21 Mar 2018 13:01:01 -0400
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity +1, this will break a lot of things Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-381) Move to Ruby 2.3 as minimum supported version
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-381 Move to Ruby 2.3 as minimum supported version Change By: Kate Lopresti Labels: breaking docs-reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-381) Move to Ruby 2.3 as minimum supported version
Title: Message Title Kate Lopresti commented on BOLT-381 Re: Move to Ruby 2.3 as minimum supported version Added to release notes: http://docs-preview.webteam.puppet.com/docs/bolt/dev/new_features.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-389) Support explicit WinRM SSL certificate verification and ignoring
Title: Message Title Kate Lopresti commented on BOLT-389 Re: Support explicit WinRM SSL certificate verification and ignoring Added to release notes: http://docs-preview.webteam.puppet.com/docs/bolt/dev/new_features.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-388) The all group includes 'localhost' even if it is not in the inventory.
Title: Message Title Kate Lopresti commented on BOLT-388 Re: The all group includes 'localhost' even if it is not in the inventory. Added to release notes: http://docs-preview.webteam.puppet.com/docs/bolt/dev/resolved_issues.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-131) Simplify tasks by sharing boilerplate code
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-131 Simplify tasks by sharing boilerplate code Change By: Alex Dreyer Summary: Simplify tasks for repeatable by sharing boilerplate code and importing code Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-131) Simplify tasks by sharing boilerplate code
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-131 Simplify tasks by sharing boilerplate code Change By: Alex Dreyer All task code must be in a single file. This means task authors quickly end up copy/pasting boilerplate code between their tasks (parsing input, generating output, handling errors) . As a user I would like a better way to reuse parts of my codes in my tasks so that I can share centralizing this boilerplate code with other tasks . Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity James Ralston fwiw I tend to prefer puppet agent --configprint foo as then you know what your actual thing will use not whats in a particular section and luckily it seems that has not been affected by this Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-131) Simplify tasks for repeatable code and importing code
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-131 Simplify tasks for repeatable code and importing code Change By: Alex Dreyer Summary: Simplify tasks by sharing boilerplate for repeatable code and importing code Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-133) I don't want to write the same boilerplate code in each task
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-133 I don't want to write the same boilerplate code in each task Change By: Alex Dreyer Writing tasks in most languages requires a lot of boilerplate code. There should be a way to reuse this code between tasks and share boilerplate libraries for different runtime environments.- parsing input- generating result output- handling errors.- polyfills for interpreter versions or installed libraries on the target Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-406) WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2
Title: Message Title Alex Dreyer commented on BOLT-406 Re: WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2 If we build this into bolt it needs to be part of the task spec first. Tasks that rely on this will be degraded when run by older task runners. I have some questions about whether problems like this should be solved as one offs for every language or if we should focus on BOLT-133 to add general handling of boilerplate code to the task spec. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4678) Enable yumrepo priority attribute to support lower priority than 99
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-4678 Enable yumrepo priority attribute to support lower priority than 99 Merged to the 5.5.x branch in c33cd640e0. Change By: Jacob Helwig Release Notes Summary: The yumrepo type no longer limits priority values to 1-99, and now accepts any integer (positive or negative). This now matches yum's behavior on determining valid priority values. Release Notes: New Feature Fix Version/s: PUP 5.5.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-374) Update bolt-vanagon to ship latest platforms
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-374 Update bolt-vanagon to ship latest platforms Change By: Kate Lopresti Labels: docs-reviewed 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-374) Update bolt-vanagon to ship latest platforms
Title: Message Title Kate Lopresti commented on BOLT-374 Re: Update bolt-vanagon to ship latest platforms Added to release notes: http://docs-preview.webteam.puppet.com/docs/bolt/dev/new_features.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title James Ralston commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity R.I.Pienaar advice appreciated, but alas, in this case, I must use puppet config print, because I'm specifically looking for reportdir, which is defined in the [master] section. So using puppet agent --configprint will give me incorrect results: $ puppet agent --configprint reportdir /opt/puppetlabs/puppet/cache/reports $ puppet config print --color=false --section master reportdir 2>/dev/null /opt/puppetlabs/server/data/puppetserver/reports For now, I've updated my scripts to redirect stderr to /dev/null, but this is just hiding the problem. Add Comment This message was sent by Atlassia
Jira (BOLT-398) Lookup/Hiera spike
Title: Message Title Henrik Lindberg commented on BOLT-398 Re: Lookup/Hiera spike Yes - there is no cache invalidation/eviction except if the input used to form the hierarchy changed. For regular compiles the "change" is really if a variable goes from non existing to being assigned since all variables are immutable. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title Henrik Lindberg commented on PUP-8561 Re: Augeas unable to handle escaped quotes within quotes Ping David Lutterkort Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-134) I want to use utility functions that can be used across my modules
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-134 I want to use utility functions that can be used across my modules Change By: Alex Dreyer Summary: I want to write use utility functions that can be used across my modules Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity Master, apply etc all have —configprint and all does the right thing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg commented on PUP-8240 Re: ERB and EPP templates handle CRLF line endings inconsistently So... FileSystem.read on my machine (mac OSx) returns text files with CRLF intact (as shown by my experiment in this thread) - i.e. no "helpful" ruby mapping. Is it only "helpful" on Windows? If so, then our implementation of the Window's version of FileSystem.read is wrong. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper commented on PUP-8562 Re: File performance nearly twice as slow after update Ah, my mistake, I thought you said the issues was introduced in 5.5.0, but I see you said it's 5.4.0. One thing that comes to mind is the fix for PUP-7451, whereby if the server (or load-balancer) returns an HTTP 429 or 503 response with a Retry-After header then the agent will backoff and sleep. The corresponding server change was made in SERVER-1767. If that's the case, then I would expect to see warning messages in the agent like "Received a response from the server. Sleeping for ... seconds". Another possibility is when that if you are running FIPS enabled hosts, then puppet will switch the default file checksum type from md5 to sha256. I wouldn't expect the file time to double though. /cc Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-406) WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-406 WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2 Change By: Ethan Brown Since it is common to want to return JSON data from tasks, and since it can be problematic to build inline JSON given escaping / formatting rules, there should be a facility always available for task authors to produce JSON from PowerShell. Normally this can be done using PowerShell 3 and above using the [ConvertTo-Json|https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/convertto-json?view=powershell-3.0] and [ConvertFrom-Json|https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/convertfrom-json?view=powershell-3.0] cmdlets. However, Bolt and PE tasks explicitly support PS2+ so for PS2, a polyfill is necessary to make these cmdlets available. Bolt code already does something similar for its own purposes at [https://github.com/puppetlabs/bolt/blob/a53f2f872a82b2a5ba6a4d8961243f2cb7c1ce1f/lib/bolt/transport/winrm/connection.rb#L205-L380] as does the implementation of PE tasks at [https://github . com/puppetlabs/pxp-agent/blob/33a76e0080e61b353dff9fbf17e4dbede44bd09b/exe/PowershellShim-Helper.ps1] . These facilities just need to be surfaced to end users. Otherwise, if users wish to write PowerShell tasks that support all PowerShell versions, they must build inline JSON strings. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-406) WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2
Title: Message Title Ethan Brown commented on BOLT-406 Re: WinRM connector should make ConvertTo-Json / ConvertFrom-Json available in PS2 I would generally advocate for doing the simple thing here that solves this specific problem, as this would primarily involve sharing code with users that is already used / implemented in Bolt / pxp-agent (for the very same reason - JSON support in PS2). For sure the generic reusable code idea has merit, but it's also a lot more work / effort to implement than I think is needed for this one narrowly scoped scenario. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-133) I don't want to write the same boilerplate code in each task
Title: Message Title Ethan Brown commented on BOLT-133 Re: I don't want to write the same boilerplate code in each task One thing worth considering is the implicit coupling that exists between shared helper libraries and the version of Bolt / PE. If there is a strong dependency relationship between the helpers and the version of the other tooling needed, then having independently versioned pieces creates additional maintenance burden by increasing the number of moving parts. But if there is no such dependency, having a separately versioned set of reusable helpers that can be referenced in the task results in greater flexibility. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7269) SPIKE: split non-core functionality out of puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7269 SPIKE: split non-core functionality out of puppet Change By: Josh Cooper Research path forward on splitting non-core functionality out of PuppetRequirements:- batteries includedImplications:- need a way to compose artifacts that aren't currently supported by vanagon (ie modules)- consider code loading implications, versioning across separate components - community support / maintenance of things we break out of puppet Discussion: https://groups.google.com/forum/#!topic/puppet-dev/lygaJ64Gw08 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit ht
Jira (BOLT-133) I don't want to write the same boilerplate code in each task
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-133
I don't want to write the same boilerplate code in each task
Change By:
Alex Dreyer
Writing tasks in most languages requires a lot of boilerplate code. There should be a way to reuse this code between tasks and share boilerplate libraries for different runtime environments.- parsing input- generating result output- handling errors.- polyfills for interpreter versions or installed libraries on the target Possible solution "file-dependencies" in task metadata:{ "file-dependencies": [ "boltlib/files/rb_boilerplate.rb", "mymodule/tasks/]}
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://gr
Jira (BOLT-133) I don't want to write the same boilerplate code in each task
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-133
I don't want to write the same boilerplate code in each task
Change By:
Alex Dreyer
Writing tasks in most languages requires a lot of boilerplate code. There should be a way to reuse this code between tasks and share boilerplate libraries for different runtime environments.- parsing input- generating result output- handling errors.- polyfills for interpreter versions or installed libraries on the targetPossible solution "file-dependencies" in task metadata:{ noformat}{ "file-dependencies": [ "boltlib/files/rb_boilerplate.rb", " myboilerplate/files/ruby_code/" " mymodule/tasks/ core_task.rb", ]} {noformat}All files and directories would then get copied to the target into the same tmpdir as the task executable. This should make the code accessible from most runtimes.
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 "Pupp
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Kate Lopresti commented on BOLT-260 Re: Should be easier to pass typed data on CLI Added to release notes: http://docs-preview.webteam.puppet.com/docs/bolt/dev/new_features.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-260) Should be easier to pass typed data on CLI
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass typed data on CLI Change By: Kate Lopresti Labels: docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8567) Extract augeas type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8567 Extract augeas type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:36 PM Priority: Normal Reporter: Josh Cooper Extract augeas type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8568) Extract cron type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8568 Extract cron type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:36 PM Priority: Normal Reporter: Josh Cooper Extract cron type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8570) Extract k5login type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8570 Extract k5login type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:37 PM Priority: Normal Reporter: Josh Cooper Extract k5login type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8569) Extract host type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8569 Extract host type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:37 PM Priority: Normal Reporter: Josh Cooper Extract host type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8571) Extract mailalias type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8571 Extract mailalias type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:37 PM Priority: Normal Reporter: Josh Cooper Extract mailalias type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8572) Extract maillist type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8572 Extract maillist type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:37 PM Priority: Normal Reporter: Josh Cooper Extract maillist type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8573) Extract macdslocal type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8573 Extract macdslocal type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:38 PM Priority: Normal Reporter: Josh Cooper Extract macdslocal type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8416) Remove old acceptance code that now lives in beaker-puppet
Title: Message Title Kris Bosland commented on PUP-8416 Re: Remove old acceptance code that now lives in beaker-puppet Merged to 4.10.x at https://github.com/puppetlabs/puppet/commit/aff25785d92678241a3f9b09b21e98966675e0eb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8575) Extract network_device type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8575 Extract network_device type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:38 PM Priority: Normal Reporter: Josh Cooper Extract network_device type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8574) Extract mount type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8574 Extract mount type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:38 PM Priority: Normal Reporter: Josh Cooper Extract mount type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8576) Extract scheduled_task type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8576 Extract scheduled_task type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:39 PM Priority: Normal Reporter: Josh Cooper Extract scheduled_task type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8577) Extract selinux type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8577 Extract selinux type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:39 PM Priority: Normal Reporter: Josh Cooper Extract selinux type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8578) Extract sshkeys type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8578 Extract sshkeys type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:39 PM Priority: Normal Reporter: Josh Cooper Extract sshkeys type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8579) Extract yumrepo type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8579 Extract yumrepo type/provider into a module Change By: Josh Cooper Summary: Extract augeas yumrepo type/provider into a module Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8579) Extract augeas type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8579 Extract augeas type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:40 PM Priority: Normal Reporter: Josh Cooper Extract yumrepo type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8580) Extract zfs type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8580 Extract zfs type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:40 PM Priority: Normal Reporter: Josh Cooper Extract zfs type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8581) Extract zpool type/provider into a module
Title: Message Title Josh Cooper created an issue Puppet / PUP-8581 Extract zpool type/provider into a module Issue Type: Task Assignee: Unassigned Created: 2018/03/21 1:41 PM Priority: Normal Reporter: Josh Cooper Extract zpool type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-3661) Extract zpool type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3661 Extract zpool type/provider into a module Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3661) Extract zpool type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3661 Extract zpool type/provider into a module Change By: Josh Cooper Summary: Remove Extract zpool from puppet core and type/provider into a module Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1077) Extract nagios type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1077 Extract nagios type/provider into a module Change By: Josh Cooper Summary: Move Nagios types and supporting from core to Extract nagios type/provider into a module Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1077) Extract nagios type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1077 Extract nagios type/provider into a module Change By: Josh Cooper Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1077) Extract nagios type/provider into a module
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-1077 Extract nagios type/provider into a module Change By: Josh Cooper Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Josh Cooper commented on PUP-3922 Re: Preserve modulepath structure during pluginsync I no longer think this issue is a blocker for removing non-core types and providers. But there are still valid reasons for preserving module namespace during pluginsync, so I'll keep this issue open, but remove it from the epic. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8581) Extract zone type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8581 Extract zone type/provider into a module Change By: Josh Cooper Extract zpool zone type/provider into a module per https://github.com/puppetlabs/puppet-specifications and https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8581) Extract zone type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8581 Extract zone type/provider into a module Change By: Josh Cooper Summary: Extract zpool zone type/provider into a module Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8582) Add vendor_modules to autoloader search path
Title: Message Title Josh Cooper created an issue Puppet / PUP-8582 Add vendor_modules to autoloader search path Issue Type: Task Assignee: Unassigned Created: 2018/03/21 2:01 PM Priority: Normal Reporter: Josh Cooper Update the autoloader to search the vendor_modules directory when loading module content. The directory should have the least precedence (per-environment modulepath, global modulepath, and pluginsync libdir) should have higher priority. puppetserver: installing an updated module should override vendor_modules (from the puppet-agent package on the local host). puppet agent: pluginsynced modules should override vendor_modules puppet apply/resource: locally installed modules should override vendor_modules Add Comment
Jira (BOLT-135) I want to execute different versions of the task file on different platforms
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Branan Riley updated an issue Facter / FACT-198 Rename uniqueid hostid Change By: Branan Riley Labels: breaking redmine triaged Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Branan Riley updated an issue Facter / FACT-198 Rename uniqueid hostid Change By: Branan Riley Labels: redmine triaged Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-454) virtual on OpenVZ returns value openvz instead of openvzve
Title: Message Title Branan Riley updated an issue Facter / FACT-454 virtual on OpenVZ returns value openvz instead of openvzve Change By: Branan Riley Labels: maintenance redmine triaged virtualization Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Issue Type: Bug Assignee: Unassigned Created: 2018/03/21 2:35 PM Priority: Normal Reporter: Alex Dreyer clavelin:aggregate adreyer$ bundle exec bolt plan show aggregate::count bundler: failed to load command: bolt (/Users/adreyer/src/bolt/.bundle/ruby/2.3.0/bin/bolt) Puppet::PreformattedError: Evaluation Error: Resource type not found: TargetSpec (file: /Users/adreyer/src/bolt/modules/aggregate/plans/count.pp, line: 5, column: 3)
Jira (FACT-478) add a fact with the default temp dir.
Title: Message Title Branan Riley updated an issue Facter / FACT-478 add a fact with the default temp dir. Change By: Branan Riley Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-478) add a fact with the default temp dir.
Title: Message Title Branan Riley updated an issue Facter / FACT-478 add a fact with the default temp dir. Change By: Branan Riley Labels: triaged Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms
Title: Message Title Branan Riley updated an issue Facter / FACT-620 windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms Change By: Branan Riley Fix Version/s: FACT 4.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Branan Riley updated an issue Facter / FACT-198 Rename uniqueid hostid Change By: Branan Riley Fix Version/s: FACT 4.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
