Jira (PUP-4206) Fedora package naming convention doesn't match acceptance install assumptions
Title: Message Title Kylo Ginsberg commented on PUP-4206 Re: Fedora package naming convention doesn't match acceptance install assumptions Matthaus Owens should we close this? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4237) Add puppet_gem provider for managing puppet-agent gems
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4237 Add puppet_gem provider for managing puppet-agent gems Change By: Kylo Ginsberg Sprint: Client 2015-04-01 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4237) Add puppet_gem provider for managing puppet-agent gems
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4237 Add puppet_gem provider for managing puppet-agent gems Issue Type: Improvement Assignee: Kylo Ginsberg Created: 2015/03/17 8:53 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Kylo Ginsberg puppet-agent packages introduce the concept of a puppet-agent ruby distinct from the system ruby. Given this, the built-in gem provider can no longer be used to manage puppet-agent's own gems, so it makes sense to add a provider for that purpose. This can be modeled on the pe_gem provider, which served a similar purpose. Add Comment
Jira (PUP-4237) Add puppet_gem provider for managing puppet-agent gems
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4237 Add puppet_gem provider for managing puppet-agent gems Change By: Kylo Ginsberg Scrum Team: Client Platform Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (FACT-853) Move native facter codebase to facter#master
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-853 Move native facter codebase to facter#master Change By: Kylo Ginsberg Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4127) Add migration check for type mismatch in case/selector options
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4127 Add migration check for type mismatch in case/selector options Change By: Henrik Lindberg Issue Type: Improvement New Feature Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4127) Add migration check for type mismatch in case/selector options
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4127 Add migration check for type mismatch in case/selector options Change By: Henrik Lindberg Issue Type: Sub-task Improvement Parent: PUP-4121 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4126) Add migration check for type mismatch in equality test
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4126 Add migration check for type mismatch in equality test Change By: Henrik Lindberg Issue Type: Sub-task New Feature Parent: PUP-4121 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4223) Smoke test packages
Title: Message Title Kylo Ginsberg commented on PUP-4223 Re: Smoke test packages Pretty sure we spec'd mesquite. But close enough. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3886) Add yumrepo resource spec integration tests
Title: Message Title Michael Smith assigned an issue to QA Puppet / PUP-3886 Add yumrepo resource spec integration tests Change By: Michael Smith Status: Ready for CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3974) ensure puppet apply source_attribute acceptance tests touch all checksums
Title: Message Title Michael Smith assigned an issue to QA Puppet / PUP-3974 ensure puppet apply source_attribute acceptance tests touch all checksums Change By: Michael Smith Status: Ready for CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4125) Add migration check for upper case bare word evaluation
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4125
Add migration check for upper case bare word evaluation
Change By:
Henrik Lindberg
RationaleThis migration check is of value since it is a common mistake to use an uppercase bare word e.g. {{Debian}} with the intent that this is a {{String}} when it in 4.0 is an instance of {{Type}}. Note that not all usage of UC bareword can be flagged, since they appear as types also in 3x (i.e. references to either a resource type e.g. {{File}}, or as a reference to a specific resource e.g. {{File[foo]}}).Instead we need to check the evaluated result of case/selector options, and report if the result is a Type instance. We do the same for evaluation of comparison expressions{code}==, !=, <, >, <=, =>{code} as 3.x puppet code never compare on type. We also need to check the LHS of{code}=~ and !~{code} if it is a Type instance. In these cases we report the location of the operator (since we otherwise would have to track deeply where a value came from in the LHS and RHS expressions) - the user should be able to figure it out (and most will be immediate operands so problem is easy to spot).It is not anticipated that users have a frequent reason to place puppet resource type references in arrays or hashes - thus the intent is most likely that they should be quoted. There are valid cases though when relationships are formed:e.g - something like this:$a = [ MyType, MyType::Special ]$b = [ MyOtherType, MyOtherType::Special ]$a -> $bIt would be irritating to be told to quote those UC bare words (it would be wrong). Instead, since we are instrumenting comparison and matching evaluation we will catch cases where such structures are used in conditionals (which is really what we care about).This will also catch use of the {{in}} operator with a LHS being an UC bareword since in uses the implementation of the comparison operators.ImplementationAdd the issue {{MIGRATE4_UC_BAREWORD_IS_TYPE}} to {{MigrationIssues}} with the text {code} "Upper cased non quoted word '#{word}' evaluates to a Type (3.x evaluates to a String)" {code} Add a method {{report_uc_bareword_type(value, o)}} where {{o}} is the semantic object to the {{MigrationChecker}} that checks and reports if the value is a type instance.Add calls to the {{report_uc_bareword_type}} method from all comparison operators, equality operators, match operators, case and selector option evaluation, and in operator (some of these are probably already covered by the equality and comparison operators).(Add API stubs to the {{MigrationChecker}} in the puppet repository, and the specific methods to the implementation in the module created in PUP-4149).
Add Comme
Jira (PUP-4125) Add migration check for upper case bare word evaluation
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4125
Add migration check for upper case bare word evaluation
Change By:
Henrik Lindberg
RationaleThis migration check is of value since it is a common mistake to use an uppercase bare word e.g. {{Debian}} with the intent that this is a {{String}} when it in 4.0 is an instance of {{Type}}. Note that not all usage of UC bareword can be flagged, since they appear as types also in 3x (i.e. references to either a resource type e.g. {{File}}, or as a reference to a specific resource e.g. {{File[foo]}}).Instead we need to check the evaluated result of case/selector options, and report if the result is a Type instance. We do the same for evaluation of comparison expressions { { code} == }} , {{ != }} , {{ < }} , {{ > }} , {{ <= }} , {{ => {code } } as 3.x puppet code never compare on type. We also need to check the LHS of { { code} =~ }} and {{ !~ {code } } if it is a Type instance. In these cases we report the location of the operator (since we otherwise would have to track deeply where a value came from in the LHS and RHS expressions) - the user should be able to figure it out (and most will be immediate operands so problem is easy to spot).It is not anticipated that users have a frequent reason to place puppet resource type references in arrays or hashes - thus the intent is most likely that they should be quoted. There are valid cases though when relationships are formed:e.g - something like this:$a = [ MyType, MyType::Special ]$b = [ MyOtherType, MyOtherType::Special ]$a -> $bIt would be irritating to be told to quote those UC bare words (it would be wrong). Instead, since we are instrumenting comparison and matching evaluation we will catch cases where such structures are used in conditionals (which is really what we care about).This will also catch use of the {{in}} operator with a LHS being an UC bareword since in uses the implementation of the comparison operators.ImplementationAdd the issue {{MIGRATE4_UC_BAREWORD_IS_TYPE}} to {{MigrationIssues}} with the text "Upper cased non quoted word '#{word}' evaluates to a Type (3.x evaluates to a String)"Add a method {{report_uc_bareword_type(value, o)}} where {{o}} is the semantic object to the {{MigrationChecker}} that checks and reports if the value is a type instance.Add calls to the {{report_uc_bareword_type}} method from all comparison operators, equality operators, match operators, case and selector option evaluation, and in operator (some of these are probably already covered by the equality and comparison operators).(Add API stubs to the {{MigrationChecker}} in the puppet repository, and the specific methods to the implementation in the module created in PUP-4149).
Jira (PUP-4125) Add migration check for upper case bare word evaluation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4125 Add migration check for upper case bare word evaluation Change By: Henrik Lindberg Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4125) Add migration check for upper case bare word evaluation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4125 Add migration check for upper case bare word evaluation Change By: Henrik Lindberg Issue Type: Sub-task Bug Parent: PUP-4121 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4050) Acceptance suite and install.rb use incorrect paths on Windows for codedir
Title: Message Title Josh Cooper commented on PUP-4050 Re: Acceptance suite and install.rb use incorrect paths on Windows for codedir Now that beaker fixes have been merged, I think this is a "simple" matter of moving the beaker pin (in puppet's acceptance/Rakefile) and retesting. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. On PR to stable is enough, will merge it to master at the same time Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Henrik Lindberg Yeah, totally. I think we'll be releasing 4.0 RCs before 3.7.5. Do two PRs, or expect that we'll be merging up real soon? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4124) Add migration check for "empty string is true"
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4124 Add migration check for "empty string is true" Change By: Henrik Lindberg Issue Type: Sub-task New Feature Parent: PUP-4121 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-1019) respond with 503 when database is unavailable
Title: Message Title Charlie Sharpsteen commented on PDB-1019 Re: respond with 503 when database is unavailable +1 on this. Today I bent the database out of shape on a PE install and spent a good 20 minutes trying to figure out why compilation was failing with 404 "Not found" errors when trying to replace facts. If the error message indicated that the PuppetDB server was in a failure state and couldn't connect to Postgres, I would have zeroed in on the problem much more quickly. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4088) update puppet-agent path acceptance for Windows 2003 and 32-bit app on 64-bit OS
Title: Message Title Michael Smith assigned an issue to QA Puppet / PUP-4088 update puppet-agent path acceptance for Windows 2003 and 32-bit app on 64-bit OS Change By: Michael Smith Status: Ready for CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Henrik Lindberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data The environment function must provide a value for the hash key 'production_module::a', and not just 'a' for it to be looked up for the parameter in question. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Nicholas Fagerlund can you retarget the PR to stable as this is affects 3.7.5 ? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-1180) Status: (query) Ensure aggregated functionality is designed well in detail
Title: Message Title Wyatt Alt commented on PDB-1180 Re: Status: (query) Ensure aggregated functionality is designed well in detail The design doc I'm working on is here: https://docs.google.com/a/puppetlabs.com/document/d/1UyaRJT3kSSQmqqkyd9tagC9sk5TY0ZmhbKuEqWnhoeI/edit Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-1197) ConsoleDB: (query) Ensure metrics and logs are anonymized
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1197 ConsoleDB: (query) Ensure metrics and logs are anonymized Change By: Wyatt Alt Comment: The design doc I'm working on is here:https://docs.google.com/a/puppetlabs.com/document/d/1UyaRJT3kSSQmqqkyd9tagC9sk5TY0ZmhbKuEqWnhoeI/edit Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDB-1197) ConsoleDB: (query) Ensure metrics and logs are anonymized
Title: Message Title Wyatt Alt commented on PDB-1197 Re: ConsoleDB: (query) Ensure metrics and logs are anonymized The design doc I'm working on is here: https://docs.google.com/a/puppetlabs.com/document/d/1UyaRJT3kSSQmqqkyd9tagC9sk5TY0ZmhbKuEqWnhoeI/edit Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4023) Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each'
Title: Message Title David Lewis commented on PUP-4023 Re: Puppet 3.7.4-1 on CentOS7 w/ Ruby 2.0.0p353 -- undefined method `each' I am getting similar error. Did any resolution come of this? I would be willing to run commands on my system for testing purposes. My error message is this: Error: Could not retrieve local facts: undefined method 'each' for # Error: Failed to apply catalog: Could not retrieve local facts: undefined method 'each' for # I am running on RHEL7.1. I am running puppet 3.7.4-1 on my RHEL7.1 system and (I know, should update master, unable to break production system) puppet-3.4.2-1.el5 on master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Eric Thompson commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data i didn't bind 'a' at all. it comes from an environment function. unless "binding" in that case is implied by the environment conf's environment_data_provider function Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4122) Add validation of preview --migrate option
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4122 Add validation of preview --migrate option Change By: Henrik Lindberg Issue Type: Sub-task New Feature Parent: PUP-4121 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4236) Puppet module subcommand has no help available
Title: Message Title Matthaus Owens commented on PUP-4236 Re: Puppet module subcommand has no help available This does still seem inconsistent with other puppet bits. `puppet resource --help` for example works just fine, so it is surprising that other parts of puppet don't work the same way. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4236) Puppet module subcommand has no help available
Title: Message Title Matthaus Owens created an issue Puppet / PUP-4236 Puppet module subcommand has no help available Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/03/17 2:29 PM Priority: Normal Reporter: Matthaus Owens When getting error messages from the module tool (really puppet in general), it is often helpful to ask for help with respect to a given subcommand. Unfortunately, the module subcommand has no such ability. [root@x4l5veq31prxezy ~]# puppet module upgrade --help No help available for puppet module [root@x4l5veq31prxezy ~]# puppet module --help
Jira (PUP-2699) Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2699 Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory" Change By: Josh Cooper Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2699) Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory"
Title: Message Title Josh Cooper commented on PUP-2699 Re: Puppet specs on windows triggers "Excluding C from search path. Fact file paths must be an absolute directory" This was merged awhile ago, and verified as fixed in https://jenkins.puppetlabs.com/view/Puppet/view/Master/job/platform_puppet_specs_windows-master/label=unit-win2012,ruby=ruby-2.1.5.1-x86/932/console Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Henrik Lindberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data Remember that if you have a module, everything inside of that module must have the module's name as the first name segment of classes and defines inside of that module. Thus the names of the parameters in production_module are production_module::a, production_module::b, etc. You must also bind those names in global hiera, environment or module data. If you bound just the name a, that name can never be automatically looked up as a class parameter - it must have at least two segements; class-name, and parameter name. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3846) Puppet 4.0 MSI Changes - Windows Unified Installer
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3846 Puppet 4.0 MSI Changes - Windows Unified Installer Change By: Ethan Brown Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. I don't really think Henrik's suggestion is the right approach; I agree it's technically accurate, but it's too heavyweight. Users will just want to know how we intended this to be used, not all the ways you could potentially make it limp along. Which is product direction perspective, so we got that from Eric Sorenson in the SoS. Summary is: The default is just there for surprise reduction. If you're reading the docs at all, it's time for you to change the value. Our actual best-practices recommendation is to set unlimited, and ping puppetserver's environment-cache endpoint (or restart apache) when you deploy code. We don't recommend any values other than 0 or unlimited, due to the out-of-sync ruby interpreters issue, but if you really want to, you can do some science and decide whatever you want. We don't recommend setting environment_timeout per-environment; you should manage it globally unless you're really doing something weird. (Eric, is this an accurate summary?) Four remaining tasks on this ticket: Update conf/environment.conf, which wasn't updated at the time of the behavior change. Update defaults.rb description, which has outdated advice. Update docs ticket for updating other relevant pages. I'll do these as soon as I can and then we can get final review on this. Add Comment
Jira (PUP-4223) Smoke test packages
Title: Message Title Matthaus Owens commented on PUP-4223 Re: Smoke test packages I smoke tested the el7 0.9.0 build of puppet-agent against 2.0.0-rc3 of puppetserver on el7. Worked fine for me. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Steve Barlow assigned an issue to Nicholas Fagerlund Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Steve Barlow Assignee: Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1928) Using hostname as a unique key is not sufficient for /etc/hosts management
Title: Message Title Eli Young commented on PUP-1928 Re: Using hostname as a unique key is not sufficient for /etc/hosts management As I document in PUP-3901, keying on the IP is insufficient to model existing hosts file states, especially considering that hosts files on Windows are limited to 9 hostnames per line. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4189) Add all per-user directories to file_paths specification
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4189 Add all per-user directories to file_paths specification Change By: Steve Barlow Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4189) Add all per-user directories to file_paths specification
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4189 Add all per-user directories to file_paths specification Change By: Steve Barlow Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title
Eric Thompson commented on PUP-3948
Re: Let lookup be the impl for agnostic lookup of data
Henrik Lindberg in writing some acceptance tests for the broad functionality here i've hit some strange behavior. if i call lookup() it finds values just fine for environment and module, but if i include a class with implied lookup, the values are not found:
class production_module($a, $b, $c, $port) {
# lookup data from the environment\\'s function databinding
notify { "#{env_data_string} $a": }
# lookup data from the module\\'s databinding
notify { "#{module_data_string} $b": }
# ensure env can override module
notify { "#{env_override_data_string} $c": }
Jira (PUP-4235) Create rake task for puppet-passenger AIO acceptance tests
Title: Message Title John Duarte created an issue Puppet / PUP-4235 Create rake task for puppet-passenger AIO acceptance tests Issue Type: Task Assignee: Unassigned Created: 2015/03/17 12:28 PM Labels: AIO Priority: Normal Reporter: John Duarte We will be running puppet acceptance tests against SUTs with puppet-agent and puppet-passenger packages. These tests will require a rake task for defining the tests. The tests for this task should be a very small subset of the acceptance test suite. The functional areas that need to be covered are: sign a cert compile a catalog send a report
Jira (PUP-4234) Create pre-suites for puppet-passenger AIO acceptance tests
Title: Message Title John Duarte created an issue Puppet / PUP-4234 Create pre-suites for puppet-passenger AIO acceptance tests Issue Type: Task Assignee: Unassigned Created: 2015/03/17 12:25 PM Labels: AIO Priority: Normal Reporter: John Duarte We will be running puppet acceptance tests against SUTs with puppet-agent and puppet-passenger packages. These tests will require updates to the pre-suites for the acceptance tests. Specifically, server selection will need to be added where appropriate. This should be keyed off of the appropriate beaker option defined in the beaker config file. Add Comment
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3948 Let lookup be the impl for agnostic lookup of data Change By: Eric Thompson Assignee: Kurt Wall Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4233) Create node configs for puppet-passenger AIO acceptance tests
Title: Message Title John Duarte created an issue Puppet / PUP-4233 Create node configs for puppet-passenger AIO acceptance tests Issue Type: Task Assignee: Unassigned Created: 2015/03/17 12:22 PM Labels: AIO Priority: Normal Reporter: John Duarte We will be running puppet acceptance tests against SUTs with puppet-agent and puppet-passenger packages. These tests will need to use beaker config files that define the correct systems, architectures, and server service. The following platforms should be incorporated with 64bit arch only (no 32bit). Debian 7 - Wheezy Ubuntu 12.04 - Precise Ubuntu 14.04 - Trusty RHEL 6 RHEL 7
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3948 Let lookup be the impl for agnostic lookup of data Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4066) With strict variables turned on, it is difficult to use built in variables
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4066 With strict variables turned on, it is difficult to use built in variables Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4066) With strict variables turned on, it is difficult to use built in variables
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4066 With strict variables turned on, it is difficult to use built in variables Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4080) support S3 URL as the file type 'source'
Title: Message Title Ethan Brown commented on PUP-4080 Re: support S3 URL as the file type 'source' Yes, we're not ready to merge this, and there is ongoing discussion internally on how to address this in a more generic way that is easily pluggable by 3rd parties. We definitely want this functionality, but it's a matter of determining the appropriate integration point. This might be something that we want to tackle as an architectural change inside Puppet core to accommodate protocol handlers in modules. As soon as there's anything to report on that front, I will let you know - we're in a bit of a holding pattern at the moment. Thanks again for the contribution and all the time you've put into this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4232) add acceptance tests for lookup()
Title: Message Title Eric Thompson created an issue Puppet / PUP-4232 add acceptance tests for lookup() Issue Type: Sub-task Assignee: Eric Sorenson Components: QA Created: 2015/03/17 9:57 AM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (PUP-4232) add acceptance tests for lookup()
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4232 add acceptance tests for lookup() Change By: Eric Thompson Assignee: Eric Sorenson Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4149) Create private repo for new preview module
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-4149 Create private repo for new preview module Change By: Hailee Kenney Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4149) Create private repo for new preview module
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-4149 Create private repo for new preview module Change By: Hailee Kenney Sprint: Language 2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging We are running into this exact problem. It seems like the status is "Needs Information" but I'm not sure what that information is. If someone could point me in the right direction I'd be happy to try and find the required information to get the ball rolling on fixing this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4080) support S3 URL as the file type 'source'
Title: Message Title Melissa Stone commented on PUP-4080 Re: support S3 URL as the file type 'source' Peter Foley the reason I moved this ticket to ready for merge is that it is a more appropriate state than open. Ready for merge does not mean we are ready to push the button right at this moment, but that we are deciding what is the best way forward. In this case, still discussing what needs to be added to your PR and what should be done with it. However, I believe Felix is correct in that 'Needs Information' is a better state for this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4080) support S3 URL as the file type 'source'
Title: Message Title Felix Frank commented on PUP-4080 Re: support S3 URL as the file type 'source' Handing this to Eric Sorenson since this needs a decision. Could perhaps be delegated to Ethan Brown or someone else. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4080) support S3 URL as the file type 'source'
Title: Message Title Felix Frank assigned an issue to Eric Sorenson Puppet / PUP-4080 support S3 URL as the file type 'source' Change By: Felix Frank Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4080) support S3 URL as the file type 'source'
Title: Message Title Peter Foley commented on PUP-4080 Re: support S3 URL as the file type 'source' Melissa Stone I just wanted to check what the next step in the workflow is from a "ready for merge" status? From the triage videos I had the impression the preference was to move this into a module (puppetlabs-aws) and more dialog needed to occur on the puppet-dev mailing list to flesh out how it could be flexible enough to work for other sources. If the consensus now is to move this into the puppet core (at least temporarily until after deciding how to give puppet modules superpowers to inject new sources into the file type) my PR code I submitted was sufficient to demonstrate how it would work. Just off the top of my head I still need to add: spec and acceptance tests update the user facing documentation to highlight the need for users of this source will need to self install the aws-sdk-core (ruby gem) fix up the gemfile to move the aws-sdk-core into a development group. (I am sure there were some other suggestions from the triage videos that I have missed (I will have to re-watch)). If it is still ultimately the intention of moving this functionality into a module is there any benefit (or precedence) adding a comment that this capability will move into the puppetlabs-aws in the future? Assuming this is something that Gareth Rushgrove or Ethan Brown would accept into the module? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
