Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title
Thomas Hallgren commented on PUP-3948
Re: Let lookup be the impl for agnostic lookup of data
The error is probably correct since it doesn't stem from the lookup given on the command line but rather from the environments/production/modules/abc/manifests/init.pp which I guess is copied from the spec/fixtures? It's tailored for the unit tests and assumes that some variables are set prior to including it:
class abc {
if $block != 'no_block_present' {
$result = lookup(*$args) |$names| { if $block == true { $names } else { $block } }
}
else {
$result = lookup(*$args)
}
}
and since $args isn't set in your call, it's given as undef (which is a bit peculiar. Henrik Lindberg, should a splat of an undef yield one undef argument?). The block is also given since $block is undefined. If you want to use this class as is to lookup 'b', then call it like this instead:
Jira (PUP-4074) Remove master settings from puppet.conf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4074 Remove master settings from puppet.conf Change By: Josh Cooper 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-4074) Remove master settings from puppet.conf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4074 Remove master settings from puppet.conf Change By: Josh Cooper 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-4080) support S3 URL as the file type 'source'
Title: Message Title
Peter Foley created an issue
Puppet / PUP-4080
support S3 URL as the file type 'source'
Issue Type:
New Feature
Assignee:
Kylo Ginsberg
Components:
Community, Types and Providers
Created:
2015/03/04 3:05 AM
Priority:
Normal
Reporter:
Peter Foley
It would be nice to use AWS S3 resources as a source for the Puppet file type.
Something like:
file {
"/tmp/example.txt":
source => 's3://foo-bucket/bar.file',
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 Thomas Hallgren yes an unfold of something that is not an array is a no-op (so *undef produces undef). 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 Eric Thompson The data provided for a module can only be looked up inside of that module. When you make the call "from the command line", that call comes from the environment so it only looks in global hiera data, then in data for the environment, but since it is not in a module, the lookup does not go further. If you like, you can think of the data in a module as private. This prevents one module from providing data for another module (in which case the configuration would need to be much more complicated). The code in the fixtures use the data in modules to lookup class parameters automatically, and to call lookup directly (as in the sample you used). The sample uses two global variables to pass arguments into the abc class (a parameterized class could have been used instead, but I did not want to muddle what it is testing with that aspect as well). As thomas showed, you can set the global variables before calling the class abc (to do the lookup). You should then be able to lookup all the data you returned from the abc::data() function. This opens a question - should a lookup from the environment succeed in looking up data from a module when the name is fully qualified (starts with the modulename)? I think it should, but I am not sure if it is implemented that way. (Ping Thomas Hallgren) 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-4078) puppet resource tool output contains incorrect quoting
Title: Message Title Henrik Lindberg commented on PUP-4078 Re: puppet resource tool output contains incorrect quoting I think it should: Output numbers as numbers Booleans as booleans Resource references as resource type instances (it probably does already i.e. File['foo'], and not 'File[foo]') Keywords in general must be quoted, the fact that true and false are keywords does not mean that values such as 'if' should be output as a keyword. The RAL is unchanged between 3.x and 4.x. It will contain values as produced by the 3.x types. I suspect the cleanup will have to be done as part of puppet resource printout of the values. (The catalog is still predominantly based on everything being strings). 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 Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4066 With strict variables turned on, it is difficult to use built in variables Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 Thomas Hallgren commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data Henrik Lindberg, That unfold would be a no-op doesn't make sense to me. What it actually does is saying that *undef == *[undef] which translates to a call with a parameter count of one. IMO, that's not a no-op. Also, ruby does not do that: def foo(*splat) puts splat.size end x = nil foo(*x) will print 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Thomas Hallgren commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data Regarding an environment using fully qualified names to lookup in a module. I tested and it doesn't seem to work. 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-4081) lookup should lookup in module when looking up qualified names
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4081 lookup should lookup in module when looking up qualified names Issue Type: Bug Assignee: Unassigned Created: 2015/03/04 6:15 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Henrik Lindberg The current behavior of the lookup function is to only lookup data provided by a module data provider if the call to lookup comes from within the module. This is done to protect that one module overrides values for other modules (which is not allowed). The rules should be changed so that a lookup for a fully qualified key should be directed to the module matched by the first name segment (if that module supports a data provider). Without this ability, it is not possible to figure out what the value of a parameter will be (unless it is overridden in the environment or globally) unless that call to lookup comes from within the module. All other keys bound by the module data provider continues to be private and should only be visible to lookups from within the module.
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 Thomas Hallgren I logged PUP-4081 for the missing "lookup of qualified name in module data" issue. 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-4082) unfold of undef should mean unfold nothing
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4082 unfold of undef should mean unfold nothing Issue Type: Improvement Assignee: Unassigned Components: DSL Created: 2015/03/04 6:18 AM Fix Versions: PUP 3.7.5 Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4082) unfold of undef should mean unfold nothing
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4082
unfold of undef should mean unfold nothing
Change By:
Henrik Lindberg
Currently, an unfold of undef e.g. {{foo(*undef)}} results in the function foo being called with {{undef}} as an argument. This because the current rules is "unfold of something that is not an array turns it into an array of one element before unfolding". It is more natural to equate an unfold of {{undef}} with an unfold of an empty array.Special care has to be taken when unfold is used with case and selector options since it will result in a "missing option" - this should probably be treated as an error rather than silently skipping (the same should happen when unfolding an empty array as options).
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-4082) unfold of undef should mean unfold nothing
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4082
unfold of undef should mean unfold nothing
Change By:
Henrik Lindberg
Currently, an unfold of undef e.g. {{foo(*undef)}} results in the function foo being called with {{undef}} as an argument. This because the current rules is "unfold of something that is not an array turns it into an array of one element before unfolding". It is more natural to equate an unfold of {{undef}} with an unfold of an empty array.Special care has to be taken when unfold is used with case and selector options since it will result in a "missing option" - this should probably be treated as an error rather than silently skipping (the same should happen when unfolding an empty array as options). This change requires a spec update.
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-4082) unfold of undef should mean unfold nothing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4082 unfold of undef should mean unfold nothing Change By: Henrik Lindberg Sprint: Language 2015-03-04 Scrum Team: Language Story Points: 1 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 Thomas Hallgren commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data I checked Ruby a bit more: x = *nil # x == [] x = *'hello' # x == ['hello'] 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 Thomas Hallgren I added PUP-4082 for the unfold of undef - continue discussion there. 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' I'm interested in concrete use cases for this. The idea of moving files to blob storage was discussed as a possible workaround for some issues that inspired PUP-2526 (the debate around which has never been resolved). I'm not really keen on bundling the AWS SDK with Puppet. But if we find the feature to be sufficiently desirable, then the ends probably justify the means. 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 Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4066 With strict variables turned on, it is difficult to use built in variables Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-4072) defined() function returns wrong value for global variable check
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4072 defined() function returns wrong value for global variable check Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Felix Frank commented on PUP-1072 Re: support HTTP(S) URL as the file 'source' Meanwhile, mtime is fully functional. Updates server files should get synchronized (smoke testing was promising, although I have yet to go to the length of refreshing an actual webserver). Moreover, if you own the webserver that hosts the file in question, you can enable content digests (apache) so that the md5 sum will be part of the HTTP headers. Puppet will verify this sum as with all files. Since the limitations I described earlier are partly resolved now, adding support for checksums as parameters doesn't seem profitable to 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-4066) With strict variables turned on, it is difficult to use built in variables
Title: Message Title Thomas Hallgren commented on PUP-4066 Re: With strict variables turned on, it is difficult to use built in variables Merged to stable at bc31f7c 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-4081) lookup should lookup in module when looking up qualified names
Title: Message Title Thomas Hallgren commented on PUP-4081 Re: lookup should lookup in module when looking up qualified names Question. There's a clearly defined precedence when looking up data. global is higher than environment which is higher than module. I guess one of the reasons for that is to enable overrides of values with lower priority. If we allow access using fully qualified keys, then what should happen? Is the environment binding for key 'b' overriding the binding for key 'b' in module 'abc' even if I explicitly lookup 'abc::b' ? 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-4081) lookup should lookup in module when looking up qualified names
Title: Message Title Henrik Lindberg commented on PUP-4081 Re: lookup should lookup in module when looking up qualified names If the lookup is for abc::b, then it should look for that key in the order global, env, module, the first found wins. If looking up b, then this is not a qualified name, so if the lookup is not from within the module abc, the lookup would search global, env (and not the module) for the key b. If it comes from within the module abc, it would search global, env, and then the module abc for the key b. Put differently: global and environment always override module, module data keys that are not in the module's namespace are not visible for lookup from a scope outside of the module. It is also a really bad idea to bind keys in a module that are not prefixed with the module's namespace. We need to deal with that as well. Say module abc binds xyz::b. With the rules described above, a lookup of xyz::b from within the module abc would not see this value. I think we should have the rule "module data can only bind keys in its own namespace - all other keys are invisible". Somewhat difficult to validate and raise errors though. Thoughts? 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 Thomas Hallgren commented on PUP-4066 Re: With strict variables turned on, it is difficult to use built in variables Merged to master at d1db507 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 Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4066 With strict variables turned on, it is difficult to use built in variables Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-4081) lookup should lookup in module when looking up qualified names
Title: Message Title Thomas Hallgren commented on PUP-4081 Re: lookup should lookup in module when looking up qualified names The data(key, scope) method of the Puppet::DataProviders::DataFunctionSupport could take a block. If given, it would be called using result of calling the bound function and then return the validated (and possibly modified) result. The Puppet::DataProviders::FunctionModuleDataProvider would use this and pass a block to validate that all keys are correctly prefixed. Another idea would be if it actually added the prefix to each key, thus removing that responsibility from the author of the data 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-3886) Add yumrepo resource spec integration tests
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3886 Add yumrepo resource spec integration tests Change By: Steve Barlow Sprint: Client 2015-02-18, Client 2015-03-04 , Client 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-3974) ensure puppet apply source_attribute acceptance tests touch all checksums
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3974 ensure puppet apply source_attribute acceptance tests touch all checksums Change By: Steve Barlow Sprint: Client 2015-03-04 , Client 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-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1635 "current thread not owner" after Puppet Agent receives USR1 signal Change By: Steve Barlow Sprint: Client 2015-03-04 , Client 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 (HI-340) Fix Hiera acceptance under new paths
Title: Message Title Steve Barlow updated an issue Hiera / HI-340 Fix Hiera acceptance under new paths Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-1085) Pacman provider constantly reinstalls package groups on arch linux
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1085 Pacman provider constantly reinstalls package groups on arch linux Change By: Steve Barlow Scope Change Reason: Community Scope Change Category: Adopted 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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4012 parsed provider destroys file if a line starts with uppercase Q Change By: Steve Barlow Scope Change Reason: Community Scope Change Category: Adopted 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-4057) Acceptance tests should not rely on the puppetpath beaker option
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4057 Acceptance tests should not rely on the puppetpath beaker option Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-3960) Presence of createrepo not checked by acceptance/rpm_util.rb
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3960 Presence of createrepo not checked by acceptance/rpm_util.rb Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-4072) defined() function returns wrong value for global variable check
Title: Message Title Henrik Lindberg commented on PUP-4072 Re: defined() function returns wrong value for global variable check This is already fixed on master - backporting to 3.x 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-4049) System module path should be a thing on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4049 System module path should be a thing on Windows Change By: Josh Cooper Labels: AIO_TechDebt 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-4057) Acceptance tests should not rely on the puppetpath beaker option
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4057 Acceptance tests should not rely on the puppetpath beaker option 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-3982) Ensure puppet service supports conditional restart
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3982 Ensure puppet service supports conditional restart 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-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Change By: Steve Barlow Sprint: Client 2015-02-04, Client 2015-02-18, Client 2015-03-04 , Client 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-4026) Create specification for new AIO settings
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4026 Create specification for new AIO settings Change By: Steve Barlow Sprint: Client 2015-03-04 , Client 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-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1635 "current thread not owner" after Puppet Agent receives USR1 signal Change By: Steve Barlow Scope Change Reason: Community Scope Change Category: Adopted 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-3960) Presence of createrepo not checked by acceptance/rpm_util.rb
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3960 Presence of createrepo not checked by acceptance/rpm_util.rb 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-4005) AIO agent CSR extension not compatible with current puppetserver packages
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4005 AIO agent CSR extension not compatible with current puppetserver packages Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4073 rundir and logdir are no longer relative to vardir Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-826) Change AIO external facts directory
Title: Message Title Steve Barlow updated an issue Facter / FACT-826 Change AIO external facts directory Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-4037) Windows AIO path changes
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4037 Windows AIO path changes Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found 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-4011) Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4011 Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4 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-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Steve Barlow Scope Change Reason: Community Scope Change Category: Adopted 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-4079) investigate File Type high-priority tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4079 investigate File Type high-priority tests Change By: Eric Thompson check audit test coverage in spec tests first to ensure /acceptance for the File Type.add subtasks if any changes can be done in this is tested sprint, otherwise add tickets to backlog .https://testrail.ops.puppetlabs.net/index.php?/suites/view/349&group_by=cases:section_id&group_order=asc&group_id=13193 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-3969) Puppet acceptance tests need auditing to derive 'host' and 'group' using the Beaker 'puppet' helper
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3969 Puppet acceptance tests need auditing to derive 'host' and 'group' using the Beaker 'puppet' helper 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-4079) investigate File Type high-priority tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4079 investigate File Type high-priority tests Change By: Eric Thompson Summary: investigate file resource File Type high - priority tests 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-3949) Update docs for application/octet-stream and binary Accept value
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3949 Update docs for application/octet-stream and binary Accept value 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-4079) investigate file resource high priority tests
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4079 investigate file resource high priority tests Change By: Eric Thompson Summary: investigate file type resource high priority tests 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-4074) Remove master settings from puppet.conf
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4074 Remove master settings from puppet.conf Change By: Steve Barlow Sprint: Client 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-4056) Audit acceptance tests for assumed ruby location
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4056 Audit acceptance tests for assumed ruby location Change By: Steve Barlow Sprint: Client 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-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4044 AIO acceptance tests copies multiple versions of repo configs to the SUT Change By: Eric Thompson Component/s: 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-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Michael Smith updated an issue Puppet / PUP-1635 "current thread not owner" after Puppet Agent receives USR1 signal Change By: Michael Smith Component/s: Community 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-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4044 AIO acceptance tests copies multiple versions of repo configs to the SUT Change By: Steve Barlow Labels: AIO AIO_TechDebt 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-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Change By: Steve Barlow Sprint: Client 2015-02-04, Client 2015-02-18, Client 2015-03-04 , Client 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-3967) Run puppet acceptance with cfacter
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3967 Run puppet acceptance with cfacter Change By: Steve Barlow 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-4056) Audit acceptance tests for assumed ruby location
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4056 Audit acceptance tests for assumed ruby location 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-4056) Audit acceptance tests for assumed ruby location
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4056 Audit acceptance tests for assumed ruby location Change By: Steve Barlow 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 (PUP-4056) Audit acceptance tests for assumed ruby location
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4056 Audit acceptance tests for assumed ruby location Change By: Eric Thompson Component/s: 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-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Kylo Ginsberg commented on PUP-4046 Re: Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction Henrik Lindberg thoughts on 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-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4046 Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction Change By: Kylo Ginsberg 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-4056) Audit acceptance tests for assumed ruby location
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4056 Audit acceptance tests for assumed ruby location 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-4026) Create specification for new AIO settings
Title: Message Title Ethan Brown assigned an issue to Josh Cooper Puppet / PUP-4026 Create specification for new AIO settings Change By: Ethan Brown Assignee: Ethan Brown Josh Cooper 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-4026) Create specification for new AIO settings
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-4026 Create specification for new AIO settings Change By: Ethan Brown Assignee: Ethan Brown 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4054 create_resources() error messages are less useful in 3.x then they were in 2.x Change By: Eric Thompson Assignee: QA 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Eric Thompson commented on PUP-4054 Re: create_resources() error messages are less useful in 3.x then they were in 2.x on master as expected i get: [root@qiunjqb56sb9eah ~]# puppet apply create_res_errors.pp Error: Evaluation Error: The value 'foo' cannot be converted to Numeric. at /root/create_res_errors.pp:2:8 on node qiunjqb56sb9eah.delivery.puppetlabs.net Error: Evaluation Error: The value 'foo' cannot be converted to Numeric. at /root/create_res_errors.pp:2:8 on node qiunjqb56sb9eah.delivery.puppetlabs.net but on stable i'm still getting: [root@qiunjqb56sb9eah ~]# puppet apply create_res_errors.pp Error: left operand of + is not a number at /root/create_res_errors.pp:3 on node qiunjqb56sb9eah.delivery.puppetlabs.net Wrapped exception: left operand of + is not a number Error: left operand of + is not a number at /root/create_res_errors.pp:3 on node qiunjqb56sb9eah.delivery.puppetlabs.net
Jira (PUP-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4054 create_resources() error messages are less useful in 3.x then they were in 2.x Change By: Eric Thompson Assignee: 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-2746) new parameter "allow_virtual"
Title: Message Title Rich tea commented on PUP-2746 Re: new parameter "allow_virtual" This really is no good, we are running PE 3.4.3 and it would seem that there is no way to stop this message appearing on every puppet run. I tried adding "disable_warnings = deprecations" to puppet.conf but it seems to be not supported. and setting "allow_virtual" will not work ether. Is there anything else we can do to stop this message? 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-1253) systemd service provider should support masking
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-1253 systemd service provider should support masking Change By: Kylo Ginsberg Assignee: Kylo Ginsberg 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-4067) Switch rpm/deb package manifest dir to default directory environment.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4067 Switch rpm/deb package manifest dir to default directory environment. Change By: Josh Cooper 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-4067) Create production environment directories in packaging
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4067 Create production environment directories in packaging Change By: Josh Cooper Summary: Switch rpm/deb package manifest dir to default directory Create production environment . directories in packaging 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-4081) lookup should lookup in module when looking up qualified names
Title: Message Title Henrik Lindberg commented on PUP-4081 Re: lookup should lookup in module when looking up qualified names Removing the prefix in data keys is not so great - it makes it more difficult to copy or reuse the data (copy to env, or if you call the function to get the hash/combine it with other data). Adding a block to that method is fine - it is an internal implementation detail anyway. 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-4083) Add sample environment.conf to puppet
Title: Message Title Matthaus Owens created an issue Puppet / PUP-4083 Add sample environment.conf to puppet Issue Type: Task Assignee: Nicholas Fagerlund Created: 2015/03/04 10:56 AM Priority: Normal Reporter: Matthaus Owens In making the default production environment, having a sample environment.conf will be very helpful. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4067) Create production environment directories in packaging
Title: Message Title Matthaus Owens commented on PUP-4067 Re: Create production environment directories in packaging We also want to add a sample environment.conf to the example production environment. Nicholas Fagerlund will be adding such a file to puppet in PUP-4083. /cc Melissa Stone 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-4074) Remove master settings from puppet.conf
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4074 Remove master settings from puppet.conf Change By: William Hopper Assignee: William Hopper 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-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Henrik Lindberg commented on PUP-4046 Re: Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction This was introduced by the refactoring of the hiera functions to the 4.x function API. For some reason, when the hiera_include, calls the 3.x include function, it ends up being a function that was not loaded by any 4x function loader. It needs this to check if the include function is available as a 4.x. function. The failure is on line 89 in Puppet::Pops::Functions::Function, but why it does not have a loader set is mysterious. 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-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Henrik Lindberg commented on PUP-4046 Re: Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction Has it been confirmed if this occurs only in the AIO packaging, or if it also occurs when running from source? 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-4076) Remove the 'allow_virtual' warning in the 3.x series
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4076 Remove the 'allow_virtual' warning in the 3.x series Change By: William Hopper Assignee: William Hopper 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-4046) Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction
Title: Message Title Henrik Lindberg commented on PUP-4046 Re: Puppet-agent 0.3.2.89.g8eeaf77-1.el7 - uninitialized constant Hiera::PuppetFunction No need to open a new ticket - the PR was not merged. Both problems can be fixed 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-4082) unfold of undef should mean unfold nothing
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4082 unfold of undef should mean unfold nothing Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-4074) Remove master settings from puppet.conf
Title: Message Title William Hopper assigned an issue to Matthaus Owens Puppet / PUP-4074 Remove master settings from puppet.conf Change By: William Hopper Assignee: William Hopper Matthaus Owens 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-4076) Remove the 'allow_virtual' warning in the 3.x series
Title: Message Title William Hopper commented on PUP-4076 Re: Remove the 'allow_virtual' warning in the 3.x series For reference, the commit in master that made this change is here: https://github.com/puppetlabs/puppet/commit/3f6d7cada1b4816b40279400aae9cce5ba29761e This PR removes the deprecation warning in stable (which I think is what we want to do here?): https://github.com/puppetlabs/puppet/pull/3681 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-4082) unfold of undef should mean unfold nothing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4082 unfold of undef should mean unfold nothing Change By: Henrik Lindberg Component/s: DOCS 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-4082) unfold of undef should mean unfold nothing
Title: Message Title Henrik Lindberg commented on PUP-4082 Re: unfold of undef should mean unfold nothing Nicholas Fagerlund For docs, specified here: https://github.com/puppetlabs/puppet-specifications/blob/ff5031ea79fad679aa568d40146d7b8bd8d0b476/language/expressions.md#unary--operator-splat The corresponding language reference documentation should be updated. 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 (HI-336) add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-336 add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Change By: Eric Thompson add some "doesn't grab stuff in the wrong hierarchy" type spec edge cases... QA portion of this is done. hiera spec tests need a hierarchy sent to datasourcefiles so that we can ensure that lookup does not pull from outside the current hierarchy even if the backend yields files that are outside the given hierarchy.repeat: yaml and json backendsinvestigate agnostic lookup tests in this regard as well. 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 (HI-336) investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-336 investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Change By: Eric Thompson Summary: add spec investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy 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 (HI-336) investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson assigned an issue to Unassigned Hiera / HI-336 investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Change By: Eric Thompson Assignee: 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-2746) new parameter "allow_virtual"
Title: Message Title Kylo Ginsberg commented on PUP-2746 Re: new parameter "allow_virtual" Rich tea the two methods given by snippets above should work in most cases. However, I've also seen where users of a module that has custom facts which call puppet to report package info as facts (that's quite a mouthful, sorry) will see this message too. In that case, the easiest thing is probably to patch the module similar to the snippet above (i.e. to set `allow_virtual=false` as a Package default). Btw, there is no release called PE 3.4.3. What is the output of 'puppet --version'? Thanks! 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 (HI-347) spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy
Title: Message Title Eric Thompson created an issue Hiera / HI-347 spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy Issue Type: Task Assignee: Unassigned Created: 2015/03/04 12:22 PM 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. To unsubscribe from this 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. Fo
Jira (HI-336) investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-336 investigate edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Change By: Eric Thompson add some "doesn't grab stuff in the wrong hierarchy" type spec edge cases...QA portion of this is done. hiera spec tests need a hierarchy sent to datasourcefiles so that we can ensure that lookup does not pull from outside the current hierarchy even if the backend yields files that are outside the given hierarchy.repeat: yaml and json backendsinvestigate agnostic lookup tests in this regard as well. will open another ticket for spec test additions 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Henrik Lindberg commented on PUP-4054 Re: create_resources() error messages are less useful in 3.x then they were in 2.x Yes, it is ugly as it shows the wrapped exception. The 3.x. parser is also notoriously bad at associating expressions with the correct line (it picks the linenumber that is current in the lexer and it may have moved to the next line). The wrapped exception is not always there - it depends on which error it is. I consider that a lesser evil than reporting the wrapped exception only (without line number). This also only affects errors occurring when calling create_resources. 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-4054) create_resources() error messages are less useful in 3.x then they were in 2.x
Title: Message Title Henrik Lindberg commented on PUP-4054 Re: create_resources() error messages are less useful in 3.x then they were in 2.x It is worth also verifying that the file is correct - i.e. by autoloading the resource type (the define in the sample). 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 (HI-347) spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy
Title: Message Title Eric Thompson commented on HI-347 Re: spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy hiera spec tests need additional tests where hierarchy sent to datasourcefiles so that we can ensure that lookup does not pull from outside the current hierarchy even if the backend yields files that are outside the given hierarchy. repeat for yaml and json backends investigate agnostic lookup tests in this regard as well. QA priority: high (impact: high: reported as security concern from PE, probability: high: core functionality) test-level: spec (with perhaps a small acceptance component to be determined) 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 (HI-347) spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-347 spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy Change By: Eric Thompson Component/s: 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.
