Jira (PUP-3668) Chaining arrows not working as expected
Title: Message Title Andy Parker commented on PUP-3668 Re: Chaining arrows not working as expected Parham Doustdar, could you explain what you expect to occur? In the output you provide there isn't an error message, so I don't know what you are pointing out. Please explain the order that you think you are supposed to get and why and explain what you are getting instead. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3642) Remove environment name from URL path
Title: Message Title Andy Parker commented on PUP-3642 Re: Remove environment name from URL path I took a look. It looks like you are just moving the environment from the path to a parameter, and then handling it the same everywhere else. That seems completely reasonable to me. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3637) Change store report processor to write report in JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3637 Change store report processor to write report in JSON Issue Type: Bug Assignee: Unassigned Created: 2014/11/07 9:25 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker As part of getting rid of YAML in puppet, we also need to stop puppet from writing reports in YAML. Reports in YAML rely on type annotations which makes loading the data in other languages, or even in ruby, much harder than it should be. Add Comment
Jira (PUP-3644) move all legacy and v2.0 endpoints to v3
Title: Message Title Andy Parker commented on PUP-3644 Re: move all legacy and v2.0 endpoints to v3 Should the current /v2.0/environments stay where it is and make a /v3/environments that is the same thing? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3622) Including a class prohibits parameterized declaration later
Title: Message Title Andy Parker commented on PUP-3622 Re: Including a class prohibits parameterized declaration later Yes, I came to the same conclusion. I tested 3.6.0 and 3.4.0 and both showed the same error. This isn't a regression in 3.7.2. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3468) create test; production environment created when missing
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3468 create test; production environment created when missing Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3468) create test; production environment created when missing
Title: Message Title Andy Parker commented on PUP-3468 Re: create test; production environment created when missing Merged into master in 624eca Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3621) Environments::Cached#get! bypasses the environment cache.
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-3621 Environments::Cached#get! bypasses the environment cache. Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3621) Environments::Cached#get! bypasses the environment cache.
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3621 Environments::Cached#get! bypasses the environment cache. Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title Andy Parker updated an issue Puppet / PUP-3514 Future parser not showing line/column for error Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3602) Do not convert strings that are on the form 0edigits to floating point
Title: Message Title Andy Parker updated an issue Puppet / PUP-3602 Do not convert strings that are on the form 0edigits to floating point Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker updated an issue Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3300) Rework Puppet::Util::Checksums to not extend itself
Title: Message Title Andy Parker commented on PUP-3300 Re: Rework Puppet::Util::Checksums to not extend itself For functional review, this should not change any user visible functionality. The changes in the code where pretty minor and just refactored a bit of the structure around how the Checksum methods are used. These methods implement puppet's ability to use various digest algorithms (for certificates, I think) and checksums used for files. Since the checksum parameter is broken (PUP-1208), I think the way the user would exercise this functionality is via the digest_algorithm setting. Exploratory testing around the functionality of digest_algorithm would be a good review of the change. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3472) make acceptance/tests/environment/directory.rb more atomic
Title: Message Title Andy Parker assigned an issue to Eric Thompson Looks good, just needs a better commit message. Puppet / PUP-3472 make acceptance/tests/environment/directory.rb more atomic Change By: Andy Parker Assignee: AndyParker EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3615) Remove automatic string to number conversion
Title: Message Title Andy Parker commented on PUP-3615 Re: Remove automatic string to number conversion scanf? I don't think that name makes sense since we aren't reading the value to convert from a stream. Maybe parse_number(T Numeric, String) : T or to_numeric(String) : Numeric? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3472) make acceptance/tests/environment/directory.rb more atomic
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3472 make acceptance/tests/environment/directory.rb more atomic Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3472) make acceptance/tests/environment/directory.rb more atomic
Title: Message Title Andy Parker commented on PUP-3472 Re: make acceptance/tests/environment/directory.rb more atomic Merged into master in da2788 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3615) Remove automatic string to number conversion
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-3615 Remove automatic string to number conversion Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-3272 Remove support for yaml on the network Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3615) Remove automatic string to number conversion
Title: Message Title Andy Parker commented on PUP-3615 Re: Remove automatic string to number conversion Moses Mendoza, yes we are putting this in 3.7.4. We are fixing the bug in the future parser By putting it into 3.7.4 people will be able to try out changes before puppet 4. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1073) Common package name in two different providers
Title: Message Title Andy Parker commented on PUP-1073 Re: Common package name in two different providers Eric Sorenson, at the moment this is still targeted at PUP 4.0.0. Assuming that it doesn't get dropped in priority and has to get bumped from 4.0.0 to a later release, then we can tackle it. Right now my understanding is that we need to do all of the code removals, the JSON transition, and any other breaks before we'll get to this. However, maybe the client team has some cycles to tackle this before then (Kylo Ginsberg)? This isn't a backwards incompatible change, so other than it being a problem for longer, we can also release it in 4.1.0 if need be. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3580) Smoke test packages
Title: Message Title Andy Parker commented on PUP-3580 Re: Smoke test packages Windows 2012 64bit msi. 1. Verified that facter 2.3.0 is included 2. Verified that puppet 3.7.3 is included 3. Ran facter 4. Checked puppet man apply and puppet help apply 5. Ran notice(hi) 6. Checked that puppet service appears in the control panel (and it was running by default). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3600) Create support for binary content on the File type
Title: Message Title Andy Parker created an issue Puppet / PUP-3600 Create support for binary content on the File type Issue Type: New Feature Assignee: Andy Parker Components: DSL, Types and Providers Created: 2014/10/31 9:39 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Once the catalog is transferred in JSON, non-UTF-8 sequences will no longer be allowed in the content. This means that Files that have a content of some arbitrary data may or may not be able to be transferred. Henrik Lindberg suggested a solution to this that will allow us to do our switch to JSON but not require an entirely new catalog format. The idea is to create a function called binary(str) that takes a String and returns a Struct[data ="" String] where data is a UTF-8 compatible encoding of the bytes (not the characters) of the input String. The content parameter of File is then changed to accept either a String or a Struct[data ="" String]. When it receives a Struct[data ="" String] then the data element is decoded with the algorithm decided for the implementation of the binary(str) function. This solution should allow the follow manifests to continue to work:
Jira (PUP-3541) Remove client and server yaml directories
Title: Message Title Andy Parker updated an issue Puppet / PUP-3541 Remove client and server yaml directories Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3475) Plan transition to JSON
Title: Message Title Andy Parker commented on PUP-3475 Re: Plan transition to JSON I had completely left out adding in support to get binary data in file contents. I've now filed that as PUP-3600. Yeah, those were never really deprecated. I'll tag the tickets about the settings with DOCS so that we can see them for mentioning in documentation. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3544) Write lastrunreport in JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3544 Write lastrunreport in JSON Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3546 Modify exec node terminus to support JSON Change By: Andy Parker Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3542 Write statefile in JSON Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3546 Modify exec node terminus to support JSON Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3543) Write lastrunfile in JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3543 Write lastrunfile in JSON Change By: Andy Parker Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3542 Write statefile in JSON Change By: Andy Parker Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3543) Write lastrunfile in JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3543 Write lastrunfile in JSON Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3544) Write lastrunreport in JSON
Title: Message Title Andy Parker updated an issue Puppet / PUP-3544 Write lastrunreport in JSON Change By: Andy Parker Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3274) Remove old parser/evaluator
Title: Message Title Andy Parker commented on PUP-3274 Re: Remove old parser/evaluator Erik Daln as of 3.7, I think those now use the Puppet::Pops::Model::LambdaExpression for the AST and are implemented in the pops evaluator. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2716) ssl_server_ca_chain and ssl_client_ca_chain are dead settings
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2716 ssl_server_ca_chain and ssl_client_ca_chain are dead settings Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2716) ssl_server_ca_chain and ssl_client_ca_chain are dead settings
Title: Message Title Andy Parker commented on PUP-2716 Re: ssl_server_ca_chain and ssl_client_ca_chain are dead settings Merged into master in 5d9f09 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3468) create test; production environment created when missing
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3468 create test; production environment created when missing Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3472) make acceptance/tests/environment/directory.rb more atomic
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3472 make acceptance/tests/environment/directory.rb more atomic Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3602) Do not convert strings that are on the form 0edigits to floating point
Title: Message Title Andy Parker updated an issue Puppet / PUP-3602 Do not convert strings that are on the form 0edigits to floating point Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3602) Do not convert strings that are on the form 0edigits to floating point
Title: Message Title Andy Parker updated an issue Puppet / PUP-3602 Do not convert strings that are on the form 0edigits to floating point Change By: Andy Parker Sprint: PlatformServer2014-11-12 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3602) Do not convert strings that are on the form 0edigits to floating point
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3602 Do not convert strings that are on the form 0edigits to floating point Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3602) Do not convert strings that are on the form 0edigits to floating point
Title: Message Title Andy Parker commented on PUP-3602 Re: Do not convert strings that are on the form 0edigits to floating point Merged into stable in 2bf53e We also had to change how very large numbers got compared. The following example should have printed false, but instead it printed true. notice(4e12341234123412341234 == 4e12341234123412341235) The new rules are: 1. a scientific notation 0 will not be converted to a number 2. a value that results in Infinity in ruby will not be converted to a number. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title
Andy Parker commented on an issue
Re: Puppet resource broken when directory environments enabled
Merged into stable in fbc7e1
Add Comment
Puppet / PUP-3302
Puppet resource broken when directory environments enabled
When running puppet resource, the command fails for want of a 'none' environment {quote} puppet resource file /usr/share/puppet-dashboard-mirror ensure=directory source=/usr/share/puppet-dashboard recurse=true ignore='*log*' Error: /File[/usr/share/puppet-dashboard-mirror]: Failed to generate additional resources using 'eval_generate': Could not find ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3566) Remove support for versions in faces
Title: Message Title Andy Parker created an issue Puppet / PUP-3566 Remove support for versions in faces Issue Type: Bug Assignee: Andy Parker Components: Server Created: 29/Oct/14 9:57 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker The version functionality has never quite worked as advertised and ends up being more confusing for anyone than it is helpful. It also incredibly complicates a lot of how faces are loaded and work. The version support needs to be removed. In order to keep compatibility with nearly all faces in existence we should only remove all of the inner workings. The public calls to create or get a face by a version should continue to accept a second version argument, but simply ignore it. As a service to users/developers it should issue a debug message to say that the version is being ignored. In the extremely rare case that the version handling was in some way put to use, that code will break. Let's not try to do anything helpful about loading all versions and merging them together in any way. Fail fast if it is possible and no extra code, or just ignore the versions.
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title
Andy Parker commented on an issue
Re: Future parser not showing line/column for error
Merged into stable in https://github.com/puppetlabs/puppet/commit/3966e897e66abe974516a16e10918539dc02eeca
Add Comment
Puppet / PUP-3514
Future parser not showing line/column for error
We had a manifest that contains this: {code} File ['/etc/pam.d/sshd'] { {code} Obviously the space there is a mistake but the future parser gave me this back: {noformat} Error: Could not parse for environment production: _expression_ is not valid as a resource, resource-default, or resource-override at (slice () 'file'):(slice () 'line'):(slice ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker updated an issue Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters Change By: Andy Parker Sprint: PlatformServer2014-10-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3396) Add support for testing 4x functions in modules
Title: Message Title Andy Parker updated an issue Puppet / PUP-3396 Add support for testing 4x functions in modules Change By: Andy Parker Fix Version/s: PUP3.7.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker updated an issue Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker updated an issue Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker commented on an issue Re: Future parser, square brackets in references cause syntax errors related to non-ASCII characters Merged into stable in eabb6d Add Comment Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters After upgrading our puppet master to 3.7.2 we started to get syntax errors in our site.pp file. After some binary search/deletions we ended up with the attached example which does not seem to allow further deletions or the syntax error will disappear. The error always happens on the open square bracket of the reference in the resource parameter. It occ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2733) Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-2733 Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3475) Plan transition to JSON
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3475 Plan transition to JSON Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker commented on an issue Re: Future parser, square brackets in references cause syntax errors related to non-ASCII characters I've confirmed that this reproduces on my machine as well. The error that I get is Error: Could not parse for environment production: Syntax error at '[' at /Users/andy/Downloads/puppet_3.7_parse_error.pp:3:11. Add Comment Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters After upgrading our puppet master to 3.7.2 we started to get syntax errors in our site.pp file. After some binary search/deletions we ended up with the attached example which does not seem to allow further deletions or the syntax error will disappear. The error always happens on the open square bracket of the reference in the resource parameter. It occ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title
Andy Parker commented on an issue
Re: Future parser, square brackets in references cause syntax errors related to non-ASCII characters
3.6.0 appears to be good. I've bisected it down to [a commit that changes how {{}} is handled. This was a change for
PUP-2288
.
Add Comment
Puppet / PUP-3558
Future parser, square brackets in references cause syntax errors related to non-ASCII characters
After upgrading our puppet master to 3.7.2 we started to get syntax errors in our site.pp file. After some binary search/deletions we ended up with the attached example which does not seem to allow further deletions or the syntax error will disappear. The error always happens on the open square bracket of the reference in the resource parameter. It occ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-3396) Add support for testing 4x functions in modules
Title: Message Title Andy Parker commented on an issue Re: Add support for testing 4x functions in modules Should this ticket be closed out now? Add Comment Puppet / PUP-3396 Add support for testing 4x functions in modules When testing a single module with a typical disk layout, the module is usually located in a directory that cannot be used as a modulepath entry. The Loaders helper facade has no public way of adding a module under test to the configuration it builds. While there is nothing preventing a different configuration to be created and used as the loaders for ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker updated an issue Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters Change By: Andy Parker Fix Version/s: PUP3.7.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3559) Allow splat in interpolation to unfold and shrinkwrap
Title: Message Title
Andy Parker commented on an issue
Re: Allow splat in interpolation to unfold and shrinkwrap
I'm a big -1 on this functionality. Given that there is now the type system, users should be aware of what type of value they are dealing with. Calling join() is much clearer about the intent and immediately puts the general solution in front of them.
Add Comment
Puppet / PUP-3559
Allow splat in interpolation to unfold and shrinkwrap
When interpolating an Array it outputs a complete array with brackets and commas. If instead a shrinkwrapped concatenation of the content is wanted, the user has to call join from stdlib, or address the parts individually. Consider supporting unfolding as follows: {code} $a = [1,2,3] notice ${*$a} {code} The interpolation logic would then handle...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-3558) Future parser, square brackets in references cause syntax errors related to non-ASCII characters
Title: Message Title Andy Parker commented on an issue Re: Future parser, square brackets in references cause syntax errors related to non-ASCII characters Josh Cooper, I think PUP-3177 is unrelated. The problem there was the Puppet::Resource did its own parsing of the title to support resource references (Puppet::Resource acts as both a resource and a resource reference). This error is happening long before that point inside the lexer and parser. Add Comment Puppet / PUP-3558 Future parser, square brackets in references cause syntax errors related to non-ASCII characters After upgrading our puppet master to 3.7.2 we started to get syntax errors in our site.pp file. After some binary search/deletions we ended up with the attached example which does not seem to allow further deletions or the syntax error will disappear. The error always happens on the open square bracket of the reference in the resource parameter. It occ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because
Jira (PUP-3541) Remove client and server yaml directories
Title: Message Title
Andy Parker commented on an issue
Re: Remove client and server yaml directories
I think so too. I took a look in the directories on my machine (where I often run the server and agent together) and it didn't look like they would collide. I think we can just go ahead and keep the separate for now unless someone discovers that there is really no good reason to keep the separate.
Add Comment
Puppet / PUP-3541
Remove client and server yaml directories
Currently, some data that puppet saves is written to the {{yamldir}} (or {{clientyamldir}}) if it is YAML or to {{server_datadir}} (or {{client_datadir}}) if it is not. All data needs to be written to {{server_datadir}} for the master and {{client_datadir}} for the client, no matter if it is YAML or not. The {{yamldir}} settings can then be removed. ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title
Andy Parker commented on an issue
Re: Modify exec node terminus to support JSON
This one isn't strictly necessary. Since puppet doesn't really produce the YAML, it can also be left as it is.
Add Comment
Puppet / PUP-3546
Modify exec node terminus to support JSON
The exec node terminus currently expects the command is executes to print YAML to stdout. The terminus then parses this and constructs a {{Puppet::Node}} from the data. As part of the switch to JSON, the exec node terminus should extend its protocol to handle JSON. The exec node terminus reads the first line of the commands stdout. The first line *may*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3524) Switch from YAML and PSON to JSON
Title: Message Title Andy Parker commented on an issue Re: Switch from YAML and PSON to JSON I'm leaving out things like config files that puppet doesn't produce. This means things like the certificate extensions on an agent aren't on this list of items. I did create a ticket for the exec ENC, but it isn't something that really has to be done and we can decide to just close it won't fix with no detriment to other tickets. Add Comment Puppet / PUP-3524 Switch from YAML and PSON to JSON I'd like to move us away from PSON and onto a standard format. YAML is out of the question because it is either slow and unsafe (all of the YAML vulnerabilities) or extremely slow and safe (safe_yaml). MessagePack might be nice. It is pretty well specified, has a fairly large number of libraries written for it, but it doesn't do much to help us solve the ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Andy Parker commented on an issue Re: Facter logs should be surfaced during Puppet runs Shouldn't this be a facter ticket? And then have a ticket for Puppet to use the new facility? Add Comment Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Information logged by Hiera [is forwarded to Puppet loggers|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/puppet_logger.rb] when Hiera is running as part of a Puppet process. Facter should do the same thing. For Facter, this is especially critical since custom facts contain arbitrary user-written code that can have a variety of side effects... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3551) Strip non-UTF-8 data from run reports
Title: Message Title Andy Parker created an issue Puppet / PUP-3551 Strip non-UTF-8 data from run reports Issue Type: Improvement Assignee: Unassigned Created: 27/Oct/14 1:35 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker One of the consequences of using JSON and the existing serialization of reports is that it won't be able to handle non-UTF-8 showing up. Non-UTF-8 data would not show up from the catalog information (since it also has the same UTF-8 restriction), but it can show up in the output of the commands that puppet runs as part of applying a catalog. Puppet must be able to send the report about the run. It can't be stopped by some data that prevents a particular serialization mechanism from working correctly. In order to send the report puppet should strip any non-UTF-8 sequences in the report and replace them with something that can be serialized. Add Comment
Jira (PUP-3551) Strip non-UTF-8 data from run reports
Title: Message Title Andy Parker commented on an issue Re: Strip non-UTF-8 data from run reports Ideally the fact that the agent had to strip some data would be recorded somewhere in the report. Add Comment Puppet / PUP-3551 Strip non-UTF-8 data from run reports One of the consequences of using JSON and the existing serialization of reports is that it won't be able to handle non-UTF-8 showing up. Non-UTF-8 data would not show up from the catalog information (since it also has the same UTF-8 restriction), but it can show up in the output of the commands that puppet runs as part of applying a catalog. Puppet *mu... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Andy Parker commented on an issue Re: Facter logs should be surfaced during Puppet runs I added it to JSON All the Things because I noticed that the message the facter produces when it hits non-UTF-8 facts doesn't go through puppet's logging system, which means that it wouldn't make it into a report. I was thinking that part of making a good user experience for JSON All the Things would be to include logs about when non-UTF-8 data is hit. Can't do this for the master side, but it should be doable for the agent side. Add Comment Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Information logged by Hiera [is forwarded to Puppet loggers|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/puppet_logger.rb] when Hiera is running as part of a Puppet process. Facter should do the same thing. For Facter, this is especially critical since custom facts contain arbitrary user-written code that can have a variety of side effects... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PUP-3552) Use application/json Content-Type/Accept instead of PSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3552 Use application/json Content-Type/Accept instead of PSON Issue Type: Improvement Assignee: Unassigned Created: 27/Oct/14 1:47 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Once puppet is handling everything as JSON instead of PSON, we need to change from using application/pson (or variants) to application/json (strictly, don't accept just json or x-json or any other variations). In order to be mostly backwards compatible puppet should still accept PSON content types but only decode and encode them like JSON. When it does this it needs to issue a warning about using a deprecated format and that it is no longer fully functional. Add Comment
Jira (PUP-3475) Plan transition to JSON
Title: Message Title Andy Parker commented on an issue Re: Plan transition to JSON Someone please review that the various tickets I've entered in the epic for this covers what will need to be done for transitioning from YAML/PSON to JSON. Add Comment Puppet / PUP-3475 Plan transition to JSON Plan out how we can move from PSON to JSON in all cases where PSON is currently being used. There are backwards compatibility issues that need to be handled for this as well. At the very least we need to be able to provide users of older agents a good way of being told what is happening rather than Can't intern from JSON (or something equally unhelpful)... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3554) Validate all of the forge modules using future parser
Title: Message Title Andy Parker created an issue Puppet / PUP-3554 Validate all of the forge modules using future parser Issue Type: Task Assignee: Andy Parker Components: DSL Created: 27/Oct/14 2:47 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker As part of a quality check for the future parser we need to run puppet parser validate against all (or at least all of the latest versions) of the forge modules. Some of them won't parse, and we should confirm that it is a valid reason that they won't parse. Others may uncover bad error messages or various other problems. Any issues with the future parser that are uncovered should have tickets opened and then be fixed. Add Comment
Jira (PUP-2037) Switch rpm/deb package manifest dir to default directory environment.
Title: Message Title Andy Parker commented on an issue Re: Switch rpm/deb package manifest dir to default directory environment. Should the packages create the default environment? It could at the same time add a README that explains the structure. As long as it isn't a directory and file managed by the packaging system, the user will still have complete control over it. Add Comment Puppet / PUP-2037 Switch rpm/deb package manifest dir to default directory environment. In 3.6.0, we are deprecating the implicit manifest dir, and have created example directory environment manifest dirs, but we refrained from removing the deprecated '/etc/puppet/manifests' so as to not break people's systems on upgrade if they happen to be using implicit environments, since a production directory environment would immediately take preceden... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title
Andy Parker commented on an issue
Re: md5lite, mtime not honoured for file type/provider
I've targeted this at 3.7.3. Charlie Sharpsteen are you putting together a patch based on what you've learned?
Add Comment
Puppet / PUP-1208
md5lite, mtime not honoured for file type/provider
It seems I can't get the puppetmaster to honour the checksum = mtime setting, or the md5lite setting. So the following example has no performance improvement over just using md5: {code} file { /testtransfer: ensure = directory, recurse = remote, purge = true, checksum = mtime, source = puppet:///modules/${module_name}/bigfilesh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title Andy Parker updated an issue Puppet / PUP-1208 md5lite, mtime not honoured for file type/provider Change By: Andy Parker Fix Version/s: PUP3.7.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3514 Future parser not showing line/column for error Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1106) Resource refreshes don't check for failed dependencies
Title: Message Title Andy Parker assigned an issue to Unassigned Taking myself off of it. The consensus on the mailing list was that the approach was correct. What I still needed to check for was: code clarity, unintended side effects, test coverage, etc. Puppet / PUP-1106 Resource refreshes don't check for failed dependencies Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-3514 Future parser not showing line/column for error Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3505 Future parser handling undef's incorrectly Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Andy Parker commented on an issue Re: Future parser handling undef's incorrectly Merged into stable in 783217. Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3300) Rework Puppet::Util::Checksums to not extend itself
Title: Message Title
Andy Parker commented on an issue
Re: Rework Puppet::Util::Checksums to not extend itself
Merged into master in 9812ca
Add Comment
Puppet / PUP-3300
Rework Puppet::Util::Checksums to not extend itself
The comment in the code states: {code} # In Puppet 4 we should switch this to `module_function` to make these methods # private when this class is included. {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3538) Create terminii for JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3538 Create terminii for JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 4:33 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker All of the indirector terminii that currently use YAML need to have a JSON terminus written. In addition, the node terminus needs a WriteOnlyJson terminus so that we don't regress on Redmine 16753. Once all of those are in place, the defaults need to be switched to use them instead of YAML. Add Comment
Jira (PUP-3289) Remove deprecated serialization and dynamic facts settings
Title: Message Title
Andy Parker commented on an issue
Re: Remove deprecated serialization and dynamic facts settings
Merged into master in b2d846
Add Comment
Puppet / PUP-3289
Remove deprecated serialization and dynamic facts settings
{{catalog_format}} and {{dynamicfacts}} are deprecated and need to be removed.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3540) Remove all uses of PSON and replace with JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3540 Remove all uses of PSON and replace with JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:19 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Right now puppet uses something called PSON instead of JSON. This is all over the place. PSON needs to be removed and replaced with JSON. At the same time replace all uses of x.to_json or x.to_pson with JSON.generate(x.to_data_hash) and then delete all of the custom to_pson and to_json methods. Remove puppet/external/pson. Create a stubbed PSON module that simply forwards all calls to JSON. When a call against PSON is made it need to emit a deprecation warning. We can't simply remove PSON because a large number of modules appear to depend on it. Add Comment
Jira (PUP-3541) Remove client and server yaml directories
Title: Message Title Andy Parker created an issue Puppet / PUP-3541 Remove client and server yaml directories Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:31 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Currently, some data that puppet saves is written to the yamldir (or clientyamldir) if it is YAML or to server_datadir (or client_datadir) if it is not. All data needs to be written to server_datadir for the master and client_datadir for the client, no matter if it is YAML or not. The yamldir settings can then be removed. Question: can we just combine the client and server data dirs? What is the reason they are separate? Add Comment
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3542 Write statefile in JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:39 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Currently the statefile is written in YAML format. It needs to be changed to JSON. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-880) Remove localconfig Setting
Title: Message Title Andy Parker updated an issue Puppet / PUP-880 Remove localconfig Setting Change By: Andy Parker Ican'tfindanyreferencetothissetting,weshould deprecate justremove it. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-880) Remove localconfig Setting
Title: Message Title Andy Parker updated an issue Puppet / PUP-880 Remove localconfig Setting Change By: Andy Parker Summary: Deprecate Remove localconfigSetting Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-880) Deprecate localconfig Setting
Title: Message Title Andy Parker updated an issue Puppet / PUP-880 Deprecate localconfig Setting Change By: Andy Parker Fix Version/s: PUP4.x Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3543) Write lastrunfile in JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3543 Write lastrunfile in JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:43 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker The lastrunfile (last_run_summary.yaml) is written in YAML. It needs to be written in JSON. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3544) Write lastrunreport in JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3544 Write lastrunreport in JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:44 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker The lastrunreport (last_run_report.yaml) is written in YAML. It needs to be written in JSON. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3545) Deprecate YAML indirector terminii
Title: Message Title Andy Parker created an issue Puppet / PUP-3545 Deprecate YAML indirector terminii Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:46 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Once PUP-3538 is done, all of the indirector caches should be written in JSON by default. We can now deprecate the YAML terminii. We'll keep them around for a while in case people need to use them for compatibility with existing tools. Add Comment This message was sent by Atlassian
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3546 Modify exec node terminus to support JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:53 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker The exec node terminus currently expects the command is executes to print YAML to stdout. The terminus then parses this and constructs a Puppet::Node from the data. As part of the switch to JSON, the exec node terminus should extend its protocol to handle JSON. The exec node terminus reads the first line of the commands stdout. The first line may be a MIME type. The supported MIME types are application/json and application/yaml. If neither of these are found one the first line (ignoring whitespace), then the input is assumed to be application/yaml. The rest of the output is read and processed depending on what MIME type was given. When application/yaml is used (either explicitly or implicitly), the terminus should issue a deprecation warning. Add Comment
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Andy Parker updated an issue Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Andy Parker Affects Version/s: PUP3.7.1 Affects Version/s: PUP3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Andy Parker updated an issue Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3334) Changes to environment.conf are not being picked up, even when environment timeout is set to 0.
Title: Message Title Andy Parker updated an issue Puppet / PUP-3334 Changes to environment.conf are not being picked up, even when environment timeout is set to 0. Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Affects Version/s: PUP3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3201) Validation thinks that an Undef instance is of type Runtime
Title: Message Title Andy Parker updated an issue Puppet / PUP-3201 Validation thinks that an Undef instance is of type Runtime Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3227) Upgrade conflict: puppetmaster-common and puppet-common
Title: Message Title Andy Parker updated an issue Puppet / PUP-3227 Upgrade conflict: puppetmaster-common and puppet-common Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Andy Parker updated an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3401) Type system does not handle Pattern correctly
Title: Message Title Andy Parker updated an issue Puppet / PUP-3401 Type system does not handle Pattern correctly Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
