Jira (PUP-6062) Allow non-root environments
Title: Message Title Kylo Ginsberg commented on PUP-6062 Re: Allow non-root environments Btw, Timothy Nelson, I should have mentioned that the reason passenger support is deprecated is because of: https://docs.puppetlabs.com/puppetserver/2.3/services_master_puppetserver.html. 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 (PUP-6062) Allow non-root environments
Title: Message Title Timothy Nelson commented on PUP-6062 Re: Allow non-root environments Kylo/Chris/Eric: Thanks for the consideration given to the idea. Kylo: Thanks. I only set up Passenger because everyone on the 'Net recommended it. We're not ready to migrate now, but, thanks to your heads-up, we should be ready by the time we're ready to migrate to Puppet 5.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 (PUP-6075) Solution to optimize resolution of TypeReference for known Resource types is broken
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6075 Solution to optimize resolution of TypeReference for known Resource types is broken Change By: Henrik Lindberg Release Notes Summary: bug in not yet released code Release Notes: Not Needed 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 (PUP-6075) Solution to optimize resolution of TypeReference for known Resource types is broken
Title: Message Title Henrik Lindberg commented on PUP-6075 Re: Solution to optimize resolution of TypeReference for known Resource types is broken merged to master at: 5a00105 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 (PUP-6028) Treat unresolved type references as errors instead of being a Resource type
Title: Message Title Henrik Lindberg commented on PUP-6028 Re: Treat unresolved type references as errors instead of being a Resource type The simplest thing would be to consult "known_resource_types" although that is a misnomer as it only contains those that are loaded. A first implementation could simply do what the 3x runtime does when encountering a resource type; it gets loaded. The 4x loader then simply adds a type alias for that type. 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 (PUP-5843) Optimize resolution of TypeReference for known Resource types
Title: Message Title Thomas Hallgren commented on PUP-5843 Re: Optimize resolution of TypeReference for known Resource types I found a problem with the PR for this issue. Created PUP-6075 since this one is already resolved. 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 (PUP-6075) Solution to optimize resolution of TypeReference for known Resource types is broken
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6075 Solution to optimize resolution of TypeReference for known Resource types is broken Issue Type: Bug Assignee: Thomas Hallgren Created: 2016/03/20 8:33 AM Fix Versions: PUP 4.5.0 Priority: Normal Reporter: Thomas Hallgren The solution for optimizing resolution of type references for known resource types does not work as intended. This is because the static loader registers these types using a TypedName where the name is capitalized. The TypeParser will always attempt to load using a downcased name so it never finds anything even if it uses a loader. Add Comment
Jira (FACT-1294) Windows facter.rb lookup of libfacter has hard-coded layout assumptions
Title: Message Title Michael Smith commented on FACT-1294 Re: Windows facter.rb lookup of libfacter has hard-coded layout assumptions Branan Riley my thought on this was to add a compile-time option to declare how to find the Ruby library, which could be a relative path (as we usually do for building into the MSI). That should simplify the logic in facter.rb. 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 (PDB-2235) (maint) Unpin beaker
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2235 (maint) Unpin beaker Change By: Ryan Senior Fix Version/s: PDB 4.0.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 (PUP-6072) Add --runreport option
Title: Message Title Michal Ruzicka moved an issue Puppet / PUP-6072 Add --runreport option Change By: Michal Ruzicka Workflow: Release Engineering Scrum Team Workflow Key: PA PUP - 251 6072 Project: Puppet Agent 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 (PUP-6067) Pip3 provider does not include features from Pip
Title: Message Title
Michael Smith created an issue
Puppet / PUP-6067
Pip3 provider does not include features from Pip
Issue Type:
Bug
Affects Versions:
PUP 4.2.0
Assignee:
Unassigned
Created:
2016/03/17 12:05 PM
Fix Versions:
PUP 4.4.1
Priority:
Normal
Reporter:
Michael Smith
The Pip3 provider was introduced in Puppet 4.2.0. The implementation was incomplete, as it doesn't specify the features provided by Pip, and using :parent doesn't inherit features.
That should only be a problem for people trying to use the Pip3 provider, but due to chance that provider is selected when no more appropriate providers are available (which happens often in module spec testing). The result is module spec tests trying to use many package features start failing in Puppet 4.2.0. See https://github.com/cdenneen/puppet-test/ for a simple example instantiating package {'foo': ensure => '1.0.0-1'}.
Jira (PDB-2332) Benchmark does not POST command version
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2332 Benchmark does not POST command version Change By: Ryan Senior Fix Version/s: PDB 4.0.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 (PUP-6029) use function local type aliases instead of string in all 4.x functions
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6029 use function local type aliases instead of string in all 4.x functions Change By: Sean Griffin Status: Ready for CI Test 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 (PUP-5836) Splat operator should turn Iterator into an array
Title: Message Title Erik Dalén commented on PUP-5836 Re: Splat operator should turn Iterator into an array Even double splatting to get that generated array into a function argument list seems to work, nice $ puppet apply -e 'notice(fqdn_rand(**[11,20].reverse_each))' Notice: Scope(Class[main]): 19 Notice: Compiled catalog for river.dalen.io in environment production in 0.07 seconds Notice: Applied catalog in 0.01 seconds Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to
Jira (PUP-909) Speed up type inference
Title: Message Title Sean Griffin updated an issue Puppet / PUP-909 Speed up type inference Change By: Sean Griffin QA Risk Assessment: Low QA Status: Reviewed 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 (PUP-6072) Add --runreport option
Title: Message Title Kylo Ginsberg commented on PUP-6072 Re: Add --runreport option +1 on Richard Clamp's idea, although I'm also wondering about a variant that doesn't require the :$(puppet configprint lastrunreport step (a second invocation of puppet seems a bit unfortunate) and if we could make do with some way of indicating "and what you're configured for already". E.g. puppet apply --lastrunreport=/tmp/my_special_report.yaml:lastrunreport_default or some such thing. 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 (PUP-6028) Treat unresolved type references as errors instead of being a Resource type
Title: Message Title Thomas Hallgren commented on PUP-6028 Re: Treat unresolved type references as errors instead of being a Resource type Every known resource type is currently contained in a Puppet::Resource::TypeCollection contained in an environment under the name known_resource_types. Is the general idea that the environment loader should have access to that? If the answer to that question is yes, then how about visibility between modules for those types? Should that be considered at this point? 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 (PUP-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5714 Add a 'git' checksum type for file resource sources Change By: Josh Cooper One of the downsides of static catalog compilation is that the master needs to checksum all the files referenced in a catalog ahead of time . Without static catalogs , to include their checksums in the catalog master computes checksums during every puppet agent run (across N nodes). With static catalogs , which can be intense on the master computes checksums once per compilation (across N nodes).Checksums are compute and i/o resources intensive . With Direct Puppet, we're providing a linkage between a git-managed backing store and the file content but aren't (yet) leveraging the fact that git inherently knows the checksum of every file at every commit-ref under its control. This seems like it'd be a good idea from a resource-conservation standpoint, plus it's bloody awesome.Implementing this would require either embedding/requiring git on the agent or re-creating the algorithm git uses to generate its checksums ( see http://git-scm.com/book/en/v2/Git-Internals-Git-Objects#Object-Storage for the gory details ), but the server could simply query the file-sync service store (for PE) or user-specified git backend (for OSS) during catalog compilation and save some work.This isn't slated for a particular release but came up out of some internal discussion and I wanted to capture it in a ticket for future prioritization. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this messag
Jira (PUP-6072) Add --runreport option
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6072 Add --runreport option Change By: Kylo Ginsberg Sprint: Client Triage 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 (PDB-2537) test indexes! on migration in different schema in master
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2537 test indexes! on migration in different schema in master Change By: Wyatt Alt Story Points: 1 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 (PUP-6061) Puppet - Passenger Could not spawn process for application
Title: Message Title Chris Price commented on PUP-6061 Re: Puppet - Passenger Could not spawn process for application Bharath Have you considered using Puppet Server (via the puppetserver distro packages) instead of Passenger? This is our recommended path for the future, and we intend to remove support for Webrick and Passenger eventually. Michael Stahnke can you provide any information on how to get Passenger working with PC1/Puppet 4? My understanding is that it requires building Passenger instead of using the gem? 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 (FACT-1271) Generate message catalogs, review and mark translatable strings
Title: Message Title Michael Smith updated an issue Facter / FACT-1271 Generate message catalogs, review and mark translatable strings Change By: Michael Smith Sprint: i18n 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 (HI-306) Hiera CLI optparse problems with -m
Title: Message Title Sean Griffin updated an issue Hiera / HI-306 Hiera CLI optparse problems with -m Change By: Sean Griffin QA Risk Assessment: Low QA Status: Reviewed 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 (PUP-5233) puppet inspect is using wrong path for catalog data
Title: Message Title Jo Rhett commented on PUP-5233 Re: puppet inspect is using wrong path for catalog data Any chance this will get into 4.4.1 or will it be 4.5? – for the Learning Puppet book 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 (FACT-1193) Add node definition for Fedora 23 (i386, x86_64) to Facter
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1193 Add node definition for Fedora 23 (i386, x86_64) to Facter Change By: Kylo Ginsberg Sprint: Client Platform Additions 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 (FACT-1371) Build failure on cisco-wrlinux5 - leatherman locale
Title: Message Title Michael Smith commented on FACT-1371 Re: Build failure on cisco-wrlinux5 - leatherman locale Fixed by merging Facter#stable to master. 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 (PDB-2539) Set up a performance testing system for PuppetDB
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2539 Set up a performance testing system for PuppetDB Issue Type: Epic Assignee: Unassigned Created: 2016/03/16 4:28 PM Priority: Normal Reporter: Wyatt Alt 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.goog
Jira (PUP-2359) Add a umask option to set the agent's umask predictably
Title: Message Title Andy Fraley assigned an issue to Andy Fraley Puppet / PUP-2359 Add a umask option to set the agent's umask predictably Change By: Andy Fraley Assignee: Andy Fraley 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 (PUP-5990) Lookup data provider should allow dot in %{key.subkey} to be escaped
Title: Message Title
Henrik Lindberg commented on PUP-5990
Re: Lookup data provider should allow dot in %{key.subkey} to be escaped
Merged to stable at: 8f736b4
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 (FACT-1373) Facter with external fact containing a facter call fork-bombs the node
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1373 Facter with external fact containing a facter call fork-bombs the node Change By: Kylo Ginsberg Scrum Team: Client Platform 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 (FACT-1272) Create Facts schema translation tooling
Title: Message Title Michael Smith updated an issue Facter / FACT-1272 Create Facts schema translation tooling Change By: Michael Smith Sprint: i18n 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 (PUP-5825) systemd service provider always enables service in chroot
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5825 systemd service provider always enables service in chroot Change By: Kylo Ginsberg Sprint: Client Triage 2016-04-20 (Bigga Bugs) 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 (PUP-6064) Optional type misinterpreted by epp() and inline_epp() in puppet 4.4.0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6064 Optional type misinterpreted by epp() and inline_epp() in puppet 4.4.0 Change By: Henrik Lindberg Story Points: 1 Release Notes Summary: A regression in the functions epp, and inline_epp caused given undef values to be treated as missing given arguments. Sprint: Language 206-04-06 Scrum Team: Language Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this mes
Jira (PUP-5617) agent stalls when connection with master is dropped
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Sean Griffin QA Status: Reviewed 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 (PUP-5843) Optimize resolution of TypeReference for known Resource types
Title: Message Title Eric Thompson commented on PUP-5843 Re: Optimize resolution of TypeReference for known Resource types is there anyway to validate this from user feature level? 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 (HI-504) Allow interpolated keys to be quoted and contain dot characters
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Hiera / HI-504 Allow interpolated keys to be quoted and contain dot characters Change By: Thomas Hallgren Assignee: Henrik Lindberg 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 (PDB-2441) Commands should be submitted only as bytes
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2441 Commands should be submitted only as bytes Change By: Ryan Senior Fix Version/s: PDB 4.1.0 Fix Version/s: PDB 4.0.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 (PUP-6069) Make docstring available from Puppet Server environment_classes endpoint
Title: Message Title Henrik Lindberg commented on PUP-6069 Re: Make docstring available from Puppet Server environment_classes endpoint That is not going to work well at all, as the "doc string" available at runtime is raw source text, it contains yard-tags etc. The job of extracting documentation and formatting it is a job for Puppet Strings. In that process there are also many things that can go wrong (badly formatted things, wrong tags, etc). The puppet runtime has no features for this. The only thing that is available is the source text, plus the offset and length of the parsed AST objects in source. This information is used by Puppet Strings. We should not put "Puppet Strings" back into the runtime. I would therefore like to close this as a "won't do" for puppet. The structured information that is needed is made available by Puppet Strings in JSON format. A UI could pick that up for presentation (possibly with timestamp information to indicate how old it is; as it is a bit on the heavy side to always keeping it up to date. Re-Generation could be triggered by deployment, but the UI must be prepared to handle that information may not be available etc.). 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 (PUP-6058) Duplicate resource error on indirectly included class
Title: Message Title Henrik Lindberg commented on PUP-6058 Re: Duplicate resource error on indirectly included class I am sorry, are you saying the problem is that there is no error when evaluating the attached test.pp ? If so, how did you expect that to fail and why? I had attached the working test case I assume that is a reference to the attached "test.pp" , and not the description (which I may have mangled). 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 (PUP-5889) Add a --strict flag to Puppet
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5889 Add a --strict flag to Puppet Change By: Henrik Lindberg Assignee: Branan Riley 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 (PUP-6050) lookup cli --unpack-arrays broken
Title: Message Title Henrik Lindberg commented on PUP-6050 Re: lookup cli --unpack-arrays broken Should we deprecate this odd feature? No one seems to understand what it is good for. More like trying to derive meaning by looking at a bowl of Ramen... 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 (PUP-6050) lookup cli --unpack-arrays broken
Title: Message Title R.I.Pienaar commented on PUP-6050 Re: lookup cli --unpack-arrays broken I have no suggestions for a word that distill the behaviour down to a single word that might convoy what this does hehe. This and most of the lookup option keys need better docs I found, ideally with sample transformations shown as in given this data in this data comes out. The deep merge has some of that, I managed to figure those out by looking at its comments and not the puppet ones 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.
