Jira (PDOC-184) Add ability to generate Markdown
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-184 Add ability to generate Markdown Change By: Hailee Kenney We want to add Markdown as a third output option for strings (right now the only options are HTML and JSON). Markdown generation will probably look something like the way we generate JSON using the YARD registry https://github.com/puppetlabs/puppet-strings/blob/master/lib/puppet-strings/json.rb 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-140) Strings-generated content on the Forge
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-140 Strings-generated content on the Forge Change By: Hailee Kenney Probably in the form of a "references" tab or something that displays the JSON output of strings. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-185) Keep generated content in sync with static content in README automatically
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-185 Keep generated content in sync with static content in README automatically Change By: Hailee Kenney Rolling out strings will eventually require us to remove the long reference sections from module READMEs. This will be a big change for a lot of users, so we'll want to make sure that strings docs are 100% ready to go before we start removing reference sections.As such, it will be necessary to have an interim step where we have docs both in the README and as comments in the source code. In order to manage this reasonably, we'll want to have the comments be the source of truth and run strings against them to update the README reference section accordingly. The goal of this ticket is to add a feature that will let us do that. 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-188) Document our own modules with Puppet Strings
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-188 Document our own modules with Puppet Strings Change By: Hailee Kenney Eventually we should work towards Strings compatible comments in all puppetlabs supported modules (as this is the standard we're proposing other people hold their modules too to ). We should start though by picking a list of several modules, at least one or two of which are rather complicated, to document with Strings. That way, users have examples to look to when trying to figure out how to document their own modules. 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-188) Document our own modules with Puppet Strings
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-188 Document our own modules with Puppet Strings Change By: Hailee Kenney Eventually we should work towards Strings compatible comments in all puppetlabs supported modules (as this is the standard we're proposing other people hold their modules too). We should start though by picking a list of several modules, at least one or two of which are rather complicated, to document with Strings. That way, users have examples to look to when trying to figure out how to document their own modules. 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-186) Comprehensive strings style guide
Title: Message Title Hailee Kenney commented on PDOC-186 Re: Comprehensive strings style guide Just a note that this is something we should probably interface with Vox about. They've been using Strings in their modules for a while and probably have some good ideas around best practices we should take into account. 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-183) Puppet Strings 2.0.0 (?)
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 (?) Change By: Hailee Kenney The next steps to get strings to a state where we and the community agree it's actually complete.More details in this doc:https://docs.google.com/document/d/1Tj1Y_RxKzP5lGJKXwxQWzNpYu_wVMpYF4JTuhkc2oqw/edit 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-189) PDK Integration
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-189 PDK Integration Change By: Hailee Kenney Key: MODULES PDOC - 5825 189 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-188) Document our own modules with Puppet Strings
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-188 Document our own modules with Puppet Strings Change By: Hailee Kenney Key: MODULES PDOC - 5820 188 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-184) Add ability to generate Markdown
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-184 Add ability to generate Markdown Change By: Hailee Kenney Summary: Add ability to generate mark down Markdown 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-187) Strings 2.0.0 improvements blog post
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-187 Strings 2.0.0 improvements blog post Change By: Hailee Kenney Key: MODULES PDOC - 5824 187 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-186) Comprehensive strings style guide
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-186 Comprehensive strings style guide Change By: Hailee Kenney Key: MODULES PDOC - 5819 186 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-185) Keep generated content in sync with static content in README automatically
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-185 Keep generated content in sync with static content in README automatically Change By: Hailee Kenney Summary: Keep generated content in sync with static content in readme README automatically 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-185) Keep generated content in sync with static content in readme automatically
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-185 Keep generated content in sync with static content in readme automatically Change By: Hailee Kenney Key: MODULES PDOC - 5823 185 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-184) Add ability to generate mark down
Title: Message Title Hailee Kenney moved an issue Puppet Strings / PDOC-184 Add ability to generate mark down Change By: Hailee Kenney Issue Type: Story New Feature Key: MODULES PDOC - 5821 184 Project: Forge Modules Puppet Strings Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-183) Puppet Strings 2.0.0 (?)
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 (?) Issue Type: Epic Assignee: Unassigned Created: 2017/11/02 9:44 AM Priority: Normal Reporter: Hailee Kenney 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
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Hailee Kenney commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 Hey Kenn Hussey, apologies for the confusion, but this ticket was assigned to me when I was investigating this issue but I wasn't actually involved with the fix. Ethan Brown or Jesse Scott would have a better idea on release notes than I do. 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 Hailee Kenney assigned an issue to Unassigned Puppet / PUP-8008 puppet module install fails to install apt 4.2.0 Change By: Hailee Kenney Assignee: Hailee Kenney 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 (PDB-3289) db creation fails with hard-coded locale
Title: Message Title Hailee Kenney commented on PDB-3289 Re: db creation fails with hard-coded locale Hey Ryan Senior, we were doing some grooming of the postgres backlog and came across this ticket. It appears to be an issue in puppetdb rather than the module so we've migrated the ticket to the PDB project. Let me know if you have any questions! 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 (PDB-3289) db creation fails with hard-coded locale
Title: Message Title Hailee Kenney moved an issue PuppetDB / PDB-3289 db creation fails with hard-coded locale Change By: Hailee Kenney Component/s: puppetdb Key: MODULES PDB - 1509 3289 Project: Forge Modules PuppetDB 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 Hailee Kenney created an issue Puppet Strings / PDOC-156 Support @api tag for classes (in addition to functions) Issue Type: Improvement Assignee: Unassigned Created: 2017/01/11 12:17 PM Priority: Normal Reporter: Hailee Kenney 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
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better Bill Niestempski No worries at all! Sorry there's been so many delays on this ticket. Usually if something is unassigned and in "ready for merge" that means it's waiting for a second pair of eyes to get the pull request merged. Now that the release is out this should get moving again soon. 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-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better Bill Niestempski the ticket isn't assigned to anyone right now because the pull request is waiting for review. We've been really behind on reviewing/merging pull requests this sprint due to some issues with the release. Someone should be reviewing the pull request soon so it can be merged. Sorry for the delay! 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 (FACT-1368) Windows output does not correctly print unicode snowman
Title: Message Title Hailee Kenney assigned an issue to Unassigned Facter / FACT-1368 Windows output does not correctly print unicode snowman Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1272) Create Facts schema translation tooling
Title: Message Title Hailee Kenney commented on FACT-1272 Re: Create Facts schema translation tooling Here's my best guess for answering these questions, feel free to chime in Michael Smith. But I agree, maybe we would benefit from a meeting to chat about all this? It would be good to get a little more info on this file. What are you planning to target for translation? I think the description, resolution, and caveats sections for each fact would be useful to extract for translation. Will all of the keys need to stay in English? Yes, I think the keys will have to remain in English, I don't know if it makes much sense to try and translate them. Will we translate all of the values, or are there some values that need to be excluded from translation? From this yaml file I think we really only want to translate the description, resolution, and caveats for each fact. So this would exclude any of the other values like "type" and "hidden" for example. Is this yaml file just for the core facts that ship in Facter? I believe it is only the core facts that ship in Facter. Do we have modules or other plugins that add their own facts? How do users access the fact documentation? I think the idea is that we would add new translated schemas to go along with this existing one. They could live in the schemas directory and probably also be used to generate docs? Not totally sure on this though. Is this YAML file only used to auto-generate https://docs.puppet.com/facter/3.3/core_facts.html, or are the values also used elsewhere? I believe it's also used in our Facter unit tests, but I don't know of any uses beyond these two. Add Comment
Jira (FACT-1272) Create Facts schema translation tooling
Title: Message Title Hailee Kenney commented on FACT-1272 Re: Create Facts schema translation tooling Michael Smith by "schema" do you mean like JSON schema? I think I need a few more specifics in order to get started on this 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 (FACT-1272) Create Facts schema translation tooling
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1272 Create Facts schema translation tooling Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1368) Windows output does not correctly print unicode snowman
Title: Message Title Hailee Kenney commented on FACT-1368 Re: Windows output does not correctly print unicode snowman I think this leaves two questions which are: Do we want to document this somewhere or put together some kind of guide for supporting unicode output on Windows? Do we want an acceptance test for this? 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 (FACT-1368) Windows output does not correctly print unicode snowman
Title: Message Title Hailee Kenney commented on FACT-1368 Re: Windows output does not correctly print unicode snowman Just recording our findings in detail for the sake of being thorough: PS C:\Users\HAIL 9000\facter> $env:FACTER_zeta_pilot カミーユ ビダン PS C:\Users\HAIL 9000\facter> .\release\bin\facter.exe zeta_pilot カミーユ ビダン PS C:\Users\HAIL 9000\facter> [Console]::OutputEncoding = [System.Text.Encoding]::UTF8 PS C:\Users\HAIL 9000\facter> .\release\bin\facter.exe zeta_pilot カミーユ ビダン
Jira (PUP-6579) yum package test failing on master branch
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-6579 yum package test failing on master branch Change By: Hailee Kenney Status: Ready for CI Test Assignee: Kenneth Barber qa 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-6413) Pip provider fails when using ensure => latest
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-6413 Pip provider fails when using ensure => latest Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa 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 (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa 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 (FACT-1459) Allow specifying the config file from command line
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1459 Allow specifying the config file from command line Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa 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 (FACT-1458) Allow setting existing facter config flags from the config file
Title: Message Title Hailee Kenney assigned an issue to qa Facter / FACT-1458 Allow setting existing facter config flags from the config file Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa 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-6435) Replace sensitive data marker type with resource metadata after catalog compilation
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-6435 Replace sensitive data marker type with resource metadata after catalog compilation Change By: Hailee Kenney Status: Ready for CI Test Assignee: Branan Riley qa 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-6567) Test failure: /spec/unit/face/generate_spec.rb:149
Title: Message Title Hailee Kenney created an issue Puppet / PUP-6567 Test failure: /spec/unit/face/generate_spec.rb:149 Issue Type: CI Blocker Assignee: Unassigned Created: 2016/08/01 8:39 AM Priority: Normal Reporter: Hailee Kenney From Jenkins: 04:26:21 Failures: 04:26:21 04:26:21 1) Puppet::Face[:generate, v0.1.0] when used from an interactive terminal in an environment with two modules containing resource types creates output with matching names for each input 04:26:21 Failure/Error: expect(children).to eql(['test1.pp', 'test2.pp'])
Jira (FACT-1368) Windows output does not correctly print unicode snowman
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1368 Windows output does not correctly print unicode snowman Change By: Hailee Kenney Assignee: Hailee Kenney 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-1796) File resource fails for root(/) directory.
Title: Message Title
Hailee Kenney commented on PUP-1796
Re: File resource fails for root(/) directory.
On SHA 7c51b6b0649c9a8206ac684e36624506941ca42f (before the fix):
[root@cfbtk6c3v3tdxkt puppet]# cat test.pp
file { '/': ensure => directory }
[root@cfbtk6c3v3tdxkt puppet]# bundle exec puppet apply test.pp
Notice: Compiled catalog for cfbtk6c3v3tdxkt.delivery.puppetlabs.net in environment production in 0.07 seconds
Error: Parameter path failed on File[/]: File paths must be fully qualified, not '' at /root/puppet/test.pp:1
And on the latest version of master (SHA 7943fcbf9b094b7e435d8dde2b0a3539b506d886):
[root@cfbtk6c3v3tdxkt puppet]# cat test.pp
file { '/': ensure => directory }
[root@cfbtk6c3v3tdxkt puppet]# bundle exec puppet apply test.pp
Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-1796 File resource fails for root(/) directory. Change By: Hailee Kenney Assignee: qa Hailee Kenney 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-6440) Tag transaction events with sensitive data
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet / PUP-6440 Tag transaction events with sensitive data Change By: Hailee Kenney Assignee: Hailee Kenney 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-6440) Tag transaction events with sensitive data
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-6440 Tag transaction events with sensitive data Change By: Hailee Kenney Assignee: qa Hailee Kenney 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-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better So it's entirely possible that I'm not using the mount_providers module right, but I've tried created a mouttab, a moutpoint, and both together and they don't seem to be a solution to this problem. They don't even complain about the bogus options in the first place, no matter how many times I apply the manifest. It's not clear to me exactly what mounttab and mountpoint manage, maybe they don't deal with any actual mounting I'm not sure. But they don't seem to be raising the first error to begin with which makes impossible for me to verify if they're a solution to this problem. Maybe I need to talk to someone who knows more about these resources and their intended use, I just wrote a quick manifest based on the output of 'puppet describe'. 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-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better That's a good point Kylo Ginsberg, I'll check if that module still has this problem before moving ahead with anything else. 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-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better With a lot of help from Adrien Thebo, I've been making progress on this ticket. I've hit a little bit of a roadblock however. The beginnings of the solution we came up with can be found in this commit. The problem basically is that puppet is failing to detect when a mount has failed due to bad options and does not attempt to remount. This is because it is comparing only two sources and ensuring they match but neither source reflects what is actually mounted. When puppet attempts to mount a resource with invalid options, the mount will fail BUT the new options will be listed in /etc/fstab. On the next puppet run, puppet will compare the defined resource to /etc/fstab and find that the options match, thus it will not attempt to remount. So puppet will give the impression that the remount with the new options is no longer failing which is incorrect. However, the output of the mount command does reveal that the resource did not successfully remount with the new problematic options. The options listed for the mounted file system from the mount command are not the update options which match the manifest, but the old ones which do not match the user defined resource. Thus we decided that the way to solve this problem was to also check the options for the mounted file system as they are in the output of the mount command, and if they do not match we know that the resource is not in sync with what is on the system and that we should attempt another remount. This was all working until we realized the difference between /etc/fstab and the output of mount for default mount options. /etc/fstab will list the string "defaults" but mount will list the full list of default options. That means for this case, it's impossible to compare if the two are in sync unless we devise some kind of insane lookup table that tells us for each type of file system and operating system (and probably some more parameters honesty) what the list of default options should look like. This has left us stumped, and we're looking for some ideas. Either a new approach, or a solution to the problem just described. Or the go ahead to attempt to construct the insane archive of default options for every OS we support. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDOC-88) Create a plan for ensuring strings support going forward
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-88 Create a plan for ensuring strings support going forward Issue Type: Task Assignee: Unassigned Created: 2016/07/07 8:51 AM Priority: Normal Reporter: Hailee Kenney If the docs team is going to rely on strings, we need to make sure that new releases of puppet do not break it in such a way that it becomes unusable. That means that new releases of puppet cannot cause strings to have any of the following issues: Fail to finish running Emit corrupted JSON or other bad things Any of the requirements defined by the PDOC-59 epic are no longer met (e.g. failing to pick up function definitions, etc) Testing for strings is incredibly minimal right now. At the very least, we need to improve unit tests and add unit tests for JSON output. We probably also need to add some actual acceptance testing. It may be that better testing is all that's needed here, but before the docs team can integrate strings we have to be able to assure that it's maintained properly along with new releases of puppet.
Jira (PDOC-83) Define a proper JSON schema for strings
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-83 Define a proper JSON schema for strings Change By: Hailee Kenney In order to ensure that strings produces JSON in a way that's consistent and workable. The language and docs teams should work together to define a schema that makes sense and will suit the needs of the docs team. As part of this work, we need to ensure that the JSON output generated does not contain any significant errors or glitches and that things are reliably in the right place so it can be used by the docs team. 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 (PDOC-87) Ensure our internal functions are documented in a way that's compatible with strings
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-87 Ensure our internal functions are documented in a way that's compatible with strings Issue Type: Task Assignee: Unassigned Created: 2016/07/07 8:31 AM Priority: Normal Reporter: Hailee Kenney We should do a quick pass to make sure that all our function documentation is written in a format that strings can support. Basically this means two things: Is it all valid Markdown that the parser used by YARD can handle Are the YARD tags used supported by strings Hopefully this shouldn't be a big effort, just a few minor corrections if anything. Add Comment
Jira (PDOC-86) Make Markdown the default format
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-86 Make Markdown the default format Change By: Hailee Kenney Issue Type: Bug Improvement 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 (PDOC-86) Make Markdown the default format
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-86 Make Markdown the default format Issue Type: Bug Assignee: Unassigned Created: 2016/07/07 7:43 AM Fix Versions: PDOC 0.5.0 Priority: Normal Reporter: Hailee Kenney Right now, without a .yardopts file dropped in the root directory of what you're documenting, strings will default to parsing comments with rdoc. This is not the desired behavior, as we now document our functions with Markdown and are encouraging this as the new standard. We need to modify strings to default to Markdown, preferably in a way that it is still configurable by the user to use rdoc instead. Add Comment
Jira (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-85 Handle the case of 4x functions and 3x stubs Change By: Hailee Kenney Issue Type: Bug Improvement 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 (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-85 Handle the case of 4x functions and 3x stubs Issue Type: Bug Assignee: Unassigned Created: 2016/07/06 8:25 AM Fix Versions: PDOC 0.5.0 Priority: Normal Reporter: Hailee Kenney Because we didn't want to maintain documentation in two places, many of the core Puppet functions are implemented in the 4x style but have a matching 3x stub with contains all the documentation. We need to ensure that strings can handle this in a way that makes sense, combining the relevant information from both, taking only the doc string from the 3x version, or something similar. Add Comment
Jira (PDOC-64) Create Puppet4xFunction and Puppet3xFunction code objects
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-64 Create Puppet4xFunction and Puppet3xFunction code objects Change By: Hailee Kenney Issue Type: Bug Improvement 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 (PDOC-63) Blizzard of errors and warnings when run against core code
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-63 Blizzard of errors and warnings when run against core code Change By: Hailee Kenney Story Points: 3 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 (PDOC-60) Strings skips docs for the log message functions
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-60 Strings skips docs for the log message functions Change By: Hailee Kenney Story Points: 2 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 (PDOC-61) Strings finds bogus "function_definition" function
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-61 Strings finds bogus "function_definition" function Change By: Hailee Kenney Story Points: 2 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 (PDOC-84) Add the ability to generate only JSON
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-84 Add the ability to generate only JSON Issue Type: Improvement Assignee: Unassigned Created: 2016/07/05 11:36 AM Fix Versions: PDOC 0.5.0 Priority: Normal Reporter: Hailee Kenney Whether it's a rake task, a subcommand, or both we need to add a way to generate only the single JSON file and not the entire doc directory of HTML pages. I'm not sure if it's possible to also prevent yard from producing the additional output like the .yardoc directory, but either way we need to clearly define what will be generated and where so that it can be automatically scrapped as appropriate. Add Comment
Jira (PDOC-83) Define a proper JSON schema for strings
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-83 Define a proper JSON schema for strings Issue Type: Improvement Assignee: Unassigned Created: 2016/07/05 9:33 AM Priority: Normal Reporter: Hailee Kenney In order to ensure that strings produces JSON in a way that's consistent and workable. The language and docs teams should work together to define a schema that makes sense and will suit the needs of the docs team. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-60 Strings skips docs for the log message functions Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 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 (PDOC-61) Strings finds bogus "function_definition" function
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-61 Strings finds bogus "function_definition" function Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 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 (PDOC-63) Blizzard of errors and warnings when run against core code
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-63 Blizzard of errors and warnings when run against core code Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 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 (PDOC-82) Ensure the strings gem can be managed via bundler in docs scripts
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-82 Ensure the strings gem can be managed via bundler in docs scripts Issue Type: Improvement Assignee: Unassigned Created: 2016/07/05 7:45 AM Fix Versions: PDOC 0.5.0 Priority: Normal Reporter: Hailee Kenney Because the docs team would like to use strings in their automated doc extraction scripts, we need to ensure that the gem can be used and managed with bundler in that context. It needs to work out of the box and can’t contaminate the user’s environment outside of bundler. There's not really any reason to believe that this won't work, but since it's essential we should verify it. The scripts in question live here Add Comment
Jira (PDOC-59) Improve behavior of Strings to support integration into Docs workflow
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-59 Improve behavior of Strings to support integration into Docs workflow Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 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 (PDOC-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title Hailee Kenney commented on PDOC-71 Re: Stack Level Too Deep Exception and Spurious Errors So unfortunately I had to time box my work on the issue and after some poking around in the debugger I still haven't been able to get to the root of it. I figured I'd leave some notes on where I was planning on going next for my future self or whoever picks up this ticket. I think this is going to be kind of a hairy issue to track down judging by the fact that it only happens at a particular scale and that this file evaluated on its own is fine. I think, as the ticket description suggests, that it's a fair assumption something is being corrupted somewhere. That being said, comparing our code object in the good case and the code object in the bad case may be the key to tracking things down. Since the exception is occurring in the HostClassHandler the object in question is this one. I think either inspecting this object with the debugger or printing it in both scenarios (a. running it in the batch when it fails and b. running it on it's own when it passes) and seeing what is different should point to where the corruption is potentially happening. 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-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Hailee Kenney Assignee: Hailee Kenney 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 (PDOC-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title Hailee Kenney commented on PDOC-71 Re: Stack Level Too Deep Exception and Spurious Errors Noting for myself and others: to reproduce this bug using the steps described in the ticket on a CentOS 7 virtual machine, makes sure you install rpm-build and rpm-devel. 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 (PDOC-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet Strings / PDOC-71 Stack Level Too Deep Exception and Spurious Errors Change By: Hailee Kenney Assignee: Hailee Kenney 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 (PDOC-78) Include LICENSE, documentation and tests in gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-78 Include LICENSE, documentation and tests in gem Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 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 (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Hailee Kenney Attachment: Screen Shot 2016-06-20 at 1.23.06 PM.png 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 (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Hailee Kenney commented on PDOC-79 Re: [SPIKE] Define the set of tickets needed to get strings working for docs needs So for what it's worth the screenshot provided isn't quite an accurate representation of what the strings output will look like for our functions. I ran strings only against the "new" function (specifically the 3.x stub in `lib/puppet/parser/functions` since it contains the actual documentation string) where I set the "--markup markdown" option in the .yardopts file and it looks much better (see attached screenshot). The issue here is that YARD by default will assume it's parsing rdoc (which is why the previous screenshot looks so unreadable), when we want it to parse our comments and Markdown. This is usually dealt with by adding a .yardopts file in the root of the module directory which specifies the Markdown option. I'm not quite sure how we want to deal with this in regards to running against core puppet since we don't want to be dropping .yardopts files everywhere. We will probably have to figure out another way to pass this setting to YARD. This can't be done via the command line because since strings is a face, all arguments are parsed as puppet arguments. 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 (FACT-1408) Facter productname issue on Solaris
Title: Message Title Hailee Kenney commented on FACT-1408 Re: Facter productname issue on Solaris Boyd Adamson, thank you! All that information is incredibly helpful. I think our plan, especially with the info you've provided, is to revert back to using prtdiag and go from there. 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 (FACT-1408) Facter productname issue on Solaris
Title: Message Title Hailee Kenney commented on FACT-1408 Re: Facter productname issue on Solaris Okay! After some digging I found the commit that made the switch from ptrdiag to ptrconf: https://github.com/puppetlabs/facter/commit/7f36d65d7c62e225b6d915d2fce39aec240eec97 The comment suggests that the reason why we're not relying on ptrdiag anymore is because it doesn't exist on all sparc machines. I can try to do some digging about which machines it does/doesn't work on. We also could potentially try to use and then fall back to ptrconf if it isn't there. 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 (FACT-1408) Facter productname issue on Solaris
Title: Message Title Hailee Kenney commented on FACT-1408 Re: Facter productname issue on Solaris It looks like we've changed the source we're using to get that fact between Facter 2 and Facter 3, curious as to why we switched. In Facter 2 it's coming from '/usr/sbin/prtdiag' https://github.com/puppetlabs/facter/blob/2.x/lib/facter/util/manufacturer.rb#L63 In Facter 3 it's coming from '/usr/sbin/prtconf' https://github.com/puppetlabs/facter/blob/4a495e877d68648b6315b1a68755627de4c3c52d/lib/src/facts/solaris/dmi_resolver.cc#L73 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 (FACT-1408) Facter productname issue on Solaris
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1408 Facter productname issue on Solaris Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1373) Facter with external fact containing a facter call fork-bombs the node
Title: Message Title Hailee Kenney updated an issue Facter / FACT-1373 Facter with external fact containing a facter call fork-bombs the node Change By: Hailee Kenney Release Notes Summary: Previously, if facter was called from an external fact it would generate endless recursive facter calls and fork bomb the agent. In order to prevent this, we will now detect recursive calls to evaluate external facts, and if we encounter one we will log a warning and stop evaluating external facts.To do this, we set an environment variable called 'INSIDE_FACTER' the first time external facts are evaluated and check this variable before we evaluate external facts to ensure it hasn't been set. It is possible that a user may have their own environment variable called 'INSIDE_FACTER' set to true, so anytime we encounter that variable set to true, we log a debug warning. Release Notes: Bug Fix 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
Jira (FACT-1373) Facter with external fact containing a facter call fork-bombs the node
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1373 Facter with external fact containing a facter call fork-bombs the node Change By: Hailee Kenney Assignee: Hailee Kenney 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-6233) Serivce SMF restart should use -s
Title: Message Title Hailee Kenney assigned an issue to Branan Riley Puppet / PUP-6233 Serivce SMF restart should use -s Change By: Hailee Kenney Assignee: Shawn Ferry Branan Riley 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-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Hailee Kenney commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Running on Debian 7 when installed from packages:
root@klk6ki5l5yss3px:~# puppet apply -e "notify{ 'hello world' :}"
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
Notice: Compiled catalog for klk6ki5l5yss3px.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world'
Notice: Finished catalog run in 0.02 seconds
root@klk6ki5l5yss3px:~# puppet --version
3.8.7
root@klk6ki5l5yss3px:~# puppet help
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Hailee Kenney commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Running on CentOS 7 when installed from packages:
[root@i2uzzu73w5pdw5v ~]# puppet apply -e "notify{ 'hello world' :}"
Notice: Compiled catalog for i2uzzu73w5pdw5v.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world'
Notice: Finished catalog run in 0.01 seconds
[root@i2uzzu73w5pdw5v ~]# puppet --version
3.8.7
[root@i2uzzu73w5pdw5v ~]# puppet help
Usage: puppet [options] [options]
Jira (PUP-6200) Smoke test packages (PUP 3.8.7)
Title: Message Title
Hailee Kenney commented on PUP-6200
Re: Smoke test packages (PUP 3.8.7)
Running the gem on CentOS 7:
[root@qf7b2t9esb806a5 ~]# puppet apply -e 'notify{ 'hello world!' :}'
-bash: !': event not found
[root@qf7b2t9esb806a5 ~]# puppet apply -e "notify{ 'hello world!' :}"
-bash: !': event not found
[root@qf7b2t9esb806a5 ~]# puppet apply -e 'notify{ "hello world^C:}'
[root@qf7b2t9esb806a5 ~]# puppet apply -e "notify{ 'hello world' :}"
Notice: Compiled catalog for qf7b2t9esb806a5.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: hello world
Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world'
Notice: Finished catalog run in 0.47 seconds
Jira (FACT-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Hailee Kenney assigned an issue to Unassigned Facter / FACT-1385 Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1385 Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1364) facter does not serialize integers above 32bits in structured facts in windows
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1364 facter does not serialize integers above 32bits in structured facts in windows Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Facter / FACT-1385 Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Change By: Hailee Kenney Assignee: Hailee Kenney 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 (FACT-1391) --custom-dir does not support trailing slashes on Windows
Title: Message Title Hailee Kenney created an issue Facter / FACT-1391 --custom-dir does not support trailing slashes on Windows Issue Type: Bug Assignee: Unassigned Components: Windows Created: 2016/04/14 2:19 PM Priority: Normal Reporter: Hailee Kenney When giving facter a directory to look for custom facts, if the path is giving with a trailing slash facter will fail to find the facts in that directory. PS C:\Users\HAIL 9000\my_custom_facts> ls
Jira (FACT-1391) --custom-dir does not support trailing slashes on Windows
Title: Message Title
Hailee Kenney updated an issue
Facter / FACT-1391
--custom-dir does not support trailing slashes on Windows
Change By:
Hailee Kenney
When giving facter a directory to look for custom facts, if the path is giving with a trailing slash facter will fail to find the facts in that directory.{noformat}PS C:\Users\HAIL 9000\my_custom_facts> lsDirectory: C:\Users\HAIL 9000\my_custom_factsModeLastWriteTime Length Name- -- -a4/14/2016 1:33 PM 71 my_fact.rbPS C:\Users\HAIL 9000\my_custom_facts> cat .\my_fact.rbFacter.add('my_fact') do setcode do'my_fact_value' endendPS C:\Users\HAIL 9000\my_custom_facts> cd 'C:\Users\HAIL 9000\facter\release\'PS C:\Users\HAIL 9000\facter\release> .\bin\facter.exe my_fact --custom-dir 'C:\Users\HAIL 9000\my_custom_facts\' PS C:\Users\HAIL 9000\facter\release> .\bin\facter.exe my_fact --custom-dir 'C:\Users\HAIL 9000\my_custom_facts'my_fact_value{noformat}
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 (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-75 Strings calls 'interpret_any' with the wrong number of arguments Change By: Hailee Kenney Fix Version/s: PDOC 0.4.0 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 (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet Strings / PDOC-75 Strings calls 'interpret_any' with the wrong number of arguments Change By: Hailee Kenney Assignee: Hailee Kenney 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 (PDOC-75) Strings calls 'interpret_any' with the wrong number of arguments
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-75 Strings calls 'interpret_any' with the wrong number of arguments Issue Type: Bug Assignee: Unassigned Created: 2016/03/24 2:08 PM Priority: Normal Reporter: Hailee Kenney Puppet strings uses an API private method in puppet which has been updated to take two parameters instead of one. This means strings is calling it with the wrong number of variables in the host class handler which is causing it to crash: https://github.com/puppetlabs/puppetlabs-strings/blob/master/lib/puppet_x/puppetlabs/strings/yard/handlers/host_class_handler.rb#L19 This ticket is for fixing the issue in strings. For details around the fact that strings is using API private puppet methods, see PUP-6088 Add Comment
Jira (PUP-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Hailee Kenney Assignee: Hailee Kenney 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-6088) Puppet strings relies on API private methods in puppet
Title: Message Title Hailee Kenney commented on PUP-6088 Re: Puppet strings relies on API private methods in puppet Ping Henrik Lindberg 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-6088) Puppet strings relies on API private methods in puppet
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-6088 Puppet strings relies on API private methods in puppet Change By: Hailee Kenney The puppet strings tool lies currently relies on at least one (potentially more) methods in puppet that are API private. This can lead to weird breakages in strings that are kind of mysterious since API private methods can be changed at will. The current issue in question is this one:https://github.com/puppetlabs/puppetlabs-strings/blob/master/lib/puppet_x/puppetlabs/strings/yard/handlers/host_class_handler.rb#L19An API private method was being used for parameter type checking, and was updated to require two parameters instead of one. This created a kind of mysterious error in strings and situations like this aren't ideal. So we need to answer two questions (which may have the same answer) : # What do we want to do with this error specifically?# How do we want to handle strings using API private methods? 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-6088) Puppet strings relies on API private methods in puppet
Title: Message Title Hailee Kenney created an issue Puppet / PUP-6088 Puppet strings relies on API private methods in puppet Issue Type: Bug Assignee: Unassigned Created: 2016/03/23 5:23 PM Priority: Normal Reporter: Hailee Kenney The puppet strings tool lies on at least one (potentially more) methods in puppet that are API private. This can lead to weird breakages in strings that are kind of mysterious since API private methods can be changed at will. The current issue in question is this one: https://github.com/puppetlabs/puppetlabs-strings/blob/master/lib/puppet_x/puppetlabs/strings/yard/handlers/host_class_handler.rb#L19 An API private method was being used for parameter type checking, and was updated to require two parameters instead of one. This created a kind of mysterious error in strings and situations like this aren't ideal. So we need to answer two questions (which may have the same answer) What do we want to do with this error specifically? How do we want to handle strings using API private methods?
Jira (PDOC-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Since there's pretty much unanimous agreement that strings is a tool better delivered via gem rather than a puppet module, the 0.4.0 will be the first and final release to feature both a gem and a module. The module will need to be updated to explain that it is deprecated and all further updates will come via the gem. That means we need to make a few changes for the module release to communicate that it's being deprecated:# Update the README to explain that the module is deprecated# Add a guide for gem installation in the README # Go through the Puppet Labs gem checklist # Update metadata and gemspec# Add CHANGELOG Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-70) Always generate JSON output for Rake task
Title: Message Title Hailee Kenney commented on PDOC-70 Re: Always generate JSON output for Rake task Whew, sorry it took so long but I finally got to test this! It works exactly as planned, and it seems to be like a sane default, especially since rake tasks aren't exactly the "default" way to use strings. Plus we haven't done a release with them yet (so this shouldn't break existing behavior for anyone). Wondering though if we want to document the fact that it will create a json file in the root directory, maybe in the section of the README about rake tasks? Thoughts Henrik Lindberg Gareth Rushgrove? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-70) Always generate JSON output for Rake task
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-70 Always generate JSON output for Rake task Change By: Hailee Kenney Fix Version/s: PDOC 0.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-28) Make puppet strings available as a gem
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet Strings / PDOC-28 Make puppet strings available as a gem Change By: Hailee Kenney Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-23) Add the ability to output JSON
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet Strings / PDOC-23 Add the ability to output JSON Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-28) Make puppet strings available as a gem
Title: Message Title Hailee Kenney commented on PDOC-28 Re: Make puppet strings available as a gem I also tested building and running the gem and didn't encounter any issues, so I suspect the issue you're seeing Jan Vansteenkiste is an issue with strings in general and not the gem specifically, so I'm going to resolve this ticket. However, if you'd like to provide some more details about your setup, what module you're running against, etc I'd be happy to see if I can trouble shoot the problem. It may be an existing issue or one that we need to file a new ticket for. Thanks for your help! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Since there's pretty much unanimous agreement that strings is a tool better delivered via gem rather than a puppet module, the 0.4.0 will be the first and final release to feature both a gem and a module. The module will need to be updated to explain that it is deprecated and all further updates will come via the gem. That means we need to make a few changes for the module release to communicate that it's being deprecated:# Update the README to explain that the module is deprecated# Add a guide for gem installation in the README # Go through the Puppet Labs gem checklist # Go through the Puppet Labs library checklist Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Since there's pretty much unanimous agreement that strings is a tool better delivered via gem rather than a puppet module, the 0.4.0 will be the first and final release to feature both a gem and a module. The module will need to be updated to explain that it is deprecated and all further updates will come via the gem. That means we need to make a few changes for the module release to communicate that it's being deprecated: Before the module release: # Update the REAMDE README to explain that the module version is deprecated and where to find the gem # Add a brief deprecation messageBefore the guide for gem release: installation in the README # Go through the Puppet Labs gem release checklist# Update Go through the README to detail the gem installation process (instead of referencing the module) Puppet Labs library checklist Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
