Jira (PDOC-130) linebreaks cause problems
Title: Message Title William Yardley updated an issue Puppet Strings / PDOC-130 linebreaks cause problems Change By: William Yardley Attachment: puppet-strings1.png 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-130) linebreaks cause problems
Title: Message Title William Yardley commented on PDOC-130 Re: linebreaks cause problems ps - Just realized if you indent, it behaves as expected. However, the unpredictable behavior when you don't indent still seems like a bug. 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-131) generate README from puppet-strings
Title: Message Title William Yardley created an issue Puppet Strings / PDOC-131 generate README from puppet-strings Issue Type: New Feature Affects Versions: PDOC 0.99.0 Assignee: Unassigned Created: 2016/10/24 9:34 PM Priority: Normal Reporter: William Yardley Is it possible to generate a module's README itself from puppet-strings? I first thought that this was possible (and some folks on the modules team seemed to think it was feasible), but from brief testing of the examples, and looking at the help text, it seems like typically things go the other way (a README html file is generated from the README). It would be ideal (IMHO) to be able to include descriptions for the various typical sections in heredocs within the module, and have puppet-strings generate the README, including the examples and the parameters and their descriptions. Add Comment
Jira (PDOC-130) linebreaks cause problems
Title: Message Title William Yardley created an issue Puppet Strings / PDOC-130 linebreaks cause problems Issue Type: Bug Affects Versions: PDOC 0.99.0 Assignee: Unassigned Created: 2016/10/24 9:27 PM Priority: Normal Reporter: William Yardley Creating long descriptions doesn't seem to work optimally; typically, I'd want to wrap at 80 or 140 characters, but a newline seems to confuse puppet-strings. If this is expected behavior, the limitation should be documented better. For example, if you try to wrap lines for a long description, e.g., # @param package_source [String] The source for the package. Possible values # are undef (default), meaning the package will be installed from the
Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title Brian Cain commented on FACT-1441 Re: Add "virtualization" fact that identifies AWS, Azure, etc How reliable is it for us to build these methods into facter? Will grepping for unknown-245 in var/lib/dhcp/dhclient.eth0.leases always work for us in the future? Or curling for FullConfig in /var/lib/waagent/GoalState.1.xml? None of these seem like solid future proof ways for determining Azure. What happens if those change? From the original ticket FACT-1383, we have an endpoint that we can query but it will only return data if it's about to go under maintenance (otherwise it returns empty). It also claims there's an InstanceInfo endpoint but I haven't seen much documentation on that endpoint or if it 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-6840) Establish revert policy for failing changes
Title: Message Title John Duarte created an issue Puppet / PUP-6840 Establish revert policy for failing changes Issue Type: Improvement Assignee: Unassigned Created: 2016/10/24 2:28 PM Priority: Normal Reporter: John Duarte We have encountered times where merged code changes have resulted in unexpected failures in testing pipelines. We need to ensure that we can return those pipelines to a green state quickly. Therefore, a clear policy for reverting code changes that result in testing pipeline failures should be established. This policy needs to define the time frame for the revert as well as the communication protocol back to the original contributor. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-5931) puppet config print does not work if you are not the master
Title: Message Title
Sean Houghton commented on PUP-5931
Re: puppet config print does not work if you are not the master
A workaround is to explicitly set the environment to `production` on the command line, even if you're setting the environment option.
{{puppet agent --environment=production config set server foo.bar.com puppet agent --environment=production config set environment not_production}}
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 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-6775) acceptance: Newlines break Puppet tag validation
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6775 acceptance: Newlines break Puppet tag validation Change By: Eric Thompson QA Status: Reviewed 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-3772) Provide a package provider to manage Puppet modules
Title: Message Title Kenaz Kwa commented on PUP-3772 Re: Provide a package provider to manage Puppet modules Tim Purkerson - does Nick's solution work for you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Andreas Wilke commented on PUP-6660 Re: cached catalogs setting not respected when --test is specified I'm using the puppet agent -t option at demos to show that the agent is still running with cached catalog when i updated my code with code manager and now i can control when the catalog will be updated. At command line it was easy to show that the agent is still using cached catalog. Now this option has gone and i need to tell them: Trust me, the agent is still using the cached catalog in the background . Would be great if we could have the option --use_cached_catalog. 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-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Moses Mendoza commented on PUP-6188 Re: Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Kenn Hussey confirmed 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-6839) Bump version.rb for 1.8.0 release
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-6839 Bump version.rb for 1.8.0 release Change By: Maggie Dreyer Assignee: Maggie Dreyer 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-6839) Bump version.rb for 1.8.0 release
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6839 Bump version.rb for 1.8.0 release Change By: Moses Mendoza 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-6839) Bump version.rb for 1.8.0 release
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6839 Bump version.rb for 1.8.0 release Issue Type: Task Assignee: Unassigned Created: 2016/10/24 9:30 AM Fix Versions: PUP 4.8.0 Priority: Blocker Reporter: Moses Mendoza lib/puppet/version.rb needs to be updated to 4.8.0 in puppet/master in anticipation of pending release. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6188 Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Change By: Kenn Hussey Fix Version/s: PUP 4.8.0 Fix Version/s: PUP 4.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Rob Reynolds commented on PUP-5652 Re: Windows Package provider does not work with Installshield with MSI files Corey Osman Internet has never been required. You've been able to use internal sources since 2011 when Chocolatey first came out. Enterprise editions not required. Too bad for misinformation. 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-1356) External facts should be able to return structured data
Title: Message Title Maggie Dreyer commented on FACT-1356 Re: External facts should be able to return structured data This got merged Friday afternoon. It's good to go for 1.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 (PDB-3111) (MAINT) Fix concurrent command proc test issue
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3111 (MAINT) Fix concurrent command proc test issue Change By: Ryan Senior Sprint: SE 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3111) (MAINT) Fix concurrent command proc test issue
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3111 (MAINT) Fix concurrent command proc test issue Change By: Ryan Senior Team: Systems Engineering 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-3113) (maint) Pursue serialization failure in two places
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3113 (maint) Pursue serialization failure in two places Change By: Ryan Senior Sprint: SE 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3113) (maint) Pursue serialization failure in two places
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3113 (maint) Pursue serialization failure in two places Change By: Ryan Senior Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3113) (maint) Pursue serialization failure in two places
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3113 (maint) Pursue serialization failure in two places Change By: Ryan Senior Team: Systems Engineering 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-3113) (maint) Pursue serialization failure in two places
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3113 (maint) Pursue serialization failure in two places Change By: Ryan Senior Story Points: 1 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.
