Jira (PUP-8414) license cube
Title: Message Title license cube created an issue Puppet / PUP-8414 license cube Issue Type: Bug Assignee: Unassigned Attachments: image.png, image.png, image.png Created: 2018/02/01 8:58 PM Priority: Normal Reporter: license cube http://www.licensecube.com/ is the #1 license providing company –offers massive assortment of licenses including c panel, Plesk, direct admin and more for fast loading. Buy your need one from various selections. Add Comment
Jira (PUP-1289) Ability to manage a windows service's user account and password
Title: Message Title Nate McCurdy commented on PUP-1289 Re: Ability to manage a windows service's user account and password This would be a great feature because it would more easily allow people to configure the puppet agent service and what user/password/domain it runs with. I run into this all the time and usually fall back to setting those things at agent install time. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8413) Show refresh commands that the service provider would issue during "noop" run
Title: Message Title Johnson Earls created an issue Puppet / PUP-8413 Show refresh commands that the service provider would issue during "noop" run Issue Type: New Feature Assignee: Unassigned Components: Types and Providers Created: 2018/02/01 5:57 PM Priority: Normal Reporter: Johnson Earls I recently made a change to a service resource definition to modify the restart command used by that service. I wanted to verify this change without actually affecting any running system, so (with the change deployed to a testing Puppet environment), i went to a non-production system and ran puppet agent -t --noop --debug. That run proceeded to show me the commands the service provider used to get the status of the services, but did not show me the commands it would have run to process the refresh event that came to it. Please see if it's possible to have the service provider display the full set of commands it would issue even during a --noop puppet run. Add Comment
Jira (PUP-5475) Windows Service provider should use something better than net.exe - perhaps direct FFI access
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5475 Windows Service provider should use something better than net.exe - perhaps direct FFI access Change By: Ethan Brown Team: Platform OS Windows Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title Owen Rodabaugh commented on PUP-6702 Re: Windows service in Paused state cannot be managed Does this ticket need to be split into one about the SSL issue and another about the paused state? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Johnson Earls created an issue Puppet / PUP-8412 In the puppet report, provide details of which provider was used for each resource Issue Type: New Feature Assignee: Unassigned Components: Types and Providers Created: 2018/02/01 4:41 PM Priority: Normal Reporter: Johnson Earls Caveat: this functionality may already exist, since I'm still stuck in the iron age at version 4.2.3. I recently needed to identify exactly which provider was being used for the service resources on one of my agents. I checked the catalog, but did not expect to see it there. I was hoping to see it in the report, but it was not there either. It also was not in the --debug output of the puppet agent. I ended up having to browse the ruby code for the various service providers and identify which one was default for my OS. Would it be possible to improve the report generated by the puppet agent to include which provider was used for each resource? Add Comment
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Change By: Owen Rodabaugh Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add action for deleting settings from puppet config
Title: Message Title Eric Delaney commented on PUP-3020 Re: Add action for deleting settings from puppet config new messages: Deleted setting from 'master' with value: 'wow = thing' Warning: No setting found in configuration file for section user setting name wow ✔ ~/work/my_repos/puppet [task/master/PUP-3020/add_config_delete_action L|⚑ 1] 14:35 $ cat /Users/eric.delaney/.puppetlabs/etc/puppet/puppet.conf [main] wow = thing crazy = thing [master] wow = thing ✔ ~/work/my_repos/puppet [task/master/PUP-3020/add_config_delete_action L|⚑ 1] 14:35 $ bundle exec puppet config set crazy thing --section user
Jira (PUP-8114) Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Title: Message Title
Jacob Helwig updated an issue
Puppet / PUP-8114
Service provider 'redhat' does not correctly detect enabled state of 'boot.*' services on SLES 11.
Change By:
Jacob Helwig
Acceptance Criteria:
The `redhat` service provider accurately detects the enabled state of considers a ` service with {{chkconfig}} status of "{{B}}" to be enabled. Eg:{code}$ chkconfig boot. *` service on SLES 11 kdumpboot . kdump B{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Kris Bosland commented on PUP-7630 Re: "Successful" puppet agent reports hide provider errors Merged into master at https://github.com/puppetlabs/puppet/commit/3aed5c03e9a4470798836892cc10c60e7683c298 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3826) (docs) Fix Markdown, formatting, and ToC issues.
Title: Message Title Garrett Guillotte updated an issue PuppetDB / PDB-3826 (docs) Fix Markdown, formatting, and ToC issues. Change By: Garrett Guillotte Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3826) (docs) Fix Markdown, formatting, and ToC issues.
Title: Message Title Garrett Guillotte updated an issue PuppetDB / PDB-3826 (docs) Fix Markdown, formatting, and ToC issues. Change By: Garrett Guillotte Reporter: gepetto-bot Garrett Guillotte Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3826) (docs) Fix Markdown, formatting, and ToC issues.
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3826 (docs) Fix Markdown, formatting, and ToC issues. Issue Type: Bug Assignee: Unassigned Created: 2018/02/01 12:33 PM Priority: Normal Reporter: gepetto-bot Several parts of the documentation have invalid or inconsistent Markdown formatting, broken links, or errors in heading levels or heading contents. This results in issues when rendering these docs on GitHub or puppet.com/docs. This PR resolves these issues. It does not attempt to validate, resolve issues with, or update any of the surrounding content. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Eric Delaney commented on PUP-3321 Re: config set adds a preceding newline to value if previous value was empty merged to master at https://github.com/puppetlabs/puppet/commit/9d431994d31c349f170f67c9458c280833b3416d Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8378 Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8231) Group resource - unable to add new member if there is existing IIS AppPool\user
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8231 Group resource - unable to add new member if there is existing IIS AppPool\user Change By: Craig Gomes Sprint: Windows Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8378 Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Change By: Josh Cooper Acceptance Criteria: It should be possible to generate types for the java_ks module, and compile a manifest where the java_ks title contains multiple namevars (and whose regex is not the default one). See https://github.com/puppetlabs/puppetlabs-java_ks/blob/master/lib/puppet/type/java_ks.rb#L184-L207 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Change By: Josh Cooper QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Josh Cooper Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-318) I want to refer to inventory groups as targets
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-318 I want to refer to inventory groups as targets Change By: Yasmin Rajabi Sprint: Bolt Ready for Grooming Discover/Design Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-307) Standardize success and failure for plans
Title: Message Title Yasmin Rajabi assigned an issue to Michal Ruzicka Puppet Task Runner / BOLT-307 Standardize success and failure for plans Change By: Yasmin Rajabi Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Thomas Hallgren commented on PUP-8411 Re: types generated by puppet generate types with title patterns are handled the wrong way Merged to 4.10.x at 44e1a85. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8410) It is difficult to return a hash from a plan, or function
Title: Message Title
Alex Dreyer commented on PUP-8410
Re: It is difficult to return a hash from a plan, or function
Why is the string case harder to parse than the name/implicit string case?
return { title : }
return { 'title' : }
return { key => val }
Why can't this be parse similarly?
return { 'key' => val }
Add Comment
This message was sent by Atlassian JIRA
Jira (BOLT-253) Set up containers for ssh unit and integration tests
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-253 Set up containers for ssh unit and integration tests Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Change By: Henrik Lindberg Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.5 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-253) Set up containers for ssh unit and integration tests
Title: Message Title Michal Ruzicka commented on BOLT-253 Re: Set up containers for ssh unit and integration tests Note that we do run ssh unit tests in travis. We ssh back to localhost, i.e. to the travis box running the tests. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7939) I18N japanese translation does not contain leading spaces
Title: Message Title
Eric Delaney commented on PUP-7939
Re: I18N japanese translation does not contain leading spaces
Erwin Hom Yes, I believe the spaces were original included in the string to enable readability of the messages. Originally most of them where just HERE doc's like this:
description <<-'EOT'
Updates values in the `puppet.conf` configuration file.
EOT
Some, but not all have been switched over to multiple lines like this:
def multiline
message = []
message << _("Could not %{action} module '%{module_name}' (%{version})") % { action: @action, module_name: @requested_name, version: vstring }
message << _(" No version of '%{module_name}' can satisfy all dependencies") % { module_name: @requested_name }
#TRANSLATORS `puppet module %{action} --ignore-dependencies` is a command line and should not be translated
Jira (BOLT-253) Set up containers for ssh unit and integration tests
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-253 Set up containers for ssh unit and integration tests Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8411) types generated by puppet generate types with title patterns are handled the wrong way
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8411 types generated by puppet generate types with title patterns are handled the wrong way Issue Type: Bug Assignee: Unassigned Created: 2018/02/01 2:00 AM Fix Versions: PUP 4.10.11 Priority: Normal Reporter: Henrik Lindberg If a resource type has title patterns, it would end up using the default regular _expression_ instead of the specified pattern. For most resource types this is the default and no problem would be noticed. We found this problem in code review as there was a typo in the implementation. Add Comment
Jira (PUP-8235) When running with --tasks Scope.to_s should shorten paths to modules
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8235
When running with --tasks Scope.to_s should shorten paths to modules
Change By:
Henrik Lindberg
Release Notes Summary:
When puppet is used for scripting with Bolt (tasks and plans), logging output will now use shortened paths inside of the {{Scope()}} identifier found in every logged message. Instead of showing the full path, a path to a module on the module path is shown as {{/name/.pp}} or the same using {{}} for a path to a .pp file in an environment.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8235) When running with --tasks Scope.to_s should shorten paths to modules
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8235 When running with --tasks Scope.to_s should shorten paths to modules Change By: Henrik Lindberg Fix Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6977) Add a module_directory function that returns a module's directory path
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6977
Add a module_directory function that returns a module's directory path
Change By:
Henrik Lindberg
Release Notes Summary:
The function {{ find_module module_directory }} has been added - it finds a module by name and returns the file system path to its root directory, or {{undef}} if module is not found on the modulepath.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6977) Add a module_directory function that returns a module's directory path
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6977
Add a module_directory function that returns a module's directory path
Change By:
Henrik Lindberg
Add a function {{ find_module module_directory (names)}} that returns the path of the first found module on the module path, or undef if none of the given names is a module on the modulepath.ORIGINALIt would be very useful for calling generator scripts in the files directory of the current module if the path to the current module (in particular which of the entries in module_path is currently used) would be supplied as a compiler variable similar to module_name.Currently it is only possible to hard-code that component of the path as far as I can tell, e.g.{code}${settings::environmentpath}/${environment}/modules/module_name/files/gen_script.sh{code}This works fine for most cases but we are currently using several folders in the environment.conf's module_path, one for local modules that abstract away stuff for specific hosts, one for shared modules between different customer's puppet masters and our own and now one for shared modules between our old and new environments (rewrite of our internal modules to support multiple Linux distributions and follow more best practices but not all hosts are migrated to it yet).
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-6977) Add a module_directory function that returns a module's directory path
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6977 Add a module_directory function that returns a module's directory path Change By: Henrik Lindberg Summary: Add a find_module module_directory function that returns a module's directory path Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7792) argument type mismatch message could be clearer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7792 argument type mismatch message could be clearer Change By: Henrik Lindberg Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8410) It is difficult to return a hash from a plan, or function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8410 It is difficult to return a hash from a plan, or function Change By: Henrik Lindberg Summary: It is difficult to return a hash from a plan , or function Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8410) It is difficult to return a hash from a plan
Title: Message Title Henrik Lindberg commented on PUP-8410 Re: It is difficult to return a hash from a plan Note that there is nothing specific to plans or return in this issue, the same problem exists for all functions that may be called without parentheses, and for code anywhere (not just in plans). Unfortunately, not much we can do about that - the root cause is the ambiguity caused by the resource expressions in the puppet language that the parsing technology we use cannot solve as it does not have lookahead that reaches more than one token. I don't see us changing the resource expressions or changing parser technology any time soon. What could be possible is to make return a keyword (now it is just a function like all others). When doing so, all other functions that may be called without parentheses (include, require, fail, info, notice, next, break, etc.) should then probably also receive the same treatment. The problem with new keywords is that they must then be handled in multiple other places as if they were just a regular "name" tokens. This means cost of fixing is relatively high and somewhat risky (as proved by similar changes made in the past causing bugs to escape into a released puppet version). We already have the list of special functions and I see no real harm in changing how "functions that may be called without parentheses" is actually implemented as we already have this ugly special case. Since Puppet 5.4.0 it is possible to drop the braces around hash entries when they appear as arguments to a function - so this can be used: return( result => 10 ) # unquoted return( 'result' => 10 ) # quoted which is a small improvement in reduction of required punctuation. Add Comment
