Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Jesse Scott commented on PUP-10641 Re: Puppet Module Tool gives unhelpful error message for bad module name Jesse Scott What do you think about these HTTP responses? I'm not sure what you mean? Those are the current API responses correct? PMT could dig in to the JSON returned to display the more detailed error messages, but in the case of a module slug being the expected parameter, I agree that PMT should validate the format before even sending the request ideally. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.59877.1417031796000.106615.1609785120077%40Atlassian.JIRA.
Jira (PUP-10387) Remove puppet module build, generate and search actions
Title: Message Title Jesse Scott commented on PUP-10387 Re: Remove puppet module build, generate and search actions Woo! I would say just direct people to visit the Forge in lieu of `puppet module search`. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.350961.1585070066000.52451.1588283160084%40Atlassian.JIRA.
Jira (PDOC-274) Add provider attribute to docs output
Title: Message Title Jesse Scott assigned an issue to Jesse Scott Puppet Strings / PDOC-274 Add provider attribute to docs output Change By: Jesse Scott Assignee: Jesse Scott Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295581.1549669062000.42490.1587428580444%40Atlassian.JIRA.
Jira (PDOC-301) Docs Process Improvements
Title: Message Title Jesse Scott moved an issue Puppet Strings / PDOC-301 Docs Process Improvements Change By: Jesse Scott Key: PUP PDOC - 9425 301 Project: Puppet Strings Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291456.1547157877000.38407.1586907540073%40Atlassian.JIRA.
Jira (PDOC-290) Strings HTML output for functions does not include text from JSON
Title: Message Title Jesse Scott assigned an issue to Jean Bond Puppet Strings / PDOC-290 Strings HTML output for functions does not include text from JSON Change By: Jesse Scott Assignee: Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323051.1567198425000.29912.1582073760286%40Atlassian.JIRA.
Jira (PDOC-290) Strings HTML output for functions does not include text from JSON
Title: Message Title Jesse Scott commented on PDOC-290 Re: Strings HTML output for functions does not include text from JSON Jean Bond to verify if this is still an issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323051.1567198425000.29914.1582073760335%40Atlassian.JIRA.
Jira (PDOC-293) Would like a documentation header generation function for puppet strings
Title: Message Title Jesse Scott commented on PDOC-293 Re: Would like a documentation header generation function for puppet strings Tim Sharpe what do you think about an puppet-lint plugin that could do this? Does that seem like a good fit? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328166.1570213652000.29906.1582073581485%40Atlassian.JIRA.
Jira (FACT-2354) Provide fact fixtures on new facter releases to facterdb
Title: Message Title Jesse Scott commented on FACT-2354 Re: Provide fact fixtures on new facter releases to facterdb Note that the default mapping of Puppet Agent version to Facter version will be automatic in a future release of rspec-puppet-facts. The code has already landed (https://github.com/mcanevet/rspec-puppet-facts/pull/109) but there was some breakage of existing tests so we think it's best if it goes out in a major version bump. That doesn't solve for making sure fact sets are up to date in facterdb though, but we have been tracking that work in https://tickets.puppetlabs.com/browse/PDK-687 and I think Tim Sharpe has done a little bit of work on a solution already, probably be good to sync up with him. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.345749.158135502.23525.1581527160198%40Atlassian.JIRA.
Jira (PDOC-297) Add tag for marking class parameters as "advanced"
Title: Message Title Jesse Scott commented on PDOC-297 Re: Add tag for marking class parameters as "advanced" I agree with Jean Bond's point that this really seems better addressed with words in the parameter description. "advanced" is really subjective and not really useful on it's own. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344978.1580827545000.14032.1580864700363%40Atlassian.JIRA.
Jira (PDOC-287) Ruby 4.x function with single dispatch gets docs generated twice
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-287 Ruby 4.x function with single dispatch gets docs generated twice Change By: Jesse Scott Labels: generated-docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321353.1566119361000.64872.1566344640339%40Atlassian.JIRA.
Jira (PDOC-289) Generate reference docs for core configuration
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-289 Generate reference docs for core configuration Issue Type: New Feature Assignee: Unassigned Created: 2019/08/20 4:41 PM Priority: Normal Reporter: Jesse Scott Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-96 Strings needs to document core puppet references (indirection, configuration, metaparameter, etc) Change By: Jesse Scott Team: Puppet Developer Experience Epic Status: In Progress Epic Name: Strings should document core puppet references Status: Accepted Developing Workflow: Scrum Team Engineering Epic Workflow Issue Type: New Feature Epic Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-96 Strings needs to document core puppet references (indirection, configuration, metaparameter, etc) Change By: Jesse Scott Priority: Minor Normal Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.152194.1473983529000.64856.1566344280583%40Atlassian.JIRA.
Jira (PDOC-96) Strings needs to document core puppet references (indirection, configuration, metaparameter, etc)
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-96 Strings needs to document core puppet references (indirection, configuration, metaparameter, etc) Change By: Jesse Scott Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.152194.1473983529000.64851.1566344220526%40Atlassian.JIRA.
Jira (PDOC-286) Break down PDOC-262 description into individual issues
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-286 Break down PDOC-262 description into individual issues Issue Type: Task Assignee: Unassigned Created: 2019/08/06 4:56 PM Priority: Normal Reporter: Jesse Scott Step one of resolving these issues is breaking down all the individual bugs here into their own tickets. It may end up being that some of the resulting tickets are duplicates of one another but we can figure that out as we triage them. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-285) Infer missing docs types from arguments
Title: Message Title Jesse Scott assigned an issue to Glenn Sarti Puppet Strings / PDOC-285 Infer missing docs types from arguments Change By: Jesse Scott Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318762.1564488282000.45794.1565134860329%40Atlassian.JIRA.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott updated an issue Puppet / PUP-9816 puppet parser validate version 6.6.0 does not accept STDIN properly Added release note summary, there is a lot more detail in the commit message of the PR if needed when writing release notes. Change By: Jesse Scott Release Notes Summary: Resolved an issue where `puppet parser validate` would fail with an error when a valid manifest was passed in via the STDIN pipe. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google
Jira (PUP-9909) Use file_sha256 to verify module tarballs
Title: Message Title Jesse Scott commented on PUP-9909 Re: Use file_sha256 to verify module tarballs To save someone some spelunking, I think most of the changes will be in lib/puppet/forge.rb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317118.1563469306000.21910.1563471060102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Jorie Tappa not sure who I should ping for review of the fix PR ^^ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16660.1563224700099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Opened https://github.com/puppetlabs/puppet/pull/7611 which should resolve this. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16652.1563224580333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly Yes, sorry I did not mean to imply that a blank manifest was the only example. Any manifest that does not produce parse errors will trigger this, of which a blank manifest is the minimal example. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16649.1563224460116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Jesse Scott commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly This seems to only surface when there are no parse errors in the manifest. (E.g. a blank manifest) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16538.1563222480370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-282) No way to output markdown format to stdout
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-282 No way to output markdown format to stdout Issue Type: Bug Assignee: Unassigned Created: 2019/06/25 12:33 PM Priority: Normal Reporter: Jesse Scott The documentation for `puppet strings generate` states: --out PATH - Write selected format to PATH. If no path is designated, strings prints to STDOUT. However when `–format markdown` is specified, the output is written to REFERENCE.md rather than STDOUT and there appears to be no way to override that behavior through the CLI. I think the offending code is https://github.com/puppetlabs/puppet-strings/blob/master/lib/puppet-strings.rb#L39
Jira (PUP-9789) Constants assigned twice emit warning during Litmus use on Windows.
Title: Message Title Jesse Scott commented on PUP-9789 Re: Constants assigned twice emit warning during Litmus use on Windows. We have already removed the monkey patching of those constants in pdk/master and that will be going out in the next PDK release: https://github.com/puppetlabs/pdk/commit/4b02f0c500275b2ef9ae07c36db553de4a5ed5a3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313352.1561054057000.58764.1561414560478%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-259) relax ruby requirement to 2.1.0 from 2.1.9
Title: Message Title Jesse Scott commented on PDOC-259 Re: relax ruby requirement to 2.1.0 from 2.1.9 OK, we updated our travis config to only test on >= 2.1.9 now, but have left the .gemspec requirement at >= 2.1.0 for the time being. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.261734.1529500595000.55371.1561046161181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-259) relax ruby requirement to 2.1.0 from 2.1.9
Title: Message Title Jesse Scott commented on PDOC-259 Re: relax ruby requirement to 2.1.0 from 2.1.9 David Schmitt is this still needed? We would like to actually bump the puppet-strings required ruby version at some point. If it's still needed can you point me to the test cases in the puppet_agent module? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.261734.1529500595000.53543.1560968460659%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title Jesse Scott commented on PDOC-262 Re: Puppet Strings output of Puppet types is inconsistent with puppet doc I converted this to an Epic, next I'm going to start going through and extracting the various bits into their own tickets. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.268188.1533580542000.45775.1560385500368%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-262 Puppet Strings output of Puppet types is inconsistent with puppet doc Change By: Jesse Scott Epic Status: In Progress Epic Name: puppet strings vs. docs Status: Accepted Defining Workflow: Scrum Team Engineering Epic Workflow Issue Type: Story Epic Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received
Jira (PUP-8984) Add JSON output option to `puppet parser validate`
Title: Message Title Jesse Scott commented on PUP-8984 Re: Add JSON output option to `puppet parser validate` Josh Cooper I added release notes this afternoon so this is ready to resolve as far as I know. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.189813.149427962.45610.1560381781978%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8984) Add JSON output option to `puppet parser validate`
Title: Message Title Jesse Scott updated an issue Puppet / PUP-8984 Add JSON output option to `puppet parser validate` Change By: Jesse Scott Release Notes Summary: The `puppet parser validate` subcommand now supports a `--render-as=json` option to output validate errors in a machine readable JSON format.Additionally, when passed multiple target files, `puppet parser validate` will now continue validating additional files after a parse error instead of halting immediately on the first error encountered. (Note: It will still only return a maximum of one parse error per file.) Release Notes: Enhancement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To
Jira (PDOC-271) unicode space causes oddly formatted output / missing text
Title: Message Title Jesse Scott commented on PDOC-271 Re: unicode space causes oddly formatted output / missing text Sorry for the delayed response, but this appears to be an issue in the underlying YARD gem's ability to detect documentation tags that include non-standard whitespace characters. I would suggest following up with https://github.com/lsegal/yard if this continues to be an issue for you. Please feel free to re-open this issue if you are sure it is a problem specific to puppet-strings. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.287706.1544123145000.43312.1560297600644%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-269) Support documenting required modules
Title: Message Title Jesse Scott commented on PDOC-269 Re: Support documenting required modules This is an interesting idea, can you give us some examples of what type of code you are documenting where this would be useful? Is it that you just want more granularity than is expressed in the metadata.json dependencies of a module or are you using this to document role and profile code? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281168.153985289.43281.1560297060403%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-268) Colliding internal anchors on autogenerated pages
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-268 Colliding internal anchors on autogenerated pages Looks like we need to make the Table of Contents anchors use the same disambiguation algorithm as the Forge does for multiple headings with the same text value. We should also investigate if there is a standard for this so we can safely predict what the anchor values will be ahead of time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.280893.1539770862000.43278.1560296760242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1356) Make example strings documentation for a plan
Title: Message Title Jesse Scott updated an issue Puppet Task Runner / BOLT-1356 Make example strings documentation for a plan Change By: Jesse Scott Reporter: Jesse Scott Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310714.1559175692000.26749.1559175720999%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1356) Make example strings documentation for a plan
Title: Message Title Jesse Scott created an issue Puppet Task Runner / BOLT-1356 Make example strings documentation for a plan Issue Type: Task Assignee: Unassigned Created: 2019/05/29 5:21 PM Priority: Normal Reporter: Jesse Scott Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDOC-267) Grouping of parameters
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-267 Grouping of parameters Ewoud Kohl van Wijngaarden sorry for the delay in responding to this request! Could you confirm if this is still something you would find useful and if so, provide a concrete example of some code that makes use of a parameter grouping syntax? If this is something that would require extensive customization to YARD, we probably won't have the bandwidth to address it any time soon, but given an example we might be able to come up with something that would work for you. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.275678.1536876963000.23924.1559084700305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-262 Puppet Strings output of Puppet types is inconsistent with puppet doc Going to create an epic and break this down into smaller individual tickets Change By: Jesse Scott Issue Type: Bug Story Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit
Jira (PDOC-256) REFERENCE.md in CI
Title: Message Title Jesse Scott assigned an issue to Jesse Scott Puppet Strings / PDOC-256 REFERENCE.md in CI Change By: Jesse Scott Assignee: Eric Putnam Jesse Scott Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.258793.1528149696000.23689.1559081160684%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-256) REFERENCE.md in CI
Title: Message Title Jesse Scott assigned an issue to Unassigned Puppet Strings / PDOC-256 REFERENCE.md in CI Change By: Jesse Scott Assignee: Jesse Scott Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.258793.1528149696000.23692.1559081160825%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-188) Document our own modules with Puppet Strings
Title: Message Title Jesse Scott commented on PDOC-188 Re: Document our own modules with Puppet Strings Davin Hanlon Are there still any plans for the content teams to adopt puppet-strings in more modules? (I hope so! Please let PDE know if there are functional blockers to that work in puppet-strings.) If so, does it make sense for the unresolved tickets in the epic to move into the MODULES project or similar? We'd like to make the PDOC project focused specifically on puppet-strings features, bugs, etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-98) Puppet Strings Maintenance
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-98 Puppet Strings Maintenance Change By: Jesse Scott Epic Name: Puppet strings potential future work Strings Maintenance Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-98) Puppet Strings Maintenance
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-98 Puppet Strings Maintenance Change By: Jesse Scott Summary: Puppet strings potential future work Strings Maintenance Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-98) Puppet Strings Maintenance
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-98 Puppet Strings Maintenance Change By: Jesse Scott Epic Status: To Do In Progress Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-278) Update HTML templates to reflect "@api private" resources
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-278 Update HTML templates to reflect "@api private" resources Issue Type: Improvement Assignee: Unassigned Created: 2019/05/02 1:05 PM Priority: Normal Reporter: Jesse Scott https://github.com/puppetlabs/puppet-strings/pull/157 added basic support for the "@api private" tag to the Puppet code objects in puppet-strings and updated the markdown rendering templates to be aware of private code objects. However the HTML templates have not been updated accordingly, we should update those templates so that the generated HTML documentation indicates which Puppet code objects are private versus public. Add Comment This message was
Jira (PDOC-277) Ensure that multiline examples are correctly parsed
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-277 Ensure that multiline examples are correctly parsed Issue Type: Bug Assignee: Unassigned Created: 2019/05/01 3:53 PM Priority: Normal Reporter: Jesse Scott Follow up to PDOC-265 From Henrik's comment on that issue: Examples in regsubst.rb (the 4.x implementation) looks like this: # @example Get the third octet from the node's IP address: # # ```puppet # $i3 = regsubst($ipaddress,'^(\\d+)\\.(\\d+)\\.(\\d+)\\.(\\d+)$','\\3') # ``` # # @example Put angle brackets around each octet in the node's IP address:
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Jesse Scott commented on PDOC-265 Re: @example doesn't work with 4.x functions Jean Bond It sounds like maybe the original issue (that puppet-strings didn't recognize the @example tag at all for 4.x style functions) has been fixed but there may still be a bug in how it's able to capture example content that contains blank lines? If that's the case can we open a new ticket specifically about that issue and close this one? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-235) Strings Next
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-235 Strings Next Change By: Jesse Scott Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-47) Puppet types and providers need in page navigation menu
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-47 Puppet types and providers need in page navigation menu Change By: Jesse Scott Labels: UI Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-167) Problem with file managed with --files (in .yardocs or using rake task)
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-167 Problem with file managed with --files (in .yardocs or using rake task) Change By: Jesse Scott Component/s: CLI Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-227) use markdown as default/only markup type
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-227 use markdown as default/only markup type Change By: Jesse Scott Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-89) Strings should exit 1 when an error occurs
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-89 Strings should exit 1 when an error occurs Change By: Jesse Scott Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-123) Support groups of parameters
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-123 Support groups of parameters Change By: Jesse Scott Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-236) @!accessor directive for params.pp (or something)
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-236 @!accessor directive for params.pp (or something) Change By: Jesse Scott Team: Modules Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-189) PDK Integration
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-189 PDK Integration Change By: Jesse Scott Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-189) PDK Integration
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-189 PDK Integration Change By: Jesse Scott Team: Modules Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-189) PDK Integration
Title: Message Title Jesse Scott assigned an issue to Unassigned Puppet Strings / PDOC-189 PDK Integration Change By: Jesse Scott Assignee: Bryan Jen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-219) Puppet Strings 2.1.0
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-219 Puppet Strings 2.1.0 Change By: Jesse Scott Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-134) evangelize "how to puppet-strings"
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-134 evangelize "how to puppet-strings" Change By: Jesse Scott Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-134) evangelize "how to puppet-strings"
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-134 evangelize "how to puppet-strings" Change By: Jesse Scott Summary: Follow up Strings blog post: delivering docs evangelize "how to puppet-strings" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-134) evangelize "how to puppet-strings"
Title: Message Title Jesse Scott updated an issue Puppet Strings / PDOC-134 evangelize "how to puppet-strings" Change By: Jesse Scott Sprint: PDOC - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9364) puppet module install is really slow
Title: Message Title Jesse Scott commented on PUP-9364 Re: puppet module install is really slow PMT could also be updated to request up to 100 entries at a time, trade off a larger payload size for fewer total requests. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9364) puppet module install is really slow
Title: Message Title Jesse Scott commented on PUP-9364 Re: puppet module install is really slow Yes, the v3 API (released in 2013) has always included those fields in the default response. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9364) puppet module install is really slow
Title: Message Title Jesse Scott commented on PUP-9364 Re: puppet module install is really slow Yes, unfortunately the original v3 api schema included that data so we can't filter it out by default. However we can update PMT to skip those fields by adding "exclude_fields" to the query params: https://forgeapi.puppet.com/v3/releases?module=puppetlabs-stdlib_by=version_fields=readme,changelog,license Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8984) Add JSON output option to `puppet parser validate`
Title: Message Title Jesse Scott updated an issue Puppet / PUP-8984 Add JSON output option to `puppet parser validate` Change By: Jesse Scott Summary: Puppet Add JSON output option to `puppet parser validate does not respect --render-as ` Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8984) Puppet parser validate does not respect --render-as
Title: Message Title Jesse Scott moved an issue Puppet / PUP-8984 Puppet parser validate does not respect --render-as Change By: Jesse Scott Issue Type: Bug Improvement Key: PDK PUP - 800 8984 Project: Puppet Development Kit Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8698) puppet module generate broken w/o stdlib
Title: Message Title
Jesse Scott commented on PUP-8698
Re: puppet module generate broken w/o stdlib
Hi Joaquin Menchaca, You are correct that the `puppet module generate` command, by default, generates a module with a dependency on the puppetlabs-stdlib module. That dependency is located in the modules metadata.json file and can be safely removed if desired. However it appears that in this case, your module still applied the desired changes. The only output related to the stdlib dependency that I see is a warning (not an error). Was there other behavior you observed that suggested the module was not doing what you expected? The line below indicates that Puppet managed the content of the templated file:
Notice: /Stage[main]/Bar/File[/var/www/html/index.html]/content: content changed '{md5}c32ad802df5abca941d784abf642e7fd' to '{md5}2d60ab375367b3e2996c7c1803009d55'
You may also want to investigate using the Puppet Development Kit to create and test modules in the future. PDK incorporates the latest module development patterns and best practices from the community:
Download PDK: https://puppet.com/download-puppet-development-kit
Docs: https://puppet.com/docs/pdk/1.x/pdk.html
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8616) puppet module upgrade crashes
Title: Message Title Jesse Scott commented on PUP-8616 Re: puppet module upgrade crashes Yes the value of the "next" field in the "pagination" section is "false" when it should be "null". It looks like this bug was supposed to be resolved in the latest release of that gem though, are you using version 1.10.1? https://github.com/unibet/puppet-forge-server/releases/tag/1.10.1 https://rubygems.org/gems/puppet-forge-server/versions/1.10.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8616) puppet module upgrade crashes
Title: Message Title Jesse Scott commented on PUP-8616 Re: puppet module upgrade crashes Nelson Araujo you should be able to use curl or your web browser to make a request directly to the API and get the JSON back. Something like: curl "https://forgeapi.puppet.com/v3/modules?limit=1" > tmp/forge_api.json with the URI of your local Forge mirror and desired output file path substituted. It sounds like the maintainer of that gem could make an update to return the correct pagination values, we are also looking into making the module tool more tolerant of unexpected values in the API response in a future Puppet release. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options,
Jira (PUP-8616) puppet module upgrade crashes
Title: Message Title Jesse Scott commented on PUP-8616 Re: puppet module upgrade crashes Can we see an example of the API responses sent by your private Forge instance? I suspect one of the pagination fields is "false" when it should be "null". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8517) module install against local repository fails
Title: Message Title
Jesse Scott commented on PUP-8517
Re: module install against local repository fails
Barry Haycock in that other ticket, the issued ended up being that their custom Forge implementation was returning an unexpected value for one of the pagination keys. What does your implementation of the Forge API return in that section? Example from the official API:
"pagination": {
"limit": 20,
"offset": 0,
"first": "/v3/releases?module=puppetlabs-motd=20=0",
"previous": null,
"current": "/v3/releases?module=puppetlabs-motd=20=0",
"next": null,
"total": 12
}
Is it possible that your implementation is returning "false" for the "previous"/"next" keys instead of "null" when you've reached the ends of the result set?
Jira (PUP-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Added another PR to fix the padding inconsistency, not sure why I didn't observe this in my initial testing: https://github.com/puppetlabs/puppet/pull/6519 I think we can still close this ticket and just let that PR get merged whenever, it's a very minor 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 (PUP-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott updated an issue Puppet / PUP-8082 Add warning to Puppet Module Tool when installing a deprecated module Change By: Jesse Scott Release Notes Summary: The Puppet Module Tool (PMT) will now warn users when interacting with Forge modules that have been "deprecated" by their author. 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Verified that the update is in that build, did discover a minor formatting issue on the search results but I don't think fixing it is a super-high priority, I'll spend a little time investigating a fix though. 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Josh Cooper Thanks, I'll work on release notes and verification tomorrow. 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-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-193 Evaluate using `yard i18n` to extract doc string content into POT files Issue Type: Improvement Assignee: Unassigned Created: 2017/12/13 6:03 AM Priority: Normal Reporter: Jesse Scott Since 0.8.0 yard has included an i18n subcommand to place all the doc strings into a .pot file. It seems like if we just run this automatically when a user invokes puppet strings that would go a long way to enabling i18n workflows for module documentation. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Thanks Henrik Lindberg! Which pipeline should I check to make sure it got through CI? 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-7546) PMT Improvements
Title: Message Title Jesse Scott commented on PUP-7546 Re: PMT Improvements Josh Cooper As we start working on some of these, we may need a little help getting up to speed on the puppetlabs/puppet contribution process (testing, PRs, promotions, etc.) Is that something you can help with or is it all well documented somewhere we can look up? 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-190) Create Style Guide Proposal
Title: Message Title Jesse Scott commented on PDOC-190 Re: Create Style Guide Proposal See https://tickets.puppetlabs.com/browse/PDOC-161 for the origins of the summary tag. 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-180) puppet-strings Tasks support
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-180 puppet-strings Tasks support Issue Type: Epic Assignee: Unassigned Created: 2017/10/27 11:18 AM Priority: Normal Reporter: Jesse Scott puppet-strings should know how to document tasks in a module based on task metadata Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott moved an issue Puppet / PUP-8082 Add warning to Puppet Module Tool when installing a deprecated module Change By: Jesse Scott Key: PF PUP - 1316 8082 Project: Puppet Forge [Internal] 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Jesse Scott commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 That PR also updates the debug log output to more accurately reflect the URI being requested. 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Jesse Scott commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 Opened https://github.com/puppetlabs/puppet/pull/6287 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Jesse Scott commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 It is definitely an issue with double encoding the URI for the subsequent pages. I've got a puppet fix mostly worked up which I will PR tomorrow. We can also mitigate the issue by changing the default ordering from the Forge API so that the latest release is always on the first page of results. Since there is a param available for requesting the results in a specific order, I feel like it's reasonable to change the default since clients should already be requesting things in a specific order if it's important for their app. That Forge change can also go out tomorrow (see PF-1431). 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-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Jesse Scott commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 Can we see what IP "forgeapi.puppet.com" is resolving to during the tests on those hosts? 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Jesse Scott assigned an issue to Thomas Hallgren Puppet / PUP-7431 Upgrade vendored version of SemanticPuppet Change By: Jesse Scott Assignee: Jesse Scott Thomas Hallgren 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Jesse Scott commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet I can add them, I just need to know if they have accounts on Rubygems.org already and if so, what the associated email addresses are. 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-7431) Upgrade vendored version of SemanticPuppet
Title: Message Title Jesse Scott commented on PUP-7431 Re: Upgrade vendored version of SemanticPuppet Ummm, I think I have released it in the past but I'm not sure the responsibility falls clearly on anyone. Probably would make sense to add Thomas/Henrik to the owners on Rubygems so they could release it. 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 Jesse Scott commented on PDOC-125 Re: JSON: Splitting function signatures into two places is awkward That sounds reasonable to me. Having one place to look for signatures (that is always a list, even if it only has one item) sounds a lot better than a conditional. 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-1830) Create a Catalog Meta Model
Title: Message Title Jesse Scott updated an issue Puppet / PUP-1830 Create a Catalog Meta Model Change By: Jesse Scott Sprint: PDS 2016-11-02 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-1830) Create a Catalog Meta Model
Title: Message Title Jesse Scott updated an issue Puppet / PUP-1830 Create a Catalog Meta Model Change By: Jesse Scott Sprint: PDS 2016-11-02 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-80) Installation overwrites facter in PE 3.8.3
Title: Message Title Jesse Scott commented on PDOC-80 Re: Installation overwrites facter in PE 3.8.3 Maybe this can be worked around by using the puppet-agent vendored "gem" command to install puppet-strings? Then it should see the existing puppet/facter gems and consider that dependency satisfied already. 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-6588) Allow context path in http_proxy
Title: Message Title Jesse Scott commented on PUP-6588 Re: Allow context path in http_proxy Jainish Shah what exactly are you trying to do? It seems like artifactory does not yet support emulating the Puppet Forge API (https://www.jfrog.com/jira/browse/RTFACT-5934) so I'm not sure how this would work? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-6341) SemanticPuppet::Dependency::ModuleRelease should implement operator eql? and operator '=='
Title: Message Title Jesse Scott commented on PUP-6341 Re: SemanticPuppet::Dependency::ModuleRelease should implement operator eql? and operator '==' semantic_puppet-0.1.3, which includes this fix, has been released and pushed to rubygems. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-6096) Add Acceptance Test for Installing Module with Long Paths with PMT
Title: Message Title Jesse Scott assigned an issue to Zach Reichert Puppet / PUP-6096 Add Acceptance Test for Installing Module with Long Paths with PMT Change By: Jesse Scott Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-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-3767) PMT build action should warn when it encounters unrecognized keys in metadata.json
Title: Message Title Jesse Scott created an issue Puppet / PUP-3767 PMT build action should warn when it encounters unrecognized keys in metadata.json Issue Type: Improvement Assignee: Unassigned Components: PMT Created: 2014/12/15 11:33 AM Priority: Normal Reporter: Jesse Scott Some sort of indication during pmt build about unrecognized metadata.json keys would help module authors detect problems before publishing. For example, in a dependency: having a valid name but a typo in the version_requirement key will currently result an unbounded dependency. Add Comment
Jira (PUP-2882) PMT upgrade command returns an error when trying to upgrade a module with only one release
Title: Message Title Jesse Scott created an issue Puppet / PUP-2882 PMT upgrade command returns an error when trying to upgrade a module with only one release Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Components: PMT Created: 02/Jul/14 1:19 PM Priority: Normal Reporter: Jesse Scott When you use the puppet module upgrade command to upgrade a module that has only one published release, it reports that there are no releases available for that module instead of telling you that you already have the latest version. $ bin/puppet module install ghoneycutt/sysklogd Notice: Preparing to install into /Users/jesse/sandbox/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /Users/jesse/sandbox/puppet/modules └── ghoneycutt-sysklogd (v1.0.0) $ bin/puppet module upgrade ghoneycutt/sysklogd Notice: Preparing to upgrade 'ghoneycutt-sysklogd' ... Notice: Found 'ghoneycutt-sysklogd' (v1.0.0) in /Users/jesse/sandbox/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Could not upgrade 'ghoneycutt-sysklogd' (v1.0.0 - latest) No releases are available from https://forgeapi.puppetlabs.com Does 'ghoneycutt-sysklogd' have at least one published release?
Jira (PUP-2312) puppet module search for module by name fails
Title: Message Title Jesse Scott commented on an issue Re: puppet module search for module by name fails Fine with me. Add Comment Puppet / PUP-2312 puppet module search for module by name fails On PE, the following search fails: puppet module search puppetlabs-mysql I expect it to find the module named puppetlabs-mysql. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
