On Wed, Jul 5, 2017 at 9:34 AM, Trevor Vaughan
wrote:
> I had to hack around this by adding the Puppet repos and doing a system
> update before proceeding.
>
> Irritating, but it worked.
>
> On Sun, Jul 2, 2017 at 4:02 AM, Thomas Müller
> wrote:
>
>> just wanted to start beaker testing with pupp
Hello puppet devs!
The puppet 3.x series has been EOL'd as of the beginning of 2017 and is no
longer supported by Puppet Inc. (
https://puppet.com/misc/puppet-enterprise-lifecycle/)
In the interest of forward progress we will begin testing on ruby and
puppet versions no older than our current old
>> For those of you in APAC, we apologize for the still-inconvenient time
>> slot. Feel free to reply here with ideas!
>>
>>
> I just talked to Hunter on IRC. Maybe we can flip flop the times of the
> meeting. For example 9:00UTC and the next week 17:00UTC. This would allow
> us a kind of US meeti
Hello,
tl;dr Puppet Modules Community Triage meeting is moving to 17:00-18:00 UTC
This is a quick note that in the last Puppet Modules Community Triage
meeting we discussed a change in the specified time that the meeting
happens.
For those of you who are curious about what the triage meeting is,
> On Thursday, February 25, 2016 at 7:45:46 PM UTC-6, Trevor Vaughan wrote:
>>
>> Sorry about that.
>>
>> What I mean is this:
>>
>> A -> [] -> B is not equivalent to A -> B since failures in A will not
>> affect B.
>>
>> However, it would be equivalent to [A,B] which I am reading as A before B
>>
On Thu, Feb 25, 2016 at 12:44 PM, Hunter Haugen
wrote:
> I am following up with a runtime type strictness thing.
>
>>
>> If you have a construct like this in your manifests:
>>
>> Notify['left'] -> $stuff -> Notify['right']
>>
>>
I am following up with a runtime type strictness thing.
>
> If you have a construct like this in your manifests:
>
> Notify['left'] -> $stuff -> Notify['right']
>
>
Thansk for asking! For me, I would prefer the ordering to follow left ->
right, and not error or warn.
If I have expressed Notify['l
No merge access?
-Hunter
On Tue, Mar 3, 2015 at 9:27 AM, Daniele Sluijters <
daniele.sluijt...@gmail.com> wrote:
> Ahem, why u no
> https://github.com/puppet-community/community-triage/tree/master/modules/notes
> ?
>
>
> On Thursday, 26 February 2015 20:12:56 UT
Here are the notes from this weeks module PR triage which happens every
week at 10:00am PST or PDT in #puppet-dev on Freenode
Mostly reviewed nodejs, with some postgresql/stdlib/gcc/java/rabbitmq
thrown in for good measure, then talked about nibalizer's
puppet-community-ci bot that he is working o
This reminds me of ARM-17 that I tried to model after
Haskell/Python/Clojure https://github.com/puppetlabs/armatures/pull/64 . It
stalled out due to lack of time, though it may have some relevant content.
-Hunter
On Tue, Feb 10, 2015 at 12:44 PM, Heck, Walter
wrote:
> Hi Henrik,
> On Tue, Feb
I commented on https://github.com/puppetlabs/beaker/issues/499 with my
method for adding a custom (closed sourced; boo) hypervisor for testing in
one module. The exact same mechanism could be used for all manner of
extension gems (or one gem, as beaker-extensions is).
beaker-rspec is essentially a
On Mon, Sep 8, 2014 at 6:28 AM, Bomber wrote:
> Is any plans to implement lightweight puppetdb replacement for
> storeconfigs?
>
https://github.com/nightfly19/minidb is an implementation that I came
across. I'm not sure if it was a hobby project or used in production.
--
You received this mess
Hello!
For those of you who attend the puppet module triage every Thursday at 10am
PDT/PST (1700/1800 UTC depending on US daylight savings), the coming
meeting on Sept 11th will be cancelled due to internal meetings. We'll
resume the following week on Sept. 18th.
For those of you who do not come,
Another option might be to call the facts indirector with the
network_device terminus from the confine block itself... Something like
confine :true => begin
a = Puppet::Node::Facts.indirection
a.terminus_class = :network_device
a.find(Puppet::Indirector::Request.new(:facts, :f
If you wanted to have the service as the resource title and pass the
protocols as an array like this:
port { 'telnet',
protocols => ['tcp', 'udp'],
number=> '22',
port_aliases => ['alias1','alias2'],
}
you can use a template that iterates on `protocols.each do |p|` and
returns multiple
> Also, what do you mean about cross-stage dependencies being broken?
Sorry, misinterpreted something Nan said. It works like it should (ie,
creating circular dependencies when a resource in a later stage
requires a resource in an earlier stage).
-Hunter
--
You received this message because you
Random idea. If stages themselves worked via tags instead of adding
something to the graph (and creating many-to-many dependencies), would
that be more functional?
If you could use the tag() function to apply a tag to the class as
normal, then define if that tag comes before or after the 'main' ta
17 matches
Mail list logo
