Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Gilles Gagniard commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) The pip-python binary disappeared with the push of pip 1.5.6 to EPEL 7 which happened on mid-december. RHEL < 7 still have pip-python. I submitted a patch taking that into account : https://github.com/puppetlabs/puppet/pull/3470 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-233) Support array merge for automatic parameter lookup
Title: Message Title Sebastian Reitenbach commented on HI-233 Re: Support array merge for automatic parameter lookup Hi, I was just head scratching and getting grey hair, until I re-read the link mentioned in the initial report here, in order to figure out that there is only priority lookup in Puppet automatic Parameter lookup functionality. However, maybe an easy, backward compatible solution could be to add a puppet.conf entry to the [master] section, something along the lines: parameter_lookup = priority that would be the default, so being/staying backward compatible. People that want to match the automatic parameter lookup to match what hiera_array() or hiera_hash() is doing, they can change the puppet.conf parameter to another value, i.e. "merge" or whatever it will be. Would that be a feasible way? thanks, Sebastian 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-233) Support array merge for automatic parameter lookup
Title: Message Title R.I.Pienaar commented on HI-233 Re: Support array merge for automatic parameter lookup The only way to do this properly is to create a way to associate schema with the data. Be it type decorations in the class declaration or something like like annotations in the code. Not all hashes or arrays are to be merged, going with the route where all are treated the same will just lead to the exact same situation where some problems cant be solved with automatic param lookup. 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-233) Support array merge for automatic parameter lookup
Title: Message Title Henrik Lindberg commented on HI-233 Re: Support array merge for automatic parameter lookup IMO, the way to do this is to make it possible to declare keys in hiera data to have a different resolution mechanism than "literal value". This is how the binder works btw. It is however difficult to implement with full backwards compatibility with something like the hiera yaml backend since it is hard to distinguish between literal values, and other types of objects. 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-233) Support array merge for automatic parameter lookup
Title: Message Title
R.I.Pienaar commented on HI-233
Re: Support array merge for automatic parameter lookup
That's a way for sure, but I think when looking at a class without data its important to know what the data is. And that one should be able to take a piece of code and go from there and construct data.
It also means at every level in every hierarchy in every backend you need to annotate the data which would be prone to error.
Now of course you could have some kind of schema that goes with the data so it's not stored in every key, this might work too, I think that's something I whiteboarded with Eric Sorenson
Back to the code needing to be authoritive:
code class x($y) { } code
makes it very hard without also studying the entire body and any other class that might access $::x::y to know what data to put in hiera as there are no hints at all
code
@hiera_hash($y) class x($y) { } code
This makes it easier for someone to know by just looking at a piece of code from the forge/docs/irc that it's going to be hash merged and that they can override accordingly. Though I am not recommending this specifically as a implementation it's horrible syntax, doesnt say anything about type of data or anyway for UIs to construct inputs etc so woefully inadequate - but shows what I mean i guess
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 grou
Jira (PUP-3820) lambda iteration and variable scoping
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-3820
lambda iteration and variable scoping
Change By:
Henrik Lindberg
can not use variables in iteration i can not get variable assigned outside of scope of iteration. {code} - hiera --- rootuser: trueloe:status : 'present'name : 'KetanPatel'suid : 'whatislove'fkey : 'true'-- Manifest --$manageuser = hiera('rootuser') $manageuser.each |$username| { $k2username = $username[0] $username[1].each |$provino, $svalue| {if $provino == 'status' { $userstatus = $svalue exec { "$provino" : command => "/usr/bin/echo $provino $svalue $userstatus >> /tmp/testfile", } }elsif $provino == 'name' { $fullname = $svalue exec { "$provino" : command => "/usr/bin/echo $provino $svalue $fullname >> /tmp/testfile", } }elsif $provino == 'suid' { $usersuid = $svalue exec { "$provino" : command => "/usr/bin/echo $provino $svalue $usersuid >> /tmp/testfile", } }elsif $provino == 'fprovino' { $filekey = $svalue exec { "$provino" : command => "/usr/bin/echo $provino $svalue $filekey>> /tmp/testfile", } } } exec { "$k2username" :command => "/usr/bin/echo $k2username $userstatus $fullname $usersuid $filekey >> /tmp/testfile", }--- Output -Info: Applying configuration version '1420756914'Debug: Exec[name](provider=posix): Executing '/usr/bin/echo name KetanPatel KetanPatel >> /tmp/testfile'Debug: Executing '/usr/bin/echo name KetanPatel KetanPatel >> /tmp/testfile'Notice: /Stage[main]/K2patelrad::Users/Exec[name]/returns: executed successfullyDebug: /Stage[main]/K2patelrad::Users/Exec[name]: The container Class[K2patelrad::Users] will propagate my refresh eventDebug: Exec[trueloe](provider=posix): Executing '/usr/bin/echo trueloe >> /tmp/testfile'Debug: Executing '/usr/bin/echo trueloe >> /tmp/testfile'Notice: /Stage[main]/K2patelrad::Users/Exec[trueloe]/returns: executed successfullyDebug: /Stage[main]/K2patelrad::Users/Exec[trueloe]: The container Class[K2patelrad::Users] will propagate my refresh eventDebug: Exec[status](provider=posix): Executing '/usr/bin/echo status present present >> /tmp/testfile'Debug: Executing '/usr/bin/echo status present present >> /tmp/testfile'Notice: /Stage[main]/K2patelrad::Users/Exec[status]/returns: executed successfullyDebug: /Stage[main]/K2patelrad::Users/Exec[status]: The container Class[K2patelrad::Users] will propagate my refresh eventDebug: Exec[suid](provider=posix): Executing '/usr/bin/echo suid whatislove whatislove >> /tmp/testfile'Debug: Executing '/usr/bin/echo suid whatislove whatislove >> /tmp/testfile'Notice: /Stage[main]/K2patelrad::Users/Exec[suid]/returns: executed successfullyDebug: /Stage[main]/K2patelrad::Users/Exec[suid]: The container Class[K2patelrad::Users] will propagate my refresh eventDebug: Class[K2patelrad::Users]:
Jira (PUP-3820) lambda iteration and variable scoping
Title: Message Title
Henrik Lindberg commented on PUP-3820
Re: lambda iteration and variable scoping
Took me a while to figure out what you expected. The problem seems to be that your last exec is referencing variables that are assigned in the lambda bodies in the iterations above it. This does not work by design, the variables in a block / lambda goes out of scope for each iteration, you cannot reference those after the iteration is completed.
you can do something like this:
$userdata = $username[1]
# ...
exec { "$k2username" :
command => "/usr/bin/echo $k2username ${userdata[status]} ${userdata[name]} ${userdata[suid]} ${userdata[fkey]} >> /tmp/testfile",
}
I suspect that this is just a sample, and that you are doing something more complex in your real logic, otherwise the above example could be simplified since you both know which keys you are interested in, and in which order you want to process them.
# simulating lookup from hiera
$manageuser = { truelove => { status => present, name => 'KetanPatel', suid => 'whatislove', fkey => 'true'}}
Jira (HI-233) Support array merge for automatic parameter lookup
Title: Message Title
Henrik Lindberg commented on HI-233
Re: Support array merge for automatic parameter lookup
Still, you can from Puppet 4.0, annotate the type of a class parameter - e.g.
class x(Hash[String, String] $y) {
}
Which clearly indicates that a Hash (with String keys and String values) is expected. It does not however say anything about how merging of the data to be injected should be done and that is IMO a property of the data (or the injection mechanism, via schema, encoding in the data, a smarter hiera backend, or whatever), not of the class parameter.
The choice of "it is this hash x::y, or that hash x::y, or a merge of all of the hashes keyed x::y in my hierarchy" should be a decision made by the person authoring the data.
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
Jira (HI-233) Support array merge for automatic parameter lookup
Title: Message Title Angel L. Mateo commented on HI-233 Re: Support array merge for automatic parameter lookup I'm agree in that the merge decision should be made by the person authoring data, but what makes me annoyed is the different behavior of automatic parameter lookup and hiera functions. I think that puppet should rely this in hiera backend and it should have the same behavior that hiera functions. 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-777) Facter should not downcase fact names
Title: Message Title Henrik Lindberg commented on FACT-777 Re: Facter should not downcase fact names The puppet language is case independent when it comes to names of defines and classes (can be entered with camel case, but are downcased internally). Variables are case sensitive; $varA is not the same as $vara. 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-3835) Specify that variables are case sensitive
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-3835 Specify that variables are case sensitive Issue Type: Task Assignee: Unassigned Components: DSL Created: 2015/01/13 4:57 AM Fix Versions: PUP 4.1.0 Priority: Normal Reporter: Henrik Lindberg The Puppet Language Specification should specify that variable names are case sensitive - the variable $varA is not the same as $vara. Add Comment
Jira (HI-233) Support array merge for automatic parameter lookup
Title: Message Title R.I.Pienaar commented on HI-233 Re: Support array merge for automatic parameter lookup Henrik Lindberg yeah I think I agree that's probably best. So we'd need some kind of data description to go with hiera, something that overlays all the possible backends 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-777) Facter should not downcase fact names
Title: Message Title Henrik Lindberg commented on FACT-777 Re: Facter should not downcase fact names There is a problem if a fact starts with an upper case letter since variables cannot start with one. I believe this is the origin of the downcasing of facts when represented as variables.(Hence, simply stopping doing the downcase will not work). A compromise is to store the facts in the $facts variable with verbatim names since there is no problem in using camel case / initial upper case names as a hash key, but not change how the mapping is done to top scope variables (something that in itself is a problem that should be fixed). 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-233) Support array merge for automatic parameter lookup
Title: Message Title Henrik Lindberg commented on HI-233 Re: Support array merge for automatic parameter lookup It could certainly be done that way; e.g. globally associating a provider of the data with a key. By default, the provider is a "literal provider". This declaration would contain parameters to the provider. There is however a problem with this, if composing data provided by different authors in different backends, one is designed to merge, another not. This concern then bubbles to the top (which is problematic). 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-233) Support array merge for automatic parameter lookup
Title: Message Title R.I.Pienaar commented on HI-233 Re: Support array merge for automatic parameter lookup But there would only be one description per key, so all authors creating data for all backends should do it with the same data description? One backend cant return string data and another hash - they can now, its a nightmare 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-233) Support array merge for automatic parameter lookup
Title: Message Title Henrik Lindberg commented on HI-233 Re: Support array merge for automatic parameter lookup Naturally you want the result to be type checked. This happens automatically if the parameter has type annotation. I can imagine declaring type in hiera data too. However I am thinking in a general sense, that the value of a key is provided by a provider and that such a provider can specify merge behavior, but can also be some other type of logic, an alias for another key, a composition of a hash of a number of given keys etc. This to reduce repetition in the data etc. Such encoding can naturally be done in the data for one backend without affecting how it is done in some other backend. You would get the same effect as you describe by binding a "merging provider" for a key at the top level as it would then continue to lookup the same key and merge the result. Another example is that lower levels is a merge of a hashkey. Now, however, you want to override this at the top level in the hierarchy with a hard coded hash. etc. etc. 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I generally don't have spaces where the module itself is. It could be an issue with beaker-rspec though. I used the command you used and got an error, but then I used bundle exec rspec spec and all is well (with at least puppetlabs-acl). C:\code\puppetlabs\modules\puppetlabs-acl>bundle exec rake spec Your Gemfile lists the gem pry (>= 0) more than once. You should probably keep only one of them. While it's not a problem now, it could cause errors if you change the version of just one of them later. rake aborted! LoadError: cannot load such file -- beaker/tasks/test C:/code/puppetlabs/modules/puppetlabs-acl/Rakefile:4:in `require' C:/code/puppetlabs/modules/puppetlabs-acl/Rakefile:4:in `' (See full trace by running task with --trace)
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Rob Reynolds Component/s: Modules 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Rob Reynolds Component/s: PMT 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-3560) Add support for properly signed trusted facts
Title: Message Title Jeremy Barlow assigned an issue to Justin May Puppet / PUP-3560 Add support for properly signed trusted facts Change By: Jeremy Barlow Assignee: Josh Cooper Justin May 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-3560) Add support for properly signed trusted facts
Title: Message Title Jeremy Barlow commented on PUP-3560 Re: Add support for properly signed trusted facts Reassigning to Justin May to diagnose CI test failures for the dev branch 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 (HI-307) cleanup dns-alt-names setting and CLI option
Title: Message Title Henrik Lindberg created an issue Hiera / HI-307 cleanup dns-alt-names setting and CLI option Issue Type: Task Assignee: Unassigned Created: 2015/01/13 8:40 AM Priority: Normal Reporter: Henrik Lindberg See PUP-3684 for background. Basically, there are two settings/options that affect the same setting; --dns-alt-names, and --dns_alt_names. In order to unite the two with the same setting riority, there is the need to have a method in settings that allows patching of the CLI provided value. This method was renamed from set_value (a deprecated method) to patch_value a non deprecated method that is marked as private. The task is to get rid of this horrible construct by deprecating the unwanted form of --dns-alt-names and updating the code. Add Comment
Jira (PUP-3836) cleanup dns-alt-names setting and CLI option
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-3836 cleanup dns-alt-names setting and CLI option Change By: Henrik Lindberg Issue Type: Task Improvement Key: HI PUP - 307 3836 Project: Hiera Puppet 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-3836) cleanup dns-alt-names setting and CLI option
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3836 cleanup dns-alt-names setting and CLI option Change By: Henrik Lindberg Fix Version/s: PUP 4.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-3836) cleanup dns-alt-names setting and CLI option
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3836 cleanup dns-alt-names setting and CLI option Change By: Henrik Lindberg 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-3684) Remove deprecated methods from Puppet::Settings and Puppet::Module
Title: Message Title Henrik Lindberg commented on PUP-3684 Re: Remove deprecated methods from Puppet::Settings and Puppet::Module All of the removals have been made except the set_value for which there is a ticket PUP-3836 to deal with the cleanup of --dns-alt-names setting/CLI option. To make that easier, the deprecated set_value method was renamed to patch_value and marked to be @api private to facilitate the change in PUP-3836 without having to also deprecate this method. 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-2105) Puppet config face and the --configprint option operate directly on environment.conf.
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2105 Puppet config face and the --configprint option operate directly on environment.conf. 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-3750) The mailalias type should allow the specification of included files
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3750 The mailalias type should allow the specification of included files 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I believe the problem lies with the following: 1. rake spec command doesn't wrapped ruby rspec in quotes 2. Since ruby is installed c/program\ files/puppet\ labs the command fails If ruby were installed under c/puppet_labs/ this problem would not exist. The work around here is to run bundle exec rspec spec. However, this is a different workflow that is not documented in puppet labs spec helper and is only needed on the windows platform to get around the misquoting issue. The issue might be how rake is calling ruby to execute rspec on windows. Should there be one-off rake tasks for windows? 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Yea, it works when ruby does not have spaces in the path. However puppet enterprise installs with spaces so its not something I can fix by removing the spaces. So a few issues here: 1. Change PE to install in path that does not contain spaces 2. Fix upstream rake command to find ruby better 3. Attach bandaid fix in puppetlabs_spec_helper to accommodate this issue on windows 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title
Corey Osman commented on PUP-3782
Re: modules on windows cannot run rake tasks to run unit tests
This is the error one should get.
C:\Program Files\Puppet Labs\lmc-test>bundle exec rake spec "C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe" -I'C:/Pro gram Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec -core-3.1.7/lib';'C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ru by/gems/2.0.0/gems/rspec-support-3.1.2/lib' C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/exe/rspec --patter n 'spec/ {classes,defines,unit,functions,hosts,integration}/*/_spec.rb' --color C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe: No such fi le or directory – C:/Program (LoadError) "C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe" -I'C:/Pro gram Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec -core-3.1.7/lib';'C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ru by/gems/2.0.0/gems/rspec-support-3.1.2/lib' C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/exe/rspec --patter n 'spec/{classes,defines,unit,functions,hosts,integration}
/*/_spec.rb' --color failed
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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Rob Reynolds commented on PUP-2564 Re: Specify UTF-8 as a default encoding for puppet Explore the possibility of globally setting Encoding.default_internal = Encoding::UTF_8. This is something we discussed a bit while working on PUP-3779. 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-2105) Puppet config face and the --configprint option operate directly on environment.conf.
Title: Message Title Kurt Wall commented on PUP-2105 Re: Puppet config face and the --configprint option operate directly on environment.conf. Verified in master at SHA=c874855. manifest, modulepath, and config_version cannot be set in puppet.conf: $ crossfader exec bundle exec puppet config print manifest Error: Could not initialize global default settings: Cannot set manifest settings in puppet.conf $ crossfader exec bundle exec puppet config print modulepath '/no/such/path' Error: Could not initialize global default settings: Cannot set modulepath settings in puppet.conf $ crossfader exec bundle exec puppet config set config_version $RANDOM Error: Could not initialize global default settings: Cannot set config_version settings in puppet.conf $ cro
Jira (PUP-3750) The mailalias type should allow the specification of included files
Title: Message Title Eric Thompson commented on PUP-3750 Re: The mailalias type should allow the specification of included files verified on rhel7 at SHA: with: [root@ujoqvj7wyru5729 ~]# puppet describe mailalias mailalias = Creates an email alias in the local alias database. Parameters -- - **ensure**
Jira (PDB-1109) Unit testing failure: Couldn't satisfy such-that predicate after 10 tries
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1109 Unit testing failure: Couldn't satisfy such-that predicate after 10 tries Change By: Kenneth Barber Sprint: PuppetDB 2015-01-28 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-1109) Unit testing failure: Couldn't satisfy such-that predicate after 10 tries
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1109 Unit testing failure: Couldn't satisfy such-that predicate after 10 tries Issue Type: Bug Affects Versions: PDB 3.0.0 Assignee: Unassigned Created: 2015/01/13 10:04 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber We keep hitting a problem with one of the clojure tests: lein test :only puppetlabs.puppetdb.zip-test/post-order-collect ERROR in (post-order-collect) (core.clj:4403)
Jira (PUP-3750) The mailalias type should allow the specification of included files
Title: Message Title Eric Thompson commented on PUP-3750 Re: The mailalias type should allow the specification of included files verified on ubuntu14.04 at SHA: c874855 with: root@v4ft9u2enyg8267:~# puppet describe mailalias mailalias = Creates an email alias in the local alias database. Parameters -- - **ensure**
Jira (PUP-2105) Puppet config face and the --configprint option operate directly on environment.conf.
Title: Message Title Kurt Wall commented on PUP-2105 Re: Puppet config face and the --configprint option operate directly on environment.conf. The directory environments still work as described, too. If a specified, non-existent dir env is specified, puppet emits an error: $ crossfader exec bundle exec puppet config print manifest modulepath config_version --environment three /Users/kwall/repos/puppet/lib/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'three' anywhere in the path: /Users/kwall/.puppet/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /Users/kwall/repos/puppet/lib/puppet/application_support.rb:29:in `push_application_context' from /Users/kwall/repos/puppet/lib/puppet/application.rb:337:in `run' from /Users/kwall/repos/puppet/lib/puppet/util/command_line.rb:124:in `run' from /Users/kwall/repos/puppet/lib/puppet/util/command_line.rb:72:in `execute' from /Users/kwall/repos/puppet/bin/puppet:5:in `' from /Users/kwall/repos/puppet/.bundle/ruby/2.0.0/bin/puppet:23:in `load'
Jira (PDB-1110) Support HA in PE Module
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1110 Support HA in PE Module Issue Type: New Feature Assignee: Unassigned Created: 2015/01/13 10:40 AM Priority: Normal Reporter: AJ Roetker The PE module needs to be updated to optionally manage the puppetdb-sync service config for PuppetDB for HA, in addition the master part of the module needs to take a list of PuppetDB's for the terminus to use. We should also work through what a user wanting to add a second PDB should look like (I imagine it will look fairly similar to adding additional master). Things to look out for: Certificate whitelisting on RBAC/Master; functionality should already be there in the pe-pdb module with the defined-type Add Comment
Jira (PDB-1110) Support HA in PE Module
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1110 Support HA in PE Module Change By: AJ Roetker The PE module needs to be updated to optionally manage the puppetdb-sync service config for PuppetDB for HA, in addition the master part of the module needs to take a list of PuppetDB's for the terminus to use. We should also work through what a user wanting to add a second PDB should look like (I imagine it will look fairly similar to adding additional master).Things to look out for:- Certificate whitelisting on RBAC/Master; functionality should already be there in the pe-pdb module with the defined-type - There might be some other config changes etc that haven't been updated in the pe module that may need to be updated 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 (PUP-1445) Certificate generation makes poor fingerprint digest alogrithm selection
Title: Message Title Josh Cooper commented on PUP-1445 Re: Certificate generation makes poor fingerprint digest alogrithm selection In recent versions of puppet, certificates are signed using SHA256withRSA if it's available, or SHA1withRSA. These are digital signature algorithms, which happen to use a hash algorithm. Puppet continues to default to md5 for fingerprinting. Unfortunately, the setting for this digest_algorithms affects both fingerprints and file bucketing, so changing it would break file bucketing. I'd recommend we change the default fingerprint algorithm for the cert CLI related tools to SHA256, and preserve the --digest command line argument for specifying alternate digest algorithms. 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-3782
modules on windows cannot run rake tasks to run unit tests
Change By:
Ethan Brown
When trying to run module unit tests on windows there seems to be an issue around shell escaping during the run of rspec. See output at bottom. Basically since windows has spaces in paths the rake command does not escape spaces. I believe this to be an issue in puppetlabs_spec_helper.Steps to reproduce:1. install pe 3.7 x64 on windows2. open puppet command prompt3. gem install bundler4. Install git and include option to have git in the windows command prompt so git is accessible in the puppet command prompt5. git clone https://github.com/logicminds/site_test.git6. bundle install7. bundle exec rake spec8. Watch the house burn down. {code} "C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe" -I'C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/lib';'C:/Program Files/ Puppet Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-support-3.1.2/lib' C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/exe/rspec -- pattern pattern 'spec/{classes,defines,unit,functions,hosts,integration}/**/*_spec.rb' --color {code}
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...@googleg
Jira (PUP-3750) The mailalias type should allow the specification of included files
Title: Message Title Eric Thompson commented on PUP-3750 Re: The mailalias type should allow the specification of included files verified on windows2012r2-r64 at SHA: c874855 with: Administrator@r91fz0f0tq47dro ~ $ cmd /c puppet describe mailalias mailalias = Creates an email alias in the local alias database. Parameters --
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests 1. Change PE to install in path that doesn't contain spaces I get that PE installs with a vendored ruby that ensures the runtime for Puppet/Modules. However I'm not sure that necessarily applies to module development. At the current time we don't develop modules in that way. I'm not sure where in the documentation you saw that it said you should do that. If you have specific documentation that pointed you down this path, please point me to them so we can get them corrected. The default install path for Windows is to Program Files and so we keep with that well-known default (https://docs.puppetlabs.com/pe/latest/install_windows.html#program-directory). We do have in our documents on how you override that location - https://docs.puppetlabs.com/pe/latest/install_windows.html#msi-properties 2. Fix upstream rake command to find ruby better and use correct quotes 3. Attach bandaid fix in puppetlabs_spec_helper to accommodate this issue on windows I agree these should be fixed. So should the use of beaker-rspec (either it works on Windows or it is removed entirely from anything less than black box integration tests). Recommended Module Development Path This is the currently recommended way of doing module development on Windows IMHO. Don't use the installed Puppet location for your development. Most module development is done based on bundle install, which installs the puppet gem and all of its dependencies. You don't want to mess up the vendored Ruby directory. Development dependencies are different than runtime dependencies. Install Ruby - the version of Ruby that we vendor can be queried. Install that same version to your development computer. Install DevKit - some modules are doing to need it. Create modules in directories without spaces in the path / Checkout existing modules to locations without spaces in the path. Pick a reference Windows module that works (puppetlabs-acl) and see what additional work has been done to spec_helper. Use a regular command line (cmd.exe) or PowerShell instead of the Puppet Command Prompt.
Jira (PUP-3750) The mailalias type should allow the specification of included files
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3750 The mailalias type should allow the specification of included files Change By: Eric Thompson QA Contact: 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-3750) The mailalias type should allow the specification of included files
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3750 The mailalias type should allow the specification of included files Change By: Eric Thompson QA Status: Reviewed 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Ethan Brown commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Corey Osman thanks for the report. Typically our internal development environments are assembled with: Git Ruby runtime + bundler Ruby devkit Puppet source code from GitHub What you've done is a little different from what we practice internally, which is why you're encountering some issues. I realize that we encourage folks to install Puppet agent from MSI on Windows to pick up the necessary environment to do module development, so agree that this is something we need to fix. As far as your suggestions, we can't change the Puppet installation directory (not only would this be difficult to maintain, but we also follow Microsoft's installation guidelines). We can address this in another fashion - whether this is via the rake command, PSH, documentation, etc - I don't have an answer yet. But certainly this is a barrier to entry for Windows module development and we will be fixing it. Thanks again for the report. 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 r
Jira (PDB-1105) Remove experimental message from v4 endpoint
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1105 Remove experimental message from v4 endpoint Change By: AJ Roetker Assignee: AJ Roetker 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-1111) Unit tests have test.check transient failures
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB- Unit tests have test.check transient failures Change By: Ryan Senior Sprint: PuppetDB 2015-01-28 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-1111) Unit tests have test.check transient failures
Title: Message Title Ryan Senior created an issue PuppetDB / PDB- Unit tests have test.check transient failures Issue Type: Bug Assignee: Unassigned Created: 2015/01/13 11:06 AM Priority: Normal Reporter: Ryan Senior The tree zipper tests use test.check and specifically the "such-that" function. It generates a possible tree, checks to see that it satisfies a predicate (coll? in this case). If it generates 10 things that don't satisfy the predicate (such as a number, boolean or nil) it will throw a runtime exception. This is generating some false negatives in our unit tests and needs to be fixed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1109) Unit testing failure: Couldn't satisfy such-that predicate after 10 tries
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1109 Unit testing failure: Couldn't satisfy such-that predicate after 10 tries Change By: Ryan Senior Sprint: PuppetDB 2015-01- 28 14 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-1109) Unit testing failure: Couldn't satisfy such-that predicate after 10 tries
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-1109 Unit testing failure: Couldn't satisfy such-that predicate after 10 tries Change By: Ryan Senior Assignee: Ryan Senior 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Its hard enough to have windows folks use the command line. To tell them they need to install cygwin, ruby (compile it) and and also install the giant list of other runtime dependencies that either come with puppet or with the module (bundle install) is just too much. My locally documented approach was to do the following. 1 install PE 2. Install git for windows (additionally, choose option to add unix tools to cmd path) 3. Development within the puppet command prompt. 4. Use Geppetto to edit files. This takes 5 minutes to setup and its completely straight forward. Install additional gems into PE's environment does not pose any risk because its a development environment and can be disposed of at any time. The only thing I dislike about this setup is that its based of the windows command prompt and not the cygwin bash prompt. For anybody reading this, the work around is to either use a non-PE environment suggested above or use bundle exec rspec spec. 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-1679) Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1679 Eradicate usage of FileUtils / File .chmod and move to the FileSystem abstraction Change By: Ethan Brown Fix Version/s: PUP 4.0.0 Fix Version/s: PUP 4.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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Jeff McCune commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Kicking this back into "to-do" since I'm not making much progress on this with the memory leak investigation and 1.0.1 release tickets. Next steps are identifying the entire set of files that are in-scope, e.g. vardir, confdir, ssldir, more? and then categorizing each file as content or configuration. 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I don't know where you got cygwin and compiling ruby...? Ruby is already compiled native to Windows, and can be installed as simply as choco install ruby -v 2.0.0.48100. Similarly with DevKit - choco install ruby2.devkit It's probably around the same amount of time: choco install puppet git choco install ruby -v 2.0.0.48100 refreshenv (cmd.exe only), otherwise close and reopen shell choco install ruby2.devkit bundle install bundle exec rake spec (or whatever we decide this should be) 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/
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests To not lose the point, there is some work that needs to be done to ensure that the existing modules work and that we have properly documented how folks should set up for Windows development. 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests This is really helpful, thanks for providing your "setup script". We were using cygwin to install ruby but this is obviously the better way. Completely forgot about choco. Is this setup already documented? If not, I might write some documentation to get this setup. Perhaps is there a module to install all these packages already? If not I will create one. 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests There is also this - adding the updated cert for gems. Forgot that one. I don't know that we have a documented way yet. I foresee that being one of the asks as part of closing 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests This is how I updated the cert curl https://raw.githubusercontent.com/rubygems/rubygems/master/lib/rubygems/ssl_certs/AddTrustExternalCARoot-2048.pem -O 'C:\Program Files\Puppet Labs\Puppet Enterprise\sys\ruby\lib\ruby\2.0.0\rubygems\ssl_certs\AddTrustExternalCARoot-2048.pem' 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-3837) Use FFI for all registry calls instead of win32/registry.rb
Title: Message Title Rob Reynolds created an issue Puppet / PUP-3837 Use FFI for all registry calls instead of win32/registry.rb Issue Type: Improvement Assignee: Unassigned Components: Windows Created: 2015/01/13 1:05 PM Labels: windows Priority: Normal Reporter: Rob Reynolds There is a lot of encoding issues surrounding the use of win32/registry.rb from Ruby. The recommendation is that we stop using that and instead make the calls to the registry directly using FFI. Quite a bit of background is on the PR for PUP-3779 - https://github.com/puppetlabs/puppet/pull/3459#discussion_r22838455 The issues surrounding ruby's win32/registry.rb could also impact: registry module Any custom facts that make registry calls
Jira (PUP-3837) Use FFI for all registry calls instead of win32/registry.rb
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3837 Use FFI for all registry calls instead of win32/registry.rb Change By: Rob Reynolds Fix Version/s: PUP 4.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-3837) Use FFI for all registry calls instead of win32/registry.rb
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3837 Use FFI for all registry calls instead of win32/registry.rb Change By: Rob Reynolds There is a lot of encoding issues surrounding the use of win32/registry.rb from Ruby v2 . 1 and above. Prior to 2.1, there was some craziness, but it didn't affect us in a negative way. The recommendation is that we stop using that and instead make the calls to the registry directly using FFI.Quite a bit of background is on the PR for PUP-3779 - https://github.com/puppetlabs/puppet/pull/3459#discussion_r22838455The issues surrounding ruby's win32/registry.rb could also impact: * registry module * Any custom facts that make registry calls 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit 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-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Rob Reynolds Comment: :) 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.
