Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7237 fix puppet acceptance Rake tasks Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7372) puppet 4.9.4 lookup fails with undefined method error message
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7372 puppet 4.9.4 lookup fails with undefined method error message Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7328) Duplication errors on Puppet Class "settings".
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7328 Duplication errors on Puppet Class "settings". Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7371) Type mismatches for variants with undef are incorrectly reported
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7371 Type mismatches for variants with undef are incorrectly reported Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7370) Ensure that returned value from data provider is type checked only once.
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7370 Ensure that returned value from data provider is type checked only once. Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7334) add a default hierarchy to module hiera.yaml
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7334 add a default hierarchy to module hiera.yaml Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7281) Add support for default options in hiera.yaml v 5
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7281 Add support for default options in hiera.yaml v 5 Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7330) Puppet::LookupKey and Puppet::LookupValue types are unavailable to Hiera backend functions
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-7330 Puppet::LookupKey and Puppet::LookupValue types are unavailable to Hiera backend functions Change By: William Hopper Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-165) Release puppet-strings 1.1.0
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-165 Release puppet-strings 1.1.0 Change By: William Hopper Skipping subtasks in favor or just commenting here.1. Is the code ready for release?CHANGELOG updated and gemspec version updated. Tests are all passing and all tickets for this release are resolved.2. Reconcile git commits and JIRA ticketsAll commits have associated JIRA tickets (except maint commits).3. Is the Jira tidy-up done for this release and prepared for the next one?We now have PDOC version 1.1.1 in JIRA.Filters:Fixed in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=25603Introduced in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=256044. Prepare long form release notes:Subject: Announce: Strings 1.1.0 ReleasedHello, all! Today we're releasing puppet-strings 1.1.0. This is a small release that includes two features: the new `summary` tag, and the ability to explicitly document the types of parameters in Puppet 4 code.Features:* The `summary` tag can be added to any code that puppet-strings supports. The recommended length limit for a summary is 140 characters. Warnings will be issued for strings longer than this limit.* Puppet 4 parameter types can now be (optionally) explicitly documented. Previously, this was not allowed because Puppet 4 parameter types can be automatically determined without extra documentation. However, users may desire to do so anyway for consistency. Strings will emit a warning if the documented type does not match the actual type. In such an event, the incorrect documented type will be ignored in favor of the real one. Note that this is purely optional - Strings will continue to automatically determine the types of Puppet 4 parameters without this documentation.Never used Strings? Check out our recent blog post to learn more! https://puppet.com/blog/using-puppet-strings-generate-great-documentation-puppet-modulesThe ruby gem can be found here: https://rubygems.org/gems/puppet-stringsFor installation and usage instructions, see https://github.com/puppetlabs/puppet-strings/blob/master/README.md.To track issues related to this release or report issues, see the PDOC Jira project:JIRA Project: https://tickets.puppetlabs.com/browse/PDOCFixed in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=25603Introduced in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=256045. Tag the release Tagged at commit eaa3d586590da9d17fc6549a1aa3160c067280b9. 6. Build and smoke test gem Smoke tested on centos 7. 7. Push tag to GitHub Tag and gem pushed. 8. Send out announcements Announcements sent to announce, users, and dev. 9. Close all resolved tickets in JIRA. Done. Add Comment
Jira (PDOC-165) Release puppet-strings 1.1.0
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-165 Release puppet-strings 1.1.0 Change By: William Hopper Skipping subtasks in favor or just commenting here.1. Is the code ready for release? CHANGELOG updated and gemspec version updated. Tests are all passing and all tickets for this release are resolved. 2. Reconcile git commits and JIRA tickets All commits have associated JIRA tickets (except maint commits). 3. Is the Jira tidy-up done for this release and prepared for the next one? We now have PDOC version 1.1.1 in JIRA.Filters:Fixed in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=25603Introduced in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=25604 4. Prepare long form release notes: Subject: Announce: Strings 1.1.0 ReleasedHello, all! Today we're releasing puppet-strings 1.1.0. This is a small release that includes two features: the new `summary` tag, and the ability to explicitly document the types of parameters in Puppet 4 code.Features:* The `summary` tag can be added to any code that puppet-strings supports. The recommended length limit for a summary is 140 characters. Warnings will be issued for strings longer than this limit.* Puppet 4 parameter types can now be (optionally) explicitly documented. Previously, this was not allowed because Puppet 4 parameter types can be automatically determined without extra documentation. However, users may desire to do so anyway for consistency. Strings will emit a warning if the documented type does not match the actual type. In such an event, the incorrect documented type will be ignored in favor of the real one. Note that this is purely optional - Strings will continue to automatically determine the types of Puppet 4 parameters without this documentation.Never used Strings? Check out our recent blog post to learn more! https://puppet.com/blog/using-puppet-strings-generate-great-documentation-puppet-modulesThe ruby gem can be found here: https://rubygems.org/gems/puppet-stringsFor installation and usage instructions, see https://github.com/puppetlabs/puppet-strings/blob/master/README.md.To track issues related to this release or report issues, see the PDOC Jira project:JIRA Project: https://tickets.puppetlabs.com/browse/PDOCFixed in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=25603Introduced in 1.1.0: https://tickets.puppetlabs.com/issues/?filter=25604 5. Tag the release6. Build and smoke test gem7. Push tag to GitHub8. Send out announcements9. Close all resolved tickets in JIRA. Add Comment
Jira (PDOC-143) Add Windows information to Strings README
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-143 Add Windows information to Strings README Change By: William Hopper Fix Version/s: PDOC 1.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-144) acceptance: fix windows pre-suite
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-144 acceptance: fix windows pre-suite Change By: William Hopper Fix Version/s: PDOC 1.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-165) Release puppet-strings 1.1.0
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-165 Release puppet-strings 1.1.0 Change By: William Hopper Fix Version/s: PDOC 1.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: William Hopper Fix Version/s: PDOC 1.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-155) Strings should allow parameter types to be documented in Puppet 4 code
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-155 Strings should allow parameter types to be documented in Puppet 4 code Change By: William Hopper Fix Version/s: PDOC 1.0.1 Fix Version/s: PDOC 1.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-165) Release puppet-strings 1.1.0
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-165 Release puppet-strings 1.1.0 Issue Type: Task Assignee: Unassigned Created: 2017/03/16 2:49 PM Priority: Normal Reporter: William Hopper Skipping subtasks in favor or just commenting here. 1. Is the code ready for release? 2. Reconcile git commits and JIRA tickets 3. Is the Jira tidy-up done for this release and prepared for the next one? 4. Prepare long form release notes: 5. Tag the release 6. Build and smoke test gem 7. Push tag to GitHub 8. Send out announcements 9. Close all resolved tickets in JIRA. Add Comment
Jira (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: William Hopper Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-163) failed to generate all docs when there are subfolders inside the manifest dir
Title: Message Title William Hopper commented on PDOC-163 Re: failed to generate all docs when there are subfolders inside the manifest dir Ah, good to hear! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-163) failed to generate all docs when there are subfolders inside the manifest dir
Title: Message Title William Hopper commented on PDOC-163 Re: failed to generate all docs when there are subfolders inside the manifest dir Edwin Biemond try this: bundle exec puppet strings generate ./*/(.pp|.rb). The search won't expand to all files in all subdirectories unless you include the **. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-144) acceptance: fix windows pre-suite
Title: Message Title William Hopper assigned an issue to Unassigned Puppet Strings / PDOC-144 acceptance: fix windows pre-suite Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-4933) Remove cfacter setting
Title: Message Title William Hopper updated an issue Puppet / PUP-4933 Remove cfacter setting Change By: William Hopper Release Notes Summary: This change removes the old cfacter feature, which has been obsolete since the Puppet 4.x series. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3670) Remove Facts#strip_internal method
Title: Message Title William Hopper updated an issue Puppet / PUP-3670 Remove Facts#strip_internal method Change By: William Hopper Release Notes Summary: This change removes the strip_internal method from the Puppet::Node::Facts class. This method has been deprecated since Puppet 4.0.0. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6219) Remove req_bits setting
Title: Message Title William Hopper updated an issue Puppet / PUP-6219 Remove req_bits setting Change By: William Hopper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-3670) Remove Facts#strip_internal method
Title: Message Title William Hopper updated an issue Puppet / PUP-3670 Remove Facts#strip_internal method Change By: William Hopper Labels: maintenance Team: Puppet Developer Experience Sprint: PDE 2017-01-25 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6481) Remove external_facts feature
Title: Message Title William Hopper updated an issue Puppet / PUP-6481 Remove external_facts feature Change By: William Hopper Labels: maintenance Team: Puppet Developer Experience Sprint: PDE 2017-01-25 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-4933) Remove cfacter setting
Title: Message Title William Hopper updated an issue Puppet / PUP-4933 Remove cfacter setting Change By: William Hopper Labels: maintenance Team: Puppet Developer Experience Sprint: PDE 2017-01-25 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6219) Remove req_bits setting
Title: Message Title William Hopper updated an issue Puppet / PUP-6219 Remove req_bits setting Change By: William Hopper Labels: maintenance Team: Puppet Developer Experience Sprint: PDE 2017-01-25 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-156) Support @api tag for classes (in addition to functions)
Title: Message Title William Hopper commented on PDOC-156 Re: Support @api tag for classes (in addition to functions) I also just discovered that our handling of @api (in HTML) is buggy for functions. It only works for functions with multiple dispatches, and thus overload tags, i.e, this kind of works: # Subtracts two things. Puppet::Functions.create_function(:subtract) do # @api private dispatch :subtract_ints do ... end dispatch :subtract_arrays do ... end
Jira (PDOC-155) Strings should allow parameter types to be documented in Puppet 4 code
Title: Message Title
William Hopper created an issue
Puppet Strings / PDOC-155
Strings should allow parameter types to be documented in Puppet 4 code
Issue Type:
Improvement
Affects Versions:
PDOC 1.0.0
Assignee:
Unassigned
Created:
2017/01/10 10:50 AM
Fix Versions:
PDOC 1.0.1
Priority:
Normal
Reporter:
William Hopper
Currently, you may not document the type of a parameter such as the following in puppet 4 code:
# @param [Regexp] param An example parameter.
class base(Regexp $param = /foobar/) {
Jira (FACT-1555) Add the Grape gem to the puppet-forge-api project
Title: Message Title William Hopper created an issue Facter / FACT-1555 Add the Grape gem to the puppet-forge-api project Issue Type: Task Assignee: Unassigned Created: 2017/01/03 1:07 PM Labels: maintenance Priority: Normal Reporter: William Hopper It should be added to both the Gemfile and the Gemfile.lock. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title William Hopper commented on PUP-6893 Re: Remove Ruby 1.9.3 support Are we thinking Puppet 5 or 6 for this one? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-7004) Remove the 'verbatim' option (added in PUP-6781)
Title: Message Title William Hopper commented on PUP-7004 Re: Remove the 'verbatim' option (added in PUP-6781) Henrik Lindberg Is this something we should add to the PUP 5.0 removal epic? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-153) There is no correct method for documenting class variables that are not parameters but are meant to be available.
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-153
There is no correct method for documenting class variables that are not parameters but are meant to be available.
Change By:
William Hopper
Consider the following, commonly used, {{params.pp}}{ { code} } foo::params { $bar = 'baz'}{ { code} } In this case, I would like to be able to declare that the {{$foo::params::bar}} variable is available for use but it is not a {{parameter}}.Ideally, this would be documented with the {{@!accessor [r]}} method, but, when I attempted to use this, an error was thrown.Presently, I'll continue using {{@param}} but it is inherently incorrect and a more correct alternative should be supplied.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-150) README links broken after being HTMLfied
Title: Message Title William Hopper commented on PDOC-150 Re: README links broken after being HTMLfied David Hollinger III it sounds like you may be talking about this issue which I raised against YARD: https://github.com/lsegal/yard/issues/1032. Does that look right? It may be an issue with redcarpet, our markdown processing library. YARD delegates rendering markup to HTML to the markdown library. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-4933) Remove cfacter setting
Title: Message Title William Hopper commented on PUP-4933 Re: Remove cfacter setting PR is up against master at https://github.com/puppetlabs/puppet/pull/5412 but we can't merge it until we're ready for master to become 5.0. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Change By: William Hopper Status: Ready for CI Test Assignee: William Hopper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Status: Ready for CI Test Assignee: William Hopper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6963
Puppet doesn't detect systemd as default service provider on CoreOS
Change By:
William Hopper
Acceptance Criteria:
Puppet should use the systemd service provider to query and interact with services in CoreOS. This can be verified by running {{puppet resource service --param provider}} to see which provider is being used to manager services.
Release Notes Summary:
Previously, the systemd service provider did not specify itself as the default for CoreOS systems. Since systemd is the default service manager in CoreOS, this change updates the provider to add the CoreOS family to its defaults.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group
Jira (PUP-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Change By: William Hopper Assignee: William Hopper Team: Puppet Developer Support Sprint: PDS 2016-12-14 Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6963) Puppet doesn't detect systemd as default service provider on CoreOS
Title: Message Title William Hopper updated an issue Puppet / PUP-6963 Puppet doesn't detect systemd as default service provider on CoreOS Change By: William Hopper Labels: maintenance Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper updated an issue Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Release Notes Summary: Previously, Puppet did not appropriately quote the RPM query string when determining package state with the RPM provider. This caused stale locks to be left on the RPM database when large volumes of RPM queries were run. This change adds the necessary quotes to the query to prevent this from happening. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper updated an issue Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6844
Ignore mercurial artifacts (.hg) when downloading plugins
Change By:
William Hopper
Acceptance Criteria:
When pluginsyncing, no files with the {{.hg}} extension should be downloaded.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title William Hopper updated an issue Puppet / PUP-6844 Ignore mercurial artifacts (.hg) when downloading plugins Change By: William Hopper Release Notes Summary: This change updates the list of file extensions which should be ignored when downloading plugins via pluginsync to also ignore Mercurial (.hg) artifacts. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6844 Ignore mercurial artifacts (.hg) when downloading plugins Change By: William Hopper Status: Ready for CI Test Assignee: William Hopper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6933) Puppet tests fail with 'environment env2 enviroment_key lookup failed'
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6933 Puppet tests fail with 'environment env2 enviroment_key lookup failed' Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-137) Release puppet-strings 1.0.0
Title: Message Title William Hopper commented on PDOC-137 Re: Release puppet-strings 1.0.0 5. Tag the release Tagged 1.0.0 at 1bd8575acb82d283412228516a6aeeb0e0259bf8 6. Build and smoke test gem Built gem and tested on Centos 7 by running against puppetlabs-apache with FOSS puppet-agent latest. 7. Push tag to GitHub Tag pushed and gem pushed. 8. Send out announcements Announcements sent to announce, dev and users mailing lists. 9. Close all resolved tickets in JIRA. Done. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-133) Edit Strings README
Title: Message Title William Hopper assigned an issue to Jean Bond Released with puppet-strings 1.0.0. Puppet Strings / PDOC-133 Edit Strings README Change By: William Hopper Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-137) Release puppet-strings 1.0.0
Title: Message Title William Hopper assigned an issue to William Hopper Released with puppet-strings 1.0.0. Puppet Strings / PDOC-137 Release puppet-strings 1.0.0 Change By: William Hopper Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-137) Release puppet-strings 1.0.0
Title: Message Title William Hopper commented on PDOC-137 Re: Release puppet-strings 1.0.0 Skipping subtasks in favor or just commenting here. 1. Is the code ready for release? Changelog entry added for 1.0.0 and version bumped in the gemspec. Tests are all passing, and all tickets are resolved for this release. See https://tickets.puppetlabs.com/issues/?filter=23607. 2. Reconcile git commits and JIRA tickets All commits have associated JIRA tickets (except maint commits). 3. Is the Jira tidy-up done for this release and prepared for the next one? We now have PDOC version 1.0.1 in JIRA. Filters: Fixed in 1.0.0: https://tickets.puppetlabs.com/issues/?filter=23607 Introduced in 1.0.0: https://tickets.puppetlabs.com/issues/?filter=23606 4. Prepare long form release notes: Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-136 Strings doesn't recognize `>> Type` syntax for return type of puppet language functions Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-138) Update strings forge page to point to current
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-138 Update strings forge page to point to current Change By: William Hopper Story Points: 1 Sprint: PDS 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-138) Update strings forge page to point to current
Title: Message Title William Hopper commented on PDOC-138 Re: Update strings forge page to point to current Just kidding, with Jesse's help I figured out how to do this. For future reference, the preferred way to deprecate a module on the forge is as follows. Download the tarball. Replace the README with a note saying that the module is deprecated and where to find it now. Update the module metadata.json to have a version of 999.999.999, and add "[deprecated]" to the beginning of the summary. Then, push the module to the forge. See https://forge.puppet.com/puppetlabs/strings. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-138) Update strings forge page to point to current
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-138 Update strings forge page to point to current Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-138) Update strings forge page to point to current
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-138 Update strings forge page to point to current Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-138) Update strings forge page to point to current
Title: Message Title William Hopper commented on PDOC-138 Re: Update strings forge page to point to current Lindsey Smith is this a blocker for the release? And did we decide how we wanted to do this? (Delete current strings module on forge, replace with stub module that points to the gem. maybe?) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-143) Add Windows information to Strings README
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-143 Add Windows information to Strings README Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper updated an issue Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Story Points: 1 Team: Puppet Developer Support Sprint: PDS 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6663) Large volumes of RPM queries leave stale locks on the rpm database
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6663 Large volumes of RPM queries leave stale locks on the rpm database Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6844) Ignore mercurial artifacts (.hg) when downloading plugins
Title: Message Title William Hopper updated an issue Puppet / PUP-6844 Ignore mercurial artifacts (.hg) when downloading plugins Change By: William Hopper Summary: Ignore mercurial artifacts (.hg) when downloading plugins Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6844) Ignore mercurial artifacts (.hg)
Title: Message Title William Hopper updated an issue Puppet / PUP-6844 Ignore mercurial artifacts (.hg) Change By: William Hopper Story Points: 1 Team: Puppet Developer Support Sprint: PDS 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6844) Ignore mercurial artifacts (.hg)
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6844 Ignore mercurial artifacts (.hg) Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1485) Facter 3 reports kernel version for os release on Amazon Linux
Title: Message Title William Hopper assigned an issue to qa Facter / FACT-1485 Facter 3 reports kernel version for os release on Amazon Linux Change By: William Hopper Status: Ready for CI Test Assignee: William Hopper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6924) Fix issues with bad separation of concern between Array, Hash and Collection types
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6924 Fix issues with bad separation of concern between Array, Hash and Collection types Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6882) Incorrect handling of escape sequence precedence
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6882 Incorrect handling of escape sequence precedence Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6926) lookup should allow rich data as values
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6926 lookup should allow rich data as values Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6821) binary_file() file not found: error message unclear
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6821 binary_file() file not found: error message unclear Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6917) the 'site' keyword cannot be used as an attribute name when app_management is on
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6917 the 'site' keyword cannot be used as an attribute name when app_management is on Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6921) Improve separation of concern between String and Enum types
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6921 Improve separation of concern between String and Enum types Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run Yeah, they should be dealt with in the best way puppet can (systemd kind of breaks some of puppet's abstractions sometimes). For most cases, we handle the state by looking at the return code of is-enabled. This mostly works except for states like indirect and masked, which are special. If you come across any other states that don't work correctly, we'd really appreciate it if you file another ticket for them. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6759
systemd provider does not understand "indirect" status / tries to turn off service on each run
Change By:
William Hopper
Acceptance Criteria:
The {{rpcbind}} service on RedHat 7 should show up as {{enabled => false}} when puppet is run with {{puppet resource service rpcbind}}.
Labels:
maintenance provider systemd
Story Points:
1
Release Notes Summary:
The systemd provider now considers services with the 'indirect' enabled state to be disabled.
Team:
Agent & Platform Puppet Developer Support
Sprint:
PDS 2016-11-30
Release Notes:
Bug Fix
Add Comment
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Change By: William Hopper Assignee: Kylo Ginsberg William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title William Hopper commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run Robert Rosengren my understanding of the indirect status (as detailed in https://www.freedesktop.org/software/systemd/man/systemctl.html) is that we should simply return false for is_enabled? when we come across such a service. Does that sound correct to you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1485) Facter 3 reports kernel version for os release on Amazon Linux
Title: Message Title William Hopper updated an issue Facter / FACT-1485 Facter 3 reports kernel version for os release on Amazon Linux Change By: William Hopper Fix Version/s: FACT 3.5.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1485) Facter 3 reports kernel version for os release on Amazon Linux
Title: Message Title William Hopper updated an issue Facter / FACT-1485 Facter 3 reports kernel version for os release on Amazon Linux Change By: William Hopper Labels: maintenance Story Points: 1 Team: Puppet Developer Support Sprint: PDS 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1485) Facter 3 reports kernel version for os release on Amazon Linux
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-1485 Facter 3 reports kernel version for os release on Amazon Linux Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-137) Release puppet-strings 1.0.0
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-137 Release puppet-strings 1.0.0 Issue Type: Task Assignee: William Hopper Created: 2016/11/16 2:26 PM Fix Versions: PDOC 1.0.0 Priority: Normal Reporter: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet B
Jira (PUP-6244) Acceptance: fix module upgrade tests
Title: Message Title William Hopper updated an issue Puppet / PUP-6244 Acceptance: fix module upgrade tests Change By: William Hopper Fix Version/s: PUP 4.y Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6244) Acceptance: fix module upgrade tests
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-6244 Acceptance: fix module upgrade tests Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6244) Acceptance: fix module upgrade tests
Title: Message Title William Hopper updated an issue Puppet / PUP-6244 Acceptance: fix module upgrade tests Change By: William Hopper Sprint: PDS 2016-11-30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-125) JSON: Splitting function signatures into two places is awkward
Title: Message Title William Hopper assigned an issue to qa Puppet Strings / PDOC-125 JSON: Splitting function signatures into two places is awkward Change By: William Hopper Status: Ready for Merge Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper assigned an issue to qa Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-129) 4.x function overload tags not parsed if the overload is missing a docstring
Title: Message Title William Hopper assigned an issue to qa Puppet Strings / PDOC-129 4.x function overload tags not parsed if the overload is missing a docstring Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title William Hopper assigned an issue to qa Puppet Strings / PDOC-136 Strings doesn't recognize `>> Type` syntax for return type of puppet language functions Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-125) JSON: Splitting function signatures into two places is awkward
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-125 JSON: Splitting function signatures into two places is awkward Change By: William Hopper Release Notes Summary: This commit adds a new top-level key to the JSON schema for functions: signatures. This key holds all function signature data, and in the case of 4.x functions with multiple dispatches, each overload is present along with each of their parameters and other tags. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Release Notes Summary: This change updates strings to recognize calls to the 'return_type' method within puppet 4.x function dispatches. This information is automatically included in the documentation for the function. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-129) 4.x function overload tags not parsed if the overload is missing a docstring
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-129 4.x function overload tags not parsed if the overload is missing a docstring Change By: William Hopper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-136 Strings doesn't recognize `>> Type` syntax for return type of puppet language functions Change By: William Hopper Release Notes Summary: Puppet 4.8 added the ability to define puppet language functions with return types (PUP-5623). This change updates strings to recognize those return types and automatically inject them into the documentation for the function. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-121) gh-pages commit should reference the source
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-121 gh-pages commit should reference the source Change By: William Hopper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title William Hopper assigned an issue to William Hopper Puppet Strings / PDOC-136 Strings doesn't recognize `>> Type` syntax for return type of puppet language functions Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-136 Strings doesn't recognize `>> Type` syntax for return type of puppet language functions Change By: William Hopper Sprint: PDS 2016-11-16 Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title William Hopper assigned an issue to William Hopper Puppet Strings / PDOC-136 Strings doesn't recognize `>> Type` syntax for return type of puppet language functions Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Sprint: PDS 2016-11-16 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper assigned an issue to William Hopper Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-136) Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Title: Message Title
William Hopper created an issue
Puppet Strings / PDOC-136
Strings doesn't recognize `>> Type` syntax for return type of puppet language functions
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/11/10 1:53 PM
Priority:
Normal
Reporter:
William Hopper
function example(String $name) >> String {
"hello"
}
In this example, >> String says that this function returns a string. Currently, Strings ignores this which requires the user to document the return type with the @return tag.
Jira (PDOC-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-135
Strings doesn't recognize `return_type` in 4.x function dispatch
Change By:
William Hopper
Acceptance Criteria:
Given the following function, strings should correctly identify that the 'subtract_ints` overload returns type 'Numeric'.{code}# Subtracts two things.Puppet::Functions.create_function(:subtract) do # @param x The first integer. # @param y The second integer. # @return Returns x - y. # @example Subtracting two integers. # subtract(5, 1) => 4 dispatch :subtract_ints doparam 'Integer', :xparam 'Integer', :yreturn_type 'Numeric' end def subtract_ints(x, y)x - y endend{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-135) Strings doesn't recognize `return_type` in 4.x function dispatch
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-135 Strings doesn't recognize `return_type` in 4.x function dispatch Issue Type: Bug Assignee: Unassigned Created: 2016/11/10 1:45 PM Priority: Normal Reporter: William Hopper Puppet 4.x API functions can include a return_type 'blah' in each of their dispatches. Strings should use this to document the return type for the overload rather than requiring the type to be documented in the @return tag. Example: # Subtracts two things. Puppet::Functions.create_function(:subtract) do # @param x The first integer. # @param y The second integer.
Jira (PDOC-134) Follow up Strings blog post: delivering docs
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-134 Follow up Strings blog post: delivering docs Issue Type: Task Assignee: Unassigned Created: 2016/11/10 12:54 PM Priority: Normal Reporter: William Hopper Should cover: Delivering Documentation to Users Hosting documentation as github pages Running the Strings web server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
