Jira (PUP-8349) scheduled_task : Deprecate scheduled_task resource
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8349 scheduled_task : Deprecate scheduled_task resource Change By: Ethan Brown Fix Version/s: PUP 5.4.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-8349) scheduled_task : Deprecate scheduled_task resource
Title: Message Title Ethan Brown moved an issue Puppet / PUP-8349 scheduled_task : Deprecate scheduled_task resource Change By: Ethan Brown Component/s: scheduled_task Key: MODULES PUP - 6400 8349 Project: Forge Modules Puppet 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-8349) scheduled_task : Deprecate scheduled_task resource
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8349 scheduled_task : Deprecate scheduled_task resource Change By: Ethan Brown Affects Version/s: PUP 5.3.3 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-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1913 Puppet user resource should respect the forcelocal option Change By: Owen Rodabaugh CS Priority: Needs Priority Reviewed 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 Owen Rodabaugh updated an issue Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Owen Rodabaugh CS Priority: Needs Priority Reviewed 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-8332) scheduled_task : Deprecate scheduled_task resource
Title: Message Title Erick Banks updated an issue Puppet / PUP-8332 scheduled_task : Deprecate scheduled_task resource Change By: Erick Banks Summary: scheduled_task : Deprecate scheduled_task resource 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-6214) scheduled_task : Confusing error message displayed when using incorrect value with scheduled_task resource
Title: Message Title Erick Banks updated an issue Puppet / PUP-6214 scheduled_task : Confusing error message displayed when using incorrect value with scheduled_task resource Change By: Erick Banks Summary: scheduled_task : Confusing error message displayed when using incorrect value with scheduled_task resource 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-6910) scheduled_task: I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after
Title: Message Title Erick Banks updated an issue Puppet / PUP-6910 scheduled_task: I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after Change By: Erick Banks Summary: scheduled_task: I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after 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-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Michelle Fredette commented on BOLT-261 Re: Uppercase class task name should not work as a reference to a task in a plan Alex Dreyer - Is this appropriate for current docs? (I assume yes) 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-7036) Cannot configure a scheduled task with two "." in the name.
Title: Message Title Erick Banks commented on PUP-7036 Re: Cannot configure a scheduled task with two "." in the name. Erick Banks try repro in puppet 5.3 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-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Owen Rodabaugh commented on PUP-1913 Re: Puppet user resource should respect the forcelocal option We reviewed this in CS Triage and have concerns on expanding the provider to handle forcelocal on OSs which do not offer the luseradd commands which forcelocal relies on. This would require the provider to manipulate the etc/shadow, etc/passwd, etc/user, etc/group which is very risky. Forcelocal does work on distributions with the luser* commands. We've seen other cases(SLES pulling in an OpenSUSE package) where users were able to add the libuser package to get this to work. Instead we would recommend updating the documentation to more clearly spell this out and also maybe elevating the debug message about forcelocal to warning level so that the reasons behind this not working are more clear. 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-6910) I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after
Title: Message Title Erick Banks updated an issue Puppet / PUP-6910 I'd like to create a scheduled_task that runs at startup and repeats every 15 minutes after Change By: Erick Banks 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 (BOLT-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Nick Lewis commented on BOLT-268 Re: Investigate using log4r for logging and stdoutoutput in bolt Yep, that would be https://github.com/puppetlabs/bolt/pull/244 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-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Michael Smith commented on BOLT-268 Re: Investigate using log4r for logging and stdoutoutput in bolt Is there a PR associated with this? 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-8223) User and group modifications should respect forcelocal
Title: Message Title Melissa Stone assigned an issue to Trey Dockendorf Puppet / PUP-8223 User and group modifications should respect forcelocal Change By: Melissa Stone Assignee: Melissa Stone Trey Dockendorf 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-8321) Update how warn_once and deprecation warnings print their location and i18n messages
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once and deprecation warnings print their location and i18n messages Change By: Eric Delaney Acceptance Criteria: * Update warn_once() to use error_location()* Update issue_deprecation_warning() to use error_location()* Update warn_once calls with i18n strings* Update deprecation_warning() calls with i18n strings* Changes pass unit and acceptance 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-8321) Update how warn_once and deprecation warnings print their location and i18n messages
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8321
Update how warn_once and deprecation warnings print their location and i18n messages
Change By:
Eric Delaney
Need to update the how the warn_once () method and issue_deprecation_warning() method prints the file and line location information by using Puppet::Util::Errors.error_location and its i18n friendly output format. Also Need to update all the calls strings passed to warn_once to include i18n string decorations for the message these methods .{code} def warn_once(kind, key, message, file = nil, line = nil, level = :warning)return if Puppet[:disable_warnings].include?(kind)$unique_warnings ||= {}if $unique_warnings.length < 100 then if (! $unique_warnings.has_key?(key)) then$unique_warnings[key] = messagecall_trace =case MM.new(file, line)when SUPPRESS_FILE_LINE ''when FILE_AND_LINE _("\n (at %{file}:%{line})") % { file: file, line: line }when FILE_NO_LINE _("\n (in %{file})") % { file: file }when NO_FILE_LINE _("\n (in unknown file, line %{line})") % { line: line }else _("\n (file & line not available)")endsend_log(level, "#{message}#{call_trace}") endend end{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
Jira (PUP-8321) Update how warn_once and deprecation warnings print their location and i18n messages
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once and deprecation warnings print their location and i18n messages Change By: Eric Delaney Summary: Update how warn_once prints the file and line deprecation warnings print their location of messages and calls to warn_once i18n messages 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-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-1913 Puppet user resource should respect the forcelocal option Change By: Halim Wijaya CS Priority: Needs Priority 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-8337 Package source on Windows errors out on deduped installation files Change By: Ethan Brown Assignee: Ethan Brown 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-8348) Gatling server tests with Java 9
Title: Message Title Lizzi Lindboe created an issue Puppet / PUP-8348 Gatling server tests with Java 9 Issue Type: Task Assignee: Unassigned Created: 2018/01/11 3:32 PM Priority: Normal Reporter: Lizzi Lindboe Attempt to test Jruby 9k + JIT with Java 9. Try to find a platform that has this built in already to make it easier; it's okay to run this manually instead of writing the automation. We want to understand the impact moving to Java 9 would have on the performance problems server is facing with JRuby 9k. Timebox this; if it's very complicated or clearly not helping performance we can stop trying to test it. Add Comment This message
Jira (PUP-8345) make code using '\' line continuation more readable and address i18n strings
Title: Message Title Eric Delaney commented on PUP-8345 Re: make code using '\' line continuation more readable and address i18n strings Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/863df23ac72fee9a81ebef657cf120a3e22b820f 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-305) Task Manifests should include a defaults field
Title: Message Title Abir Majumdar created an issue Puppet Task Runner / BOLT-305 Task Manifests should include a defaults field Issue Type: Improvement Assignee: Unassigned Created: 2018/01/11 3:00 PM Priority: Normal Reporter: Abir Majumdar When you pick a Task in the console it would be nice to have pre-populated text fields and pre-selected entries (aka defaults). It could be a new attribute in the metadata.json. It opens up more flexibility with task params. Scenario 1: If your parameter requires a particular format like a URL. You could put an example url as a default. Scenario 2: I want the developer to pick from a list, but if they don't care they can ignore the field and run the task. Right now you only have the option for optional/required fields. Add Comment
Jira (PUP-8347) Find more places where we report the file or line information and convert them to use error_location()
Title: Message Title
Eric Delaney created an issue
Puppet / PUP-8347
Find more places where we report the file or line information and convert them to use error_location()
Issue Type:
Task
Assignee:
Unassigned
Created:
2018/01/11 2:46 PM
Priority:
Normal
Reporter:
Eric Delaney
We need to grep the puppet code base and find more of the locations that we report the file and line location information for an error and use the Puppet::Util::Errors.error_location() method to create the string so we are consistent.
For example:
$ grep -r 'at line' lib
lib/puppet/settings/config_file.rb:raise(Puppet::Error, _("Illegal section '%{name}' in config file %{file} at line %{line}. The only valid puppet.conf sections are: [%{allowed_sections}]. Please use the directory environments feature to specify environments. (See https://docs.puppet.com/puppet/latest/reference/environments.html)") % { name: section.name, file: file, line: section.line_number, allowed_sections: allowed_section_names.join(", ") })
Jira (BOLT-295) Run any script with extension handler on Windows
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-295 Run any script with extension handler on Windows Change By: Michelle Fredette Labels: docs_reviewed 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-285) Bolt should handle parser errors better
Title: Message Title Michelle Fredette commented on BOLT-285 Re: Bolt should handle parser errors better added resolved issue. 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-285) Bolt should handle parser errors better
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: Michelle Fredette Labels: resolved-issue-added 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-295) Run any script with extension handler on Windows
Title: Message Title Michelle Fredette commented on BOLT-295 Re: Run any script with extension handler on Windows I added the new setting and the release note. 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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title Eric Putnam commented on PDOC-76 Re: Document the available YARD @tags for ruby/pp doc objects Jean Bond, I marked this as "Ready for Review" just because it's ready for you to look at. Made more sense than In Progress. Anyway, feel free to close when you're done I think. 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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title Eric Putnam assigned an issue to Eric Putnam Puppet Strings / PDOC-76 Document the available YARD @tags for ruby/pp doc objects Change By: Eric Putnam Assignee: Eric Putnam 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-81) Error message regarding ssh-agent on successful run
Title: Message Title Thomas Kishel commented on BOLT-81 Re: Error message regarding ssh-agent on successful run As suggested by Alex, we could just check the environment to see if ssh-agent is configured. For example, add: options[:use_agent] = ENV['SSH_AUTH_SOCK'].to_s && File.socket?(ENV['SSH_AUTH_SOCK']) to: https://github.com/puppetlabs/bolt/blob/master/lib/bolt/node/ssh.rb#L36 Since ssh-agent communicates via unix-domain sockets, as per: A unix-domain socket is created and the name of this socket is stored in the SSH_AUTH_SOCK environment variable. The socket is made accessible only to the current user. Add Comment
Jira (BOLT-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title Alex Dreyer commented on BOLT-286 Re: Clean up Bolt::Result ExecutionResult interface BOLT-222 is changing the execution result as well... 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-8321) Update how warn_once prints the file and line location of messages and calls to warn_once
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8321
Update how warn_once prints the file and line location of messages and calls to warn_once
Change By:
Eric Delaney
Need to update the how the warn_once method prints the file and line location information by using Puppet::Util::Errors.error_location and its i18n friendly output format. Also update all the calls to warn_once to include i18n string decorations for the message. {code} def warn_once(kind, key, message, file = nil, line = nil, level = :warning)return if Puppet[:disable_warnings].include?(kind)$unique_warnings ||= {}if $unique_warnings.length < 100 then if (! $unique_warnings.has_key?(key)) then$unique_warnings[key] = messagecall_trace =case MM.new(file, line)when SUPPRESS_FILE_LINE ''when FILE_AND_LINE _("\n (at %{file}:%{line})") % { file: file, line: line }when FILE_NO_LINE _("\n (in %{file})") % { file: file }when NO_FILE_LINE _("\n (in unknown file, line %{line})") % { line: line }else _("\n (file & line not available)")endsend_log(level, "#{message}#{call_trace}") endend end{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
Jira (PUP-8321) Update how warn_once prints the file and line location of messages and calls to warn_once
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once prints the file and line location of messages and calls to warn_once Change By: Eric Delaney Summary: Update how warn_once prints the file and line location of messages and calls to warn_once 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-8321) Update how warn_once prints the file and line location of messages
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once prints the file and line location of messages Change By: Eric Delaney Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.4 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-8321) Update how warn_once prints the file and line location of messages
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once prints the file and line location of messages Change By: Eric Delaney 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 (PUP-8321) Update how warn_once prints the file and line location of messages
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8321 Update how warn_once prints the file and line location of messages Change By: Eric Delaney Assignee: Eric Delaney 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-81) Error message regarding ssh-agent on successful run
Title: Message Title Thomas Kishel commented on BOLT-81 Re: Error message regarding ssh-agent on successful run Given: https://github.com/net-ssh/net-ssh/issues/137 https://github.com/net-ssh/net-ssh/pull/159 :use_agent => Set false to disable the use of ssh-agent. Defaults to true We could create a disable-ssh-agent option to specify the Net-SSH :use_agent option ... https://github.com/puppetlabs/bolt/pull/240 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-8039) Puppet 4.10.x: Only warn once when gettext cannot be found
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8039 Puppet 4.10.x: Only warn once when gettext cannot be found Change By: Maggie Dreyer Affects Version/s: PUP 4.10.8 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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide.*This is a list of the built-in YARD tags that are also picked up by puppet-strings. This is NOT a list of all puppet-strings tags.* YARD reference: http://www.rubydoc.info/gems/yard/0.6.4/file/docs/Tags.md#List_of_Available_Tags h3. @exampleShow an example snippet of code for an object. The first line is an optional title. Use for specific examples of a given component. One example tag per example.h3. @paramdefines a parameter for the given component. remember, if Puppet 4 types are present in the source, they will override whatever is in the docs.h3. @raisecan be used to document any exceptions that may be raised by the given component{{# @raise PuppetError this error will be raised if x}}h3. @authorAuthor of the componenth3. @seeused to document additional references. comes out in the generated docs as a "See Also" section. one tag per reference (website, other method, etc)h3. @sinceused to document how long the component has been available.{{# @since version 1.1.1}}h3. @versionanother way to talk about which version the component is in or how long it's been available.h3. @option* only displays if there's actually an options hash being passed to the method* should be used in conjunction with a @param tage.g.{code}# @param [Hash] opts # List of options# @option opts [String] :option1 # option 1 in the hash# @option opts [Array] :option2# option 2 in the hash{code}
Add Comment
Jira (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide. * This is a list of the built-in YARD tags that are also picked up by puppet-strings. This is NOT a list of all puppet-strings tags. * h3. @exampleShow an example snippet of code for an object. The first line is an optional title. Use for specific examples of a given component. One example tag per example.h3. @paramdefines a parameter for the given component. remember, if Puppet 4 types are present in the source, they will override whatever is in the docs.h3. @raisecan be used to document any exceptions that may be raised by the given component{{# @raise PuppetError this error will be raised if x}}h3. @authorAuthor of the componenth3. @seeused to document additional references. comes out in the generated docs as a "See Also" section. one tag per reference (website, other method, etc)h3. @sinceused to document how long the component has been available.{{# @since version 1.1.1}}h3. @versionanother way to talk about which version the component is in or how long it's been available.h3. @option* only displays if there's actually an options hash being passed to the method* should be used in conjunction with a @param tage.g.{code}# @param [Hash] opts # List of options# @option opts [String] :option1 # option 1 in the hash# @option opts [Array] :option2# option 2 in the hash{code}
Add Comment
Jira (PUP-8346) File type content attribute accepts non-strings
Title: Message Title Pär Lindfors created an issue Puppet / PUP-8346 File type content attribute accepts non-strings Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Components: Types and Providers Created: 2018/01/11 1:12 PM Priority: Normal Reporter: Pär Lindfors Puppet Version: 5.3.3, 3.8.7, 2.7.26 The documentation of the file type's content attribute is: "The desired contents of a file, as a string." However an array of strings is also accepted. When content is set to an array, the last element of the array is used as content. I don't know if this behaviour is intended, it is not documented as far as I can tell. This behaviour is not new, I tested using Puppet 5.3, 3.8, 2.7 and got the same result with all of them. Desired Behavior: I would expect the following to result in an evaluation error due to content not being a String value:
Jira (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide. h3. @summaryunique to This is a list of the built-in YARD tags that are also picked up by puppet-strings , used for . This is NOT a short summary list of the component all puppet-strings tags. h3. @exampleShow an example snippet of code for an object. The first line is an optional title. Use for specific examples of a given component. One example tag per example.h3. @paramdefines a parameter for the given component. remember, if Puppet 4 types are present in the source, they will override whatever is in the docs.h3. @raisecan be used to document any exceptions that may be raised by the given component{{# @raise PuppetError this error will be raised if x}}h3. @authorAuthor of the componenth3. @seeused to document additional references. comes out in the generated docs as a "See Also" section. one tag per reference (website, other method, etc)h3. @sinceused to document how long the component has been available.{{# @since version 1.1.1}}h3. @versionanother way to talk about which version the component is in or how long it's been available.h3. @option* only displays if there's actually an options hash being passed to the method* should be used in conjunction with a @param tage.g.{code}# @param [Hash] opts # List of options# @option opts [String] :option1 # option 1 in the hash# @option opts [Array] :option2# option 2 in the hash{code}
Add Comment
Jira (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide.h3. @ summaryunique to puppet-strings, used for a short summary of the componenth3. @ exampleShow an example snippet of code for an object. The first line is an optional title. Use for specific examples of a given component. One example tag per example.h3. @ paramdefines a parameter for the given component. remember, if Puppet 4 types are present in the source, they will override whatever is in the docs.h3. @ raisecan be used to document any exceptions that may be raised by the given component{{# @raise PuppetError this error will be raised if x}}h3. @ authorAuthor of the componenth3. @ seeused to document additional references. comes out in the generated docs as a "See Also" section. one tag per reference (website, other method, etc)h3. @ sinceused to document how long the component has been available.{{# @since version 1.1.1}}h3. @ versionanother way to talk about which version the component is in or how long it's been available.h3. @ option* only displays if there's actually an options hash being passed to the method* should be used in conjunction with a @param tage.g.{code}# @param [Hash] opts # List of options# @option opts [String] :option1 # option 1 in the hash# @option opts [Array] :option2# option 2 in the hash{code}
Add Comment
Jira (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide. h3. summary unique to puppet-strings, used for a short summary of the componenth3. example Show an example snippet of code for an object. The first line is an optional title. Use for specific examples of a given component. One example tag per example.h3. param defines a parameter for the given component. remember, if Puppet 4 types are present in the source, they will override whatever is in the docs.h3. raise can be used to document any exceptions that may be raised by the given component{{# @raise PuppetError this error will be raised if x}}h3. author Author of the componenth3. see used to document additional references. comes out in the generated docs as a "See Also" section. one tag per reference (website, other method, etc)h3. since used to document how long the component has been available.{{# @since version 1.1.1}} h3. versionanother way to talk about which version the component is in or how long it's been available.h3. option* only displays if there's actually an options hash being passed to the method * should be used in conjunction with a @param tage.g.{code}# @param [Hash] opts # List of options# @option opts [String] :option1 # option 1 in the hash# @option opts [Array] :option2# option 2 in the hash{code}
Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Michelle Fredette Labels: docs_reviewed 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-266) Log run_* actions when called from a plan
Title: Message Title Michelle Fredette commented on BOLT-266 Re: Log run_* actions when called from a plan added a release note. 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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide. @ summary @ example param raiseauthorseesinceversionoptions
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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) )*UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide. @summary@param
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-8345) make code using '\' line continuation more readable and address i18n strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8345 make code using '\' line continuation more readable and address i18n strings Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-8345) make code using '\' line continuation more readable and address i18n strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8345 make code using '\' line continuation more readable and address i18n strings Change By: Eric Delaney Release Notes: Not Needed 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-8345) make code using '\' line continuation more readable and address i18n strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8345 make code using '\' line continuation more readable and address i18n strings Change By: Eric Delaney There are a few places in the code where we use a '\' to continue the line on the next line and in some of the places that we use it, it makes the code less readable. Also address i18n strings while making changes 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-8345) make code using '\' line continuation more readable and address i18n strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8345 make code using '\' line continuation more readable and address i18n strings Change By: Eric Delaney Summary: make code using '\' line continuation more readable and address i18n strings 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-8345) make code using '\' line continuation more readable
Title: Message Title Eric Delaney created an issue Puppet / PUP-8345 make code using '\' line continuation more readable Issue Type: Task Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2018/01/11 11:38 AM Fix Versions: PUP 5.3.4 Priority: Normal Reporter: Eric Delaney There are a few places in the code where we use a '\' to continue the line on the next line and in some of the places that we use it, it makes the code less readable. Add Comment
Jira (PUP-8345) make code using '\' line continuation more readable
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8345 make code using '\' line continuation more readable Change By: Eric Delaney Assignee: Eric Delaney 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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-76
Document the available YARD @tags for ruby/pp doc objects
Change By:
Eric Putnam
You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list!For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another ticket. :) ) *UPDATE*: this ticket already exists! A user recently found that not _all_ of the YARD tags can be used. This information should all go into the style guide.
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 (PDOC-76) Document the available YARD @tags for ruby/pp doc objects
Title: Message Title Eric Putnam assigned an issue to Eric Putnam Puppet Strings / PDOC-76 Document the available YARD @tags for ruby/pp doc objects Change By: Eric Putnam Assignee: Eric Putnam 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-295) Run any script with extension handler on Windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-295 Run any script with extension handler on Windows Change By: Michael Smith 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 (BOLT-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Alex Dreyer commented on BOLT-261 Re: Uppercase class task name should not work as a reference to a task in a plan Given how this is handled in the loader we should probably just add a warning in docsthat users should refer to tasks and plans as all lowercase: https://puppet.com/docs/bolt/0.x/writing_plans.html#running-tasks-from-plans Task names should not include uppercase characters and https://puppet.com/docs/bolt/0.x/writing_plans.html#running-plans-in-a-plan Plan names should not include uppercase characters. Michelle Fredette 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-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: Alex Dreyer 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 (BOLT-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Alex Dreyer assigned an issue to Michelle Fredette Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: Alex Dreyer Assignee: Alex Dreyer Michelle Fredette 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-295) Run any script with extension handler on Windows
Title: Message Title Alex Dreyer commented on BOLT-295 Re: Run any script with extension handler on Windows Michelle Fredette This adds a new configution setting to document. Predocs -> https://github.com/puppetlabs/bolt/pull/235/files 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-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Release Notes Summary: Information about actions run from a plan are now logged at the notice level which is visible by default. This provides good default logging for progress during a plan. Release Notes: New Feature 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-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Melissa Stone Release Notes: Not Needed 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-8344) Switch to new nightly format for testing with puppetserver latest
Title: Message Title Melissa Stone created an issue Puppet / PUP-8344 Switch to new nightly format for testing with puppetserver latest Issue Type: Task Assignee: Unassigned Created: 2018/01/11 10:28 AM Priority: Normal Reporter: Melissa Stone Hey team! A follow-up about upcoming puppet5 nightlies: If your repo pulls from nightlies.pl.com for testing, you will need to update your paths after we make the switch to the new nightly repos. Currently, builds are in directories under the name of the component, e.g. http://nightlies.puppet.com/puppet-agent/. When we roll out new nightlies, paths will be similar to final-build paths, as on [apt|yum|downloads].pl.com, e.g. http://nightlies.puppet.com/puppet5-nightly/el/7/x86_64/. Please let the RE team know if you have any questions or need help updating tests - you can find us in the 'release-new' HipChat room, or reply to this email. Thanks! Add Comment
Jira (PUP-8327) Optimize TypeParser for common data type string
Title: Message Title Thomas Hallgren commented on PUP-8327 Re: Optimize TypeParser for common data type string Merged to master at dac944e. 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-8327) Optimize TypeParser for common data type string
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8327 Optimize TypeParser for common data type string 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 (BOLT-295) Run any script with extension handler on Windows
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-295
Run any script with extension handler on Windows
Change By:
Michael Smith
Release Notes Summary:
Previously for WinRM targets Bolt would only run scripts and tasks with the extensions .ps1, .pp, or .rb. Any others it would attempt to run as a powershell script.Now Bolt will reject scripts that don't end in those 3 extensions by default. More extensions can be allowed by adding them to your Bolt config, e.g. {code} ``` winrm: extensions: [.py, .pl] {code} ``` Any extensions added this way rely on the target host having the appropriate file type association registered for that extension with a way to run it.
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-295) Run any script with extension handler on Windows
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-295
Run any script with extension handler on Windows
Change By:
Michael Smith
Release Notes Summary:
Previously for WinRM targets Bolt would only run scripts and tasks with the extensions .ps1, .pp, or .rb. Any others it would attempt to run as a powershell script.Now Bolt will reject scripts that don't end in those 3 extensions by default. More extensions can be allowed by adding them to your Bolt config, e.g.{code}winrm: extensions: [.py, .pl]{code}Any extensions added this way rely on the target host having the appropriate file type association registered for that extension with a way to run it.
Release Notes:
New Feature
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-295) Run any script with extension handler on Windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-295 Run any script with extension handler on Windows Change By: Michael Smith Release Notes Summary: Previously for WinRM targets Bolt would only run scripts and tasks with the extensions .ps1, .pp, or .rb. Any others it would attempt to run as a powershell script.Now Bolt will reject scripts that don't end in those 3 extensions by default. More extensions can be allowed by adding them to your Bolt config, e.g. ``` winrm: extensions: [.py, .pl] ``` Any extensions added this way rely on the target host having the appropriate file type association registered for that extension with a way to run it. 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-285) Bolt should handle parser errors better
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: Michael Smith Release Notes Summary: Simplifies some errors reported from running tasks and plans. When using Also changes to printing human- format output, prints formatted errors in running a subcommand to stdout and colors coloring them red rather than printing to stderr.When using , while json- format formatted output , errors will no longer be reprinted reprint errors on stderr. Errors parsing Bolt configuration will continue to be output on stderr. 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-285) Bolt should handle parser errors better
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: Michael Smith Release Notes Summary: Simplifies some errors reported from running tasks and plans.When using human-format output, prints errors to stdout and colors them red rather than printing to stderr.When using json-format output, errors will no longer be reprinted on stderr.Errors parsing Bolt configuration will continue to be output on stderr. Release Notes: Bug Fix 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-8327) Optimize TypeParser for common data type string
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8327 Optimize TypeParser for common data type string Change By: Henrik Lindberg 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-8327) Optimize TypeParser for common data type string
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8327 Optimize TypeParser for common data type string Change By: Henrik Lindberg Fix Version/s: PUP 5.y Fix Version/s: PUP 5.4.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 (BOLT-285) Bolt should handle parser errors better
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: Michael Smith Fix Version/s: BOLT 0.14.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 (BOLT-304) Show parameter names and types with bolt plan show
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-304 Show parameter names and types with bolt plan show Issue Type: New Feature Assignee: Unassigned Created: 2018/01/11 9:47 AM Priority: Normal Reporter: Alex Dreyer Plan parameter and usage information should be displayed with bolt plan show . It should align with the bolt task show output but does not have to include descriptions since they aren't available in the PAL api yet. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8343) When enforcing String data type for a class param, a regex data type does not raise an error.
Title: Message Title
Sam Woods created an issue
Puppet / PUP-8343
When enforcing String data type for a class param, a regex data type does not raise an error.
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2018/01/11 9:00 AM
Priority:
Normal
Reporter:
Sam Woods
When enforcing a String data type for a class parameter:
class test::myclass (
String $my_string = 'default',
) {
Jira (BOLT-209) Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-209 Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files Change By: Alex Dreyer Sprint: Bolt Ready for 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 (BOLT-209) Bolt exits zero on run_* commands that fail on some targets
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-209 Bolt exits zero on run_* commands that fail on some targets Change By: Alex Dreyer Issue Type: Bug New Feature 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-295) Run any script with extension handler on Windows
Title: Message Title Alex Dreyer commented on BOLT-295 Re: Run any script with extension handler on Windows It's BOLT-209 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-209) Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-209 Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files Change By: Alex Dreyer Summary: Bolt exits zero on run_* commands that fail on should exit 2 when some targets nodes fail for commands, scripts, tasks and files 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-209) Bolt exits zero on run_* commands that fail on some targets
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-209 Bolt exits zero on run_* commands that fail on some targets Change By: Alex Dreyer Summary: Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file zero on run_* commands that fail on some targets 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-295) Run any script with extension handler on Windows
Title: Message Title Zach Reichert commented on BOLT-295 Re: Run any script with extension handler on Windows Bolt seems to exit 0 if an extension is not configured on a node. Is this the correct behavior? [6] pry(#)> result = bolt_command_on(bolt, bolt_command, flags) tlr76ts71drauxh.delivery.puppetlabs.net (centos7-64-1) 08:33:46$ bolt script run C100549.exe --nodes winrm://nkydbnrbt5sxqb6.delivery.puppetlabs.net -u Administrator -p Qu@lity! --insecure Started on nkydbnrbt5sxqb6.delivery.puppetlabs.net... Failed on nkydbnrbt5sxqb6.delivery.puppetlabs.net: File extension .exe is not enabled, to run it please add to 'winrm: extensions' Ran on 1 node in 0.33 seconds tlr76ts71drauxh.delivery.puppetlabs.net (centos7-64-1) executed in 0.79 seconds
Jira (PUP-8341) Lookup interpolation on alias to missing key should return not found
Title: Message Title Henrik Lindberg commented on PUP-8341 Re: Lookup interpolation on alias to missing key should return not found The docs PR looks fine. If we are to add a proper alias to hiera 5 then that can be done either as I suggested above (an alias lookup function) or as a lookup_option. The later has the advantage that it is done in the data and that any function can return this. 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-8341) Lookup interpolation on alias to missing key should return not found
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8341 Lookup interpolation on alias to missing key should return not found Change By: Henrik Lindberg 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 (BOLT-295) Run any script with extension handler on Windows
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-295 Run any script with extension handler on Windows Change By: Zach Reichert Assignee: Zach Reichert 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-285) Bolt should handle parser errors better
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: Zach Reichert Assignee: Zach Reichert 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-8341) Lookup interpolation on alias to missing key should return not found
Title: Message Title Sean Millichamp commented on PUP-8341 Re: Lookup interpolation on alias to missing key should return not found I understand the concerns about preserving backwards compatible behavior, but it is certainly surprising behavior for someone using the function for the first time. The documentation at https://puppet.com/docs/puppet/5.3/hiera_merging.html#alias doesn't outright address the issue of missing keys but certainly leaves one with the impression that the alias function will basically provide a 1:1 key name remap behavior. If you don't want to change the behavior of alias I'd like to suggest that the documentation be clarified as to the behavior with missing keys. Also, I'd like to suggest that a similar function (maybe remap_key) be supplied at part of Puppet that does preserve identical behavior, and if not part of Puppet then it seems reasonable for inclusion in stdlib. I have put up a PR with a clarifying note here: https://github.com/puppetlabs/puppet-docs/pull/832 I certainly can create my own function to do this, but it feels like a common enough pattern to want to remap key names that having a standard function people can use that doesn't have any surprising behaviors in it would be beneficial. 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-3801) PuppetDB migration stuck (31) fact_values.
Title: Message Title Steve Traylen commented on PDB-3801 Re: PuppetDB migration stuck (31) fact_values. In reality not stuck - stage 31 just takes 14 hours for us 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-303) Unable to connect over winrm HTTP
Title: Message Title Glenn Sarti commented on BOLT-303 Re: Unable to connect over winrm HTTP Netstat on the remote machine C:\Users\Administrator>netstat -a -n -o Active Connections Proto Local Address Foreign AddressState PID TCP0.0.0.0:1350.0.0.0:0 LISTENING 628 TCP0.0.0.0:4450.0.0.0:0 LISTENING 4 TCP0.0.0.0:3389 0.0.0.0:0 LISTENING 1352 TCP0.0.0.0:5985 0.0.0.0:0 LISTENING 4<-- It's listening TCP0.0.0.0:47001 0.0.0.0:0 LISTENING 4
Jira (BOLT-303) Unable to connect over winrm HTTP
Title: Message Title Glenn Sarti commented on BOLT-303 Re: Unable to connect over winrm HTTP Firewall is turned off on the target node. Powershell WinRM is clearly working C:\Source\tmp\reboot-dylan\reboot [master ≡ +1 ~0 -0 !]> be bolt --version 0.13.0 C:\Source\tmp\reboot-dylan\reboot [master ≡ +1 ~0 -0 !]> be ruby --version ruby 2.3.1p112 (2016-04-26 revision 54768) [x64-mingw32] C:\Source\tmp\reboot-dylan\reboot [master ≡ +1 ~0 -0 !]> Add Comment
Jira (BOLT-303) Unable to connect over winrm HTTP
Title: Message Title Glenn Sarti updated an issue Puppet Task Runner / BOLT-303 Unable to connect over winrm HTTP Change By: Glenn Sarti Affects Version/s: 0.13.1 Affects Version/s: BOLT 0.13.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 (BOLT-303) Unable to connect over winrm HTTP
Title: Message Title Glenn Sarti updated an issue Puppet Task Runner / BOLT-303 Unable to connect over winrm HTTP Change By: Glenn Sarti Environment: From OS: Windows 10 Version 1709Ruby 2.3.1Bolt 0.13. 1 0 To OS: Windows Server 2012R2 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-303) Unable to connect over winrm HTTP
Title: Message Title Glenn Sarti created an issue Puppet Task Runner / BOLT-303 Unable to connect over winrm HTTP Issue Type: Bug Affects Versions: 0.13.1 Assignee: Unassigned Created: 2018/01/11 12:56 AM Environment: From OS: Windows 10 Version 1709 Ruby 2.3.1 Bolt 0.13.1 To OS: Windows Server 2012R2 Priority: Normal Reporter: Glenn Sarti I am trying to test the reboot task for the reboot module and I cannot get bolt to connect over WinRM even though PowerShell can run commands remotely fine. C:\Source\tmp\reboot-dylan\reboot [master ≡ +1 ~0 -0 !]> bundle exec bolt task run reboot --modulepath .. --nodes 192.168.200.79 --user Administrator --password Password1 --debug --params @C:\Source\tmp\reboot-dylan\reboot\params.json --insecure --transport winrm --verbose
