Sorry Kylo, I thought the last post was from Henrik and my phone won't let me
see the full thread while replying...
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an e
Thanks for that clarification Henrik.
Also, having seen such behaviour before, it appears that PE is patched to
default to *not* stringifying facts, unlike the corresponding open source
version, which is why your test with PE behaved differently than with bundle.
--
You received this message b
On Mon, Mar 9, 2015 at 8:21 AM, Raphaël Pinson <
raphael.pin...@camptocamp.com> wrote:
> Hi Felix,
>
> By default, Puppet 3 stringifies all facts. And apparently,
> "--stringify_facts false" does not work with puppet apply…
>
For any boolean setting, "--some_boolean false" doesn't work, and you
i
Lets add some extra confusion here :
[witjoh@fc20 spec]$ puppet apply -e 'notify { $::os: }'
Notice: Compiled catalog for fc20.koewacht.net in environment production
in 0.03 seconds
Notice: {"name"=>"Fedora", "family"=>"RedHat",
"release"=>{"major"=>"20", "full"=>"20"}}
Notice: /Stage[main]/Mai
now I'm really embarrassed ...
hiding with dark red cheeks .
In the demo_spec file, i don't have to test three context, because I
only have one, using the osfamily fact, and the structures os fact (twice).
Now I'm green for all tests !!
Thanks for opening my (so closed) eyes.
I own you
On 09/03/2015 21:20, Chris Price wrote:
> On Mon, Mar 9, 2015 at 10:15 AM, Brice Figureau
> mailto:brice-pup...@daysofwonder.com>>
> wrote:
>
> On Mon, 2015-03-09 at 08:52 -0700, Chris Price wrote:
> >
> > This sounds great, thanks a ton for putting it together! I'll try to
> > ge
On Mon, Mar 9, 2015 at 10:15 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On Mon, 2015-03-09 at 08:52 -0700, Chris Price wrote:
> >
> > This sounds great, thanks a ton for putting it together! I'll try to
> > get some reviews going, and maybe at some point roll an experimental
> >
On Monday, 9 March 2015 17:33:27 UTC+1, Joshua Partlow wrote:
>
> On Mon, Mar 9, 2015 at 9:05 AM, Henrik Lindberg > wrote:
>
>> On 2015-09-03 14:54, Felix Frank wrote:
>>
>>> On 03/09/2015 02:16 PM, Henrik Lindberg wrote:
>>>
It would be splendid if we could define modulepath paths with
>
On Monday, 9 March 2015 17:05:22 UTC+1, henrik lindberg wrote:
>
> On 2015-09-03 14:54, Felix Frank wrote:
> > I also fail to see the value in that. Do you mean to allow an
> > environment to extend itself to a whole different file system tree?
> > Wouldn't that just be horrible for organizing
On Monday, 9 March 2015 14:54:14 UTC+1, Felix Frank wrote:
>
> On 03/09/2015 02:16 PM, Henrik Lindberg wrote:
> >> It would be splendid if we could define modulepath paths with
> >> $environment as variable part of path, like this:
> >> modulepath = /path/to/$environment/modules
> >> manifest =
On Mon, 2015-03-09 at 08:52 -0700, Chris Price wrote:
> On Mon, Mar 9, 2015 at 1:59 AM, Brice Figureau
> wrote:
>
> I think I've completed a milestone in respect with what you
> wanted and
> SERVER-111:
>
> https://github.com/masterzen/trapperkeepe
On Mon, Mar 9, 2015 at 9:05 AM, Henrik Lindberg <
henrik.lindb...@cloudsmith.com> wrote:
> On 2015-09-03 14:54, Felix Frank wrote:
>
>> On 03/09/2015 02:16 PM, Henrik Lindberg wrote:
>>
>>> It would be splendid if we could define modulepath paths with
$environment as variable part of path, li
On 2015-09-03 14:54, Felix Frank wrote:
On 03/09/2015 02:16 PM, Henrik Lindberg wrote:
It would be splendid if we could define modulepath paths with
$environment as variable part of path, like this:
modulepath = /path/to/$environment/modules
manifest = /path/to/$environment/manifest2/
Would the
On Mon, Mar 9, 2015 at 1:59 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
>
> I think I've completed a milestone in respect with what you wanted and
> SERVER-111:
>
> https://github.com/masterzen/trapperkeeper-authorization
>
>
> I've tried to put the better documentation I could in t
On 03/09/2015 04:21 PM, Raphaël Pinson wrote:
> Hi Felix,
>
>
> By default, Puppet 3 stringifies all facts. And apparently,
> "--stringify_facts false" does not work with puppet apply…
>
>
> Raphaël
I see. Well that's a relief ;-)
In a disturbing, not at all relieving way...
Thanks again,
Fe
Hi Felix,
By default, Puppet 3 stringifies all facts. And apparently,
"--stringify_facts false" does not work with puppet apply…
Raphaël
On Monday, March 9, 2015 at 4:13:33 PM UTC+1, Felix Frank wrote:
>
> Hi,
>
> me I'm now utterly confused by how this (not) works in the wild.
>
> $ bundl
Hi,
me I'm now utterly confused by how this (not) works in the wild.
$ bundle exec puppet apply -e 'notice $os'
Notice: Scope(Class[main]): {"name"=>"Debian", "family"=>"Debian",
"release"=>{"major"=>"jessie/sid", "full"=>"jessie/sid"},
"lsb"=>{"distcodename"=>"sid", "distid"=>"Debian",
"distdesc
Hi Johan,
It works for me. By that, I mean I get two errors:
* One error for the first test, when it meets $::os['family'], since $::os
is not defined in the first test case
* One error for the second test, since $::os['release'] is not defined in
this case
Cheers,
Raphaël
On Monday, Mar
Again , I'm loosing the fight
When i split up my rspec, it works, but the demo test always fails,
There is something I overlook.
Maybe someone else sees my mistake ??
https://github.com/witjoh/rspec
Grts
Johan
--
Johan De Wit
Open Source Consultant
Red Hat Certified Engineer
On 03/09/2015 02:16 PM, Henrik Lindberg wrote:
>> It would be splendid if we could define modulepath paths with
>> $environment as variable part of path, like this:
>> modulepath = /path/to/$environment/modules
>> manifest = /path/to/$environment/manifest2/
>>
>> Would there be any interest for thi
Yes, https://tickets.puppetlabs.com/browse/PUP-4131
On Monday, March 9, 2015 at 1:47:53 PM UTC+1, Trevor Vaughan wrote:
>
> +1 for this. Is there a bug to go vote for?
>
> Thanks,
>
> Trevor
>
> On Mon, Mar 9, 2015 at 8:44 AM, Raphaël Pinson > wrote:
>
>> Hello,
>>
>>
>> I've recently tried to us
On 2015-08-03 20:27, Bostjan Skufca wrote:
Hi all,
this change I have not yet implemented, but I believe it might be nice
to have.
Currently in environment.conf we can specify modulepath with relative or
absolute paths to module directories, like this:
modulepath = modules/:/some/other/location
On 2015-08-03 20:10, Bostjan Skufca wrote:
Hi there,
I like to have my environments organized into multiple subdirectories.
Puppet configuration supports that by defining multiple paths for
environmentpath setting, separated by ':'.
However, I find it very convenient to use this simple configur
+1 for this. Is there a bug to go vote for?
Thanks,
Trevor
On Mon, Mar 9, 2015 at 8:44 AM, Raphaël Pinson <
raphael.pin...@camptocamp.com> wrote:
> Hello,
>
>
> I've recently tried to use the following syntax for a gem resource:
>
>
>
> package { 'hiera-eyaml-gpg':
> ensure => '>= 0.5.pre1'
Hello,
I've recently tried to use the following syntax for a gem resource:
package { 'hiera-eyaml-gpg':
ensure => '>= 0.5.pre1'
provider => 'gem',
}
It *does* work, but is not idempotent, since it cannot compare ">=
0.5.pre1" with the installed version "0.5.pre1".
The following code
Hi Martin,
What do you mean by "translating to Puppet DSL"? Do you have an example of
what you want to achieve?
Raphaël
On Thursday, February 26, 2015 at 9:02:24 AM UTC+1, Martin Alfke wrote:
>
> Hi Raphael,
>
> can the Augeas provider “translate” from xml into Puppet DSL and vice
> versa
On Sun, 2015-02-22 at 21:18 -0800, Eric Sorenson wrote:
>
> > On Feb 16, 2015, at 2:01 AM, Brice Figureau
> > wrote:
> >
> > Hi,
> >
> > Following a conversation I had with Kevin and Deepak at last Ghent
> > Contributor summit about solving SERVER-111[*], I started working on
> > a
> > clojure
27 matches
Mail list logo
