Jira (PUP-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Ethan Brown commented on PUP-6035 Re: Puppet Throws Exception when Running Under Unicode Windows User I have moved this into the Phase 1 Blockers epic PUP-6718, because the underlying Ruby Dir.chdir seems to be having issues, and that should impact other uses within Puppet. If we want to create a new ticket around Dir problems we can do that - moving this ticket back into the Developer epic PUP-6720. I believe that Dir.entries and other Dir methods may misbehave with Unicode paths. 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-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6803 puppet run status should be "failed" if there are failed generated resources Issue Type: Task Assignee: Unassigned Created: 2016/10/07 5:07 PM Priority: Normal Reporter: Moses Mendoza In support escalation PE-17793 the customer reports that puppet runs are showing up as successful in the console despite having failures in the reports log. The customer has generated resources that are failing, which are getting logged in the report as errors, but the overall run status is reported as successful (specifically, unchanged). The console reads the run status field to determine what to display - hence success. When generated resources fail to generate in `eval_generate`, we log the exception and don't generate anymore resources for that parent, but otherwise management of the parent resource is unaffected. In transaction::report::compute_status we don't take the exception log into account when determining the run status, and thus can consider a run successful even when generated resources failed. After discussion with Branan Riley, the proposal is to detect when any resource generation has failed (perhaps introspect the Puppet::Util::Log instances associated with the report for failures or some other way?) and consider the run failed if any are encountered. This won't affect any resource-specific report data, just the overall run status, but will have the effect of "correcting" the report viewing for the user.
Jira (PUP-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza commented on PUP-6803 Re: puppet run status should be "failed" if there are failed generated resources Marking as needs information pending discussion with Puppet maintainers 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-3077) Integrate Ezbake service reload and logback/logrotate changes into PuppetDB
Title: Message Title Chris Price assigned an issue to Jeremy Barlow PuppetDB / PDB-3077 Integrate Ezbake service reload and logback/logrotate changes into PuppetDB Change By: Chris Price Assignee: Jeremy Barlow 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-1108) PuppetDB appears to ignore trailing spaces
Title: Message Title Wyatt Alt commented on PDB-1108 Re: PuppetDB appears to ignore trailing spaces I can reproduce this with hsqldb but not with postgres. We haven't supported hsqldb for a long time at this point, so I'm closing wontfix. 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Ethan Brown commented on PUP-6432 Re: Puppet::Util::Execution.execute cannot handle Unicode output on Windows A few more notes: cmd.exe has a command line parameter to enable Unicode - not entirely sure yet what behavioral changes it will make: /U Causes the output of internal commands to a pipe or file to be Unicode Changing Puppets codepage to 65001 with chcp 65001 or programatically with SetConsoleOutputCP might not work properly. This would have to be done before Ruby initializes, which I don't believe is even possible. Note that there are supposedly many bugs with using that codepage, that at least anecdotally are WONTFIX per http://stackoverflow.com/a/1371069/87793 Michael Kaplan has a very detailed post about using _O_U16TEXT and _O_U8TEXT with the CRT call _setmode at http://archives.miloush.net/michkap/archive/2008/03/18/8306597.html - not that some of the problems revolve around rendering on Windows, which we don't typically care about unless logoutput is on for the exec. As long as bytes are written correctly in both directions, we should generally be OK. He summarizes conventional, but incorrect Windows limitations as: Unicode I/O with ReadConsoleW/WriteConsoleW is always supported; but default raster font will break it. Changing console codepage is always possible, but DBCS codepages are supported under DBCS system locales (not necessarily matching). The console does not support complex script languages such as Arabic or the various Indic languages that can only be rendered with Uniscribe. Unicode I/O is supported through Win32, but with several limitations: a user has to select a truetype font in console; no redirection of input/output is supported;
Jira (PDB-2357) PQL: Decide on final group by syntax
Title: Message Title Wyatt Alt commented on PDB-2357 Re: PQL: Decide on final group by syntax Ryan Senior I think we can close this – any thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1384) Remove deprecated APIs necessitated by Server 2003 compat
Title: Message Title Ethan Brown updated an issue Facter / FACT-1384 Remove deprecated APIs necessitated by Server 2003 compat Change By: Ethan Brown Sprint: AP Triage 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-111) Prepare long form release notes (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-111 Re: Prepare long form release notes (PDOC 0.99.0) Subject: Announce: Strings 0.99.0 Released! Body: Hello, all! Today, we're pleased to announce the release of puppet-strings 0.99.0! Strings is a YARD-based documentation tool for Puppet extensions written in Puppet and Ruby. Given some simple in-code comments containing YARD tags, it will generate consistent HTML or JSON documentation for all of your Puppet 3x/4x API functions, Puppet language functions, Ruby classes, Ruby methods, types, and providers. This release includes a near-complete rewrite of the project, fixing many bugs from previous versions and generally improving the user experience. Note that this release is intended to be the last stop before the strings major version 1.0.0 is released, and nearly all of the functionality of the major release is included. Note also: backwards incompatible changes have been made to the original JSON schema. Highlights: Both HTML and JSON documentation has been split into sections based on type: Puppet 3x API functions, Puppet 4x API functions, Ruby classes/methods, Puppet language functions, types, and providers. New --emit-json and --emit-json-stdout commandline options for generating JSON documentation. A brand new JSON schema organized around the new separation of types. Support for custom functions written in the puppet language. Support for function overloads via the create_function 4x API. YARD has been bumped to the latest version, greatly enhancing the look and usability of the HTML output. Other important notes: Markdown is now the default format for parsing in-code docstrings. The runtime dependency of puppet has been removed in favor of a gem 'requirement' which appears on rubygems.org. We recommend you install the puppet-strings gem using puppet, as suggested in the README. Never used Strings? Check out the README linked below and give it a try! The CHANGELOG can be found here: https://github.com/puppetlabs/puppet-strings/blob/master/CHANGELOG.md
Jira (PDOC-110) Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0)
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-110 Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0) Change By: William Hopper (Initial planned release date: 2016-10-10)This happens on Jira - we need to clean up the current release and prepare for the next release.Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket):'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone TestRail: Results 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
Jira (PDOC-110) Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-110 Re: Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0) We now have PDOC versions for both 0.99.1 and 1.0.0. Filters: Fixed in 0.99.0: https://tickets.puppetlabs.com/issues/?filter=22705 Introduced in 0.99.0: https://tickets.puppetlabs.com/issues/?filter=22706 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-110) Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0)
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-110 Is the Jira tidy-up done for this release and prepared for the next one? (PDOC 0.99.0) Change By: William Hopper (Initial planned release date: 2016-10-10)This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket):'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for EveryoneTestRail: Results 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
Jira (PDOC-108) Is the code ready for release? (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-108 Re: Is the code ready for release? (PDOC 0.99.0) Changelog entry added for 0.99.0 and version bumped in the gemspec. Tests are all passing, and all tickets are resolved for this release. 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-109) Reconcile git commits and JIRA tickets (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-109 Re: Reconcile git commits and JIRA tickets (PDOC 0.99.0) All of the old code was gutted at https://github.com/puppetlabs/puppet-strings/commit/7ae8e74ec571c84a31dd2aee42aaa86f09a8ece3, thus we don't really need to worry about them. The rewrite commit is tracked as PDOC-63 , and everything after that is associated with a ticket or is a (maint) commit. 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-6184) Remove win32-dir code usage from Puppet / Facter
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6184 Remove win32-dir code usage from Puppet / Facter Change By: Ethan Brown Sprint: AP Triage 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-6184) Remove win32-dir code usage from Puppet / Facter
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6184 Remove win32-dir code usage from Puppet / Facter Change By: Ethan Brown Team: Agent & Platform 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-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title William Hopper commented on PDOC-71 Re: Stack Level Too Deep Exception and Spurious Errors Trevor Vaughan oh yes, definitely! We've got a new team with strings as a central part of its charter now. We have big plans! Please do try it out and let us know if/when you find any issues - we'll be doing the big 1.0.0 soon, after fixing anything found in this one. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title Trevor Vaughan commented on PDOC-71 Re: Stack Level Too Deep Exception and Spurious Errors William Hopper Awesome! It's really great to hear that there has been some love here. Looking forward to trying the new version. 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-119) Add required ruby version to gemspec
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-119 Add required ruby version to gemspec Change By: William Hopper Story Points: 1 Team: Puppet Developer Support Sprint: PDS 2016-10-19 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-119) Add required ruby version to gemspec
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-119 Add required ruby version to gemspec Issue Type: Task Assignee: Unassigned Created: 2016/10/07 2:02 PM Priority: Normal Reporter: William Hopper See PDOC-118, which I accidentally referenced in the commit . Opening this to match the commit message, instead of force pushing master. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-107) puppet-strings 0.99.0 Release
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-107 puppet-strings 0.99.0 Release Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-78) Include LICENSE, documentation and tests in gem
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-78 Include LICENSE, documentation and tests in gem Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-77 Create an easy way to modify the rake task to include/exclude certain files/folders. Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-82) Ensure the strings gem can be managed via bundler in docs scripts
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-82 Ensure the strings gem can be managed via bundler in docs scripts Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-85 Handle the case of 4x functions and 3x stubs Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-59) Improve behavior of Strings to support integration into Docs workflow
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-59 Improve behavior of Strings to support integration into Docs workflow Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-60 Strings skips docs for the log message functions Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-61) Strings finds bogus "function_definition" function
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-61 Strings finds bogus "function_definition" function Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title William Hopper commented on PDOC-71 Re: Stack Level Too Deep Exception and Spurious Errors Trevor Vaughan we're going to be releasing strings 0.99.0 (a complete rewrite) on Monday, and we're pretty confident that this won't be an issue in the new code. Definitely let us know if it pops up again, though. 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-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-71 Stack Level Too Deep Exception and Spurious Errors Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-88) Create a test plan for ensuring strings support going forward
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-88 Create a test plan for ensuring strings support going forward Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3091) sweep acceptance tests for service reload opportunities
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3091 sweep acceptance tests for service reload opportunities Issue Type: Task Assignee: Unassigned Created: 2016/10/07 1:36 PM Priority: Normal Reporter: Wyatt Alt We should be able to reduce our acceptance time in places by restarting PuppetDB and PuppetServer with a HUP. This might end up being significant savings. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-86) Make Markdown the default format
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-86 Make Markdown the default format Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-106 Acceptance tests for strings JSON output Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-107) puppet-strings 0.99.0 Release
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-107 puppet-strings 0.99.0 Release Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-92) Rename the puppetlabs-strings repo to puppet-strings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-92 Rename the puppetlabs-strings repo to puppet-strings Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-118) Add ruby version requirement in puppet-strings.gemspec
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-118 Add ruby version requirement in puppet-strings.gemspec Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-6096 Add Acceptance Test for Installing Module with Long Paths with PMT Change By: Eric Thompson Assignee: Zach Reichert qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6096 Add Acceptance Test for Installing Module with Long Paths with PMT Change By: Eric Thompson Team: Puppet Developer Support 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-6096) Add Acceptance Test for Installing Module with Long Paths with PMT
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6096 Add Acceptance Test for Installing Module with Long Paths with PMT Change By: Eric Thompson Labels: maintenance tech-debt 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-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Eric Thompson Assignee: Sean Griffin qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Eric Thompson Team: Puppet Developer Support 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-83) Define a proper JSON schema for strings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-83 Define a proper JSON schema for strings Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-84) Add the ability to generate only JSON
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-84 Add the ability to generate only JSON Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson commented on PUP-5000 Re: acceptance: test agent_specified environment, ENC, and related facts Sean Griffin do you have a branch or any related work to give us a head-start on this? 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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Eric Thompson Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6244) Acceptance: fix module upgrade tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6244 Acceptance: fix module upgrade tests Change By: Eric Thompson Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6244) Acceptance: fix module upgrade tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6244 Acceptance: fix module upgrade tests Change By: Eric Thompson Labels: maintenance 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Eric Thompson updated an issue Puppet / PUP-686 --detailed-exit-codes not honored when --noop is used Change By: Eric Thompson Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6244) Acceptance: fix module upgrade tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6244 Acceptance: fix module upgrade tests Change By: Eric Thompson Team: Puppet Developer Support 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 William Hopper updated an issue Puppet Strings / PDOC-80 Installation overwrites facter in PE 3.8.3 Change By: William Hopper Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-63) Strings outputs errors on puppet core
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-63 Strings outputs errors on puppet core Change By: William Hopper Fix Version/s: PDOC 0.5.0 Fix Version/s: PDOC 0.99.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1526) Package type should support environment variables
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1526 Package type should support environment variables Change By: Eric Thompson Team: Agent & Platform 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-6245) Acceptance: fix zpool create zone test
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6245 Acceptance: fix zpool create zone test Change By: Eric Thompson Team: Agent & Platform 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-6524) The shell used with exec resource provider=shell should be configurable
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6524 The shell used with exec resource provider=shell should be configurable Change By: Eric Thompson Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1515) Facter does not respect the configuration file and still attempts to collect facts
Title: Message Title
Maggie Dreyer commented on FACT-1515
Re: Facter does not respect the configuration file and still attempts to collect facts
To use the blocklist, you must give it the names of the fact groups you would like to block, NOT individual facts. The available groups can be found by using the --list-block-groups command line flag. (You may have to update Facter to the latest version on the master branch on GitHub). So for the facts you would like to block, your config file should be:
facts : { blocklist : [ "file system" ] }
The timezone fact is not currently blockable, but if you have a good use case for needing to block it, please consider filing a ticket (or a PR!) to add it to the blockable facts.
The blocklist works this way because in Facter 3, unlike in Facter 2, we batch collect facts to speed up fact collection and cut down on system calls. Therefore, if a user wants to stop the actual collection of a given fact because the system calls cause issues, they also necessarily lose the other facts that are extracted from the same system calls. This makes it slightly more difficult to discover what the valid elements of the blocklist are, which is why we have added the --list-block-groups command line option. Luckily, it looks like you already wanted to block all of the "file system" facts (i.e. mountpoints, filesystems, and partitions), so this fits your use case perfectly.
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-82) Ensure the strings gem can be managed via bundler in docs scripts
Title: Message Title William Hopper commented on PDOC-82 Re: Ensure the strings gem can be managed via bundler in docs scripts Just worked with Nick on this. His workflow is as follows: Bundle install puppet-strings in the puppet-doc repo (it is in the Gemfile). This repo holds a version of the puppet source in its vendor directory. Then, point strings at that source with bundle exec puppet-strings generate ./vendor/puppet/lib/puppet/*/.rb (for functions) We determined that this works correctly for Puppet 4.7.0. When running strings against 4.2.2, strings errored out with no explanation via logging. Though we should probably look into that, it doesn't affect the docs workflow as they will not be regenerating docs for older versions of puppet. 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Moses Mendoza commented on PUP-1431 Re: Pre/Post-run commands don't work under Windows cc Geoff Nichols tossed this in the top 10 grooming sprint 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Change By: Moses Mendoza Sprint: AP Grooming Top 10 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Change By: Moses Mendoza Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Change By: Moses Mendoza Priority: Normal Major 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1431 Pre/Post-run commands don't work under Windows Change By: Moses Mendoza Fix Version/s: PUP 4.y 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Henrik Lindberg commented on PUP-6799 Re: PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided merged to master at: b9a54a4 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-6768) Implement 'lookup context' object in the lookup v5 API
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6768 Implement 'lookup context' object in the lookup v5 API Change By: Henrik Lindberg Assignee: Henrik Lindberg Acceptance Criteria: This is enabling functionality - there should be unit test coverage of the features provided in the LookupContext API. Fix Version/s: PUP 4.8.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6768) Implement 'lookup context' object in the lookup v5 API
Title: Message Title Henrik Lindberg commented on PUP-6768 Re: Implement 'lookup context' object in the lookup v5 API merged to master at: 0c08725 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-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Nick Walker updated an issue Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment Change By: Nick Walker Affects Version/s: PUP 4.5.3 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-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title
Nick Walker commented on PUP-6802
Re: Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
I think PUP-6048 is related but different. That has to do with `puppet facts` looking for an environment locally which is unexpected. In the case of this ticket I can successfully run `puppet facts` .
If I set environment in [main] on the box I was testing with we see that I reproduce PUP-6048.
[root@agent201621-centos ~]# puppet facts
{
"name": "agent201621-centos",
...
}
[root@agent201621-centos ~]# puppet config set environment fake --section main
[root@agent201621-centos ~]# puppet facts
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'fake' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound)
from
Jira (PUP-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment Change By: Lindsey Smith Summary: Agent cannot compile catalog if it specifies an non- existant existent environment in puppet.conf even when the classifier is controlling environment 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-6802) Agent cannot compile catalog if it specifies an non-existant environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Nick Walker updated an issue Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existant environment in puppet.conf even when the classifier is controlling environment Change By: Nick Walker Priority: Normal Major 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-6802) Agent cannot compile catalog if it specifies an non-existant environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Nick Walker created an issue Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existant environment in puppet.conf even when the classifier is controlling environment Issue Type: Bug Assignee: Unassigned Created: 2016/10/07 8:58 AM Labels: tcse Priority: Normal Reporter: Nick Walker The Problem [root@agent201621-centos ~]# puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts
Jira (PDB-3090) (maint) update tk to 1.5.1 to avoid dependency conflict with PDB
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3090 (maint) update tk to 1.5.1 to avoid dependency conflict with PDB Issue Type: Bug Assignee: Unassigned Created: 2016/10/07 6:53 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PUP-6768) Implement 'lookup context' object in the lookup v5 API
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6768 Implement 'lookup context' object in the lookup v5 API Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-6800) Better error messaging around invalid class names
Title: Message Title Henrik Lindberg commented on PUP-6800 Re: Better error messaging around invalid class names The example looks more like a bug since class references are supposedly case independent. The fact that it worked a second time seems to indicate that this has nothing to do with the class name per se. I can imagine though that first vs. second time could lead to a different path through the logic and that there may be something wrong on the path used the first time - say using create_resources vs. something else - conditional logic written differently etc. IIRC, there has also been bugs related to case independent references that are now fixed - so, puppet version used matters here. Can you supply a simple self contained reproducer? Note that 'role::appserver::windows_2012R2' does not break the naming convention - it is ok to have underscores, digits and upper case letters as long as those are not the first in a name segment. This means that the issue here is not about "better errors when naming convention is broken", but something else. 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-6768) Implement 'lookup context' object in the lookup v5 API
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6768 Implement 'lookup context' object in the lookup v5 API Change By: Henrik Lindberg Assignee: 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 (PDOC-85) Handle the case of 4x functions and 3x stubs
Title: Message Title Henrik Lindberg commented on PDOC-85 Re: Handle the case of 4x functions and 3x stubs The right thing to do is: move all 3.x stubs' documentation to 4.x and add/fix the markup to yard remove the 3.x stubs Until that is done however (say, when making the function reference generator work) the sane thing to do is to use the 3.x variant if one exists. 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-6768) Implement 'lookup context' object in the lookup v5 API
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-6768
Implement 'lookup context' object in the lookup v5 API
Change By:
Thomas Hallgren
In Lookup (v5) as defined by PUP-6484, the data provider API is built on 4.x functions. A helper mechanism is needed since:\\* functions cannot hold state, and this is needed when implementing something like a key by key lookup from an external source (for session key, private cached data, etc.)* {{undef}} is valid value and cannot be used to signal "not found" * there needs to be a way for a called function to provide explanations of its actions, and these needs to be appropriately nested.To accommodate for this, all of the function-kinds (hashed_data, lookup_key, data_dig) should take an object of Puppet:: LookupInvocation LookupContext kind. This object has an API as follows:\\* LookupInvocation LookupContext ::new()Allows a helper to be created for the purpose of testing a data provider function directly* not_found()Handles all aspects of a key not being found (cache, trace, etc). This method does not return. This method must be called when there is no value for a root key, or no data available at all for a hashed_data function.* explain() || { < lambda producing message > }Adds a trace/explanation for the processing done to arrive at either not_found or found. The lambda is only called if explanations are wanted. (Alternatively allow being called with a message string). This method must be called for decisions made in the function that are of value when a user tries to understand where a value came from.* cache(key, value)Caches a value private to this function layer. The intended functionality is to allow a function to store a session key, RPC connection or similar object. The private values are not part of regular data and cannot be looked up externally. This method is of value since the function cannot hold any state. It is also much preferred over home-grown caching in the function implementation (which is hard to get right, and to correctly support different versions of puppet). Privately cached values are made immutable on addition, but the keys may be bound to new immutable values.* cache(hash) Caches all values in the hash.* cached_value(key)Returns an earlier privately cached value for the key* all_cached() | $key, $val | { }Returns an {{Iterable}} version (if not called with a lambda) of the immutable entries in the cache. (If an immutable hash is wanted from the result this can be achieved with Hash(all_cached()). (Using an Iterable prevents the mutable hash holding the cache from escaping into puppet as is).* environment_name()Returns the name of the environment the configuration is part of.* module_name()Returns the name of the module where the function is included in the respective configuration. Returns {{undef}} if the functions is part of the environment's configuration.The lookup feature manages the creation/nesting of instances during lookup such that the lookup function can be called from within a data provider function as well as a nested lookup taking place indirectly via some other calls that are not lookup related.
Jira (PUP-6768) Implement 'lookup context' object in the lookup v5 API
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6768 Implement 'lookup context' object in the lookup v5 API Change By: Thomas Hallgren Summary: Implement 'lookup invocation context ' object in the lookup v5 API 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: Thomas Hallgren Assignee: 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-6799) PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6799 PEZ 2016.5.x mono smoke integration fails with Unable to serialize non-Data type parameters unless a serializer is provided Change By: Thomas Hallgren Assignee: 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.
