On Thursday, October 1, 2015 at 12:26:44 PM UTC-7, Joshua Hoblitt wrote:
>
> I received marketing email this morning about "Puppet Application
> Orchestration". I'm guessing this is related to PRFC-6 and the recent
> PR's for PUP-s that are not publicly accessible.
>
> If this feature is
On Thu, Aug 13, 2015 at 3:28 PM, Ryan Coleman wrote:
>
> On Thu, Aug 13, 2015 at 3:10 PM, Chris Rigby
> wrote:
>
>> My issue in particular is related to a bug introduced into the future
>> parser in 3.8.2.
>>
>> The bug breaks compilation when using a reserve
On Thu, Aug 13, 2015 at 3:10 PM, Chris Rigby wrote:
> My issue in particular is related to a bug introduced into the future
> parser in 3.8.2.
>
> The bug breaks compilation when using a reserved keyword as a classname
> when the future parser is enabled.
>
> See https://tickets.puppetlabs.com/br
u are doing.
> After that most either drop immediately or stick around for a while,
> realize what you are doing, and drop eventually. Maybe they'll stick around
> and get interested in puppet modules! Who knows? :)
>
I noticed that hangouts are automatically posted to plus.go
I've posted this to Puppet-Users to better ensure those publishing to the
Puppet Forge see it. If you want to reply, please reply to Puppet-Dev.
With the launch of Puppet Enterprise 3.2 this week, the Puppet Forge added
search filters to help people find modules that are compatible with their
Pupp
On Mon, Feb 10, 2014 at 7:06 PM, Ryan Coleman wrote:
> Tomorrow, 9 a.m. PST, the Forge modules team will trial its first pull
> request triage Google Hangouts. Tomorrow's module is puppetlabs-apache.
> We've planned for an hour.
>
> The goal is to set aside time for di
On Tue, Feb 11, 2014 at 6:43 AM, Daniele Sluijters <
daniele.sluijt...@gmail.com> wrote:
> Hi,
>
> Would you mind specifying what tomorrow is? Depending on the timezone
> you're living in versus the timezone I'm reading this in my tomorrow might
> not be your tomorrow.
>
> I'm guessing tomorrow is
these and figure out what
works and what doesn't, trying to model ourselves after what the Puppet
platform team does.
--
Ryan Coleman | Modules & Forge | ryanycoleman on twitter & #puppet IRC
--
You received this message because you are subscribed to the Google Groups
"Puppet
On Thu, Jan 30, 2014 at 1:55 AM, Erik Dalén wrote:
> On a related note, what are the features of beaker vs rspec-system?
>
> We adopted rspec-system at Spotify and have written some node providers
> and fixes for it. Partly because it seemed like that was what the community
> modules were using (t
On Wed, Jan 29, 2014 at 3:03 PM, Ryan Coleman wrote:
> On Wed, Jan 29, 2014 at 10:58 AM, Igor Galić wrote:
>
>> I would like to propose a bug triage for the puppet modules
>> team. At least for the time being, during the transition to
>> beaker I would also like to see
tgresql/tree/master/spec/acceptance
&
https://github.com/puppetlabs/puppetlabs-apache/tree/master/spec/acceptance
[6]
https://github.com/puppetlabs/beaker/wiki/How-to-Write-a-Beaker-Test-for-a-Module
[7] https://github.com/puppetlabs/beaker/wiki/How-To-Beaker
--
Ryan Coleman | Modules &
r discussing this and for all of your contributions. We'll
get here soon, hopefully by next quarter if hiring is successful.
--
Ryan Coleman | Modules & Forge | ryanycoleman on twitter & #puppet IRC
--
You received this message because you are subscribed to the Google Groups
"
We've been working hard to reduce the complexity involved in publishing
modules to the Forge and make it simpler to find great modules. I'm writing
today to give you some background on the problems we're working to solve
and the approach we'd like to take to help solve them.
To publish a Forge mod
On Thu, Sep 26, 2013 at 6:45 AM, Andy Parker wrote:
> Agreed, the last thing that is needed is to present a solution that we say
> is to make things "easier" and then have people start the simple case by
> having to learn an abstract language expressed in data structures :)
>
> How about a hybrid
On Mon, Sep 23, 2013 at 11:14 PM, Ashish Nandurkar wrote:
> Hi,
>
> Puppet browser is working fine , But We are facing some issue on while
> connecting puppetdb with 8081 port accessing through browser .
>
> PFA .
>
Hello, you may have better luck with this particular issue on the Puppet
Use
On Mon, Sep 23, 2013 at 1:36 PM, William Van Hevelingen wrote:
> Can you add the openstack modules as well? They're under the stackforge
> namespace on github and puppetlabs namespace on the forge. There are twelve
> of them.
>
Hey Will, those metrics are intended for our team to keep tabs on the
and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-dev@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-dev.
> For more options, visit https://groups.google.com/groups/
On Wed, Aug 28, 2013 at 8:04 AM, Henrik Lindberg <
henrik.lindb...@cloudsmith.com> wrote:
> Questions
> =
> * Do you think it is of value to have a "R3" language revision in Puppet 4?
>
Would the language changes correspond to major.minor revisions in Puppet?
If so, keep in mind that very
rn itself needs more collaboration before it
starts getting applied to Puppet Labs modules. That said, you've got a more
appropriate thread going for that discussion already (on Puppet-Users) and
I look forward to continuing it there.
--
Ryan Coleman | Modules & Forge | ryanycoleman on twitter &a
abs modules to a
solid >=1.0.0 state where they'll all be regularly and expertly maintained
while strictly following SemVer rules.
I do empathize regarding the temporary instability for the few modules that
require it and I'll make sure that we clearly spell out what's happening in
the
dev@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-dev?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Ryan Coleman | Modules & Forge | @ryanycoleman | ryancoleman in #puppet
--
You received this message
com/group/puppet-dev?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Ryan Coleman | Modules & Forge | @ryanycoleman | ryancoleman in #puppet
--
You received this message because you are subscribed to the Google Groups
"Puppet Develop
ther big pain points at the
moment. If something's not quite right in that tool, consider contributing
to it. We'll certainly be looking at it for inspiration when we've got some
time to work on this.
I hope that helps!
--
Ryan Coleman | @ryanycoleman
Modules & Forge | Puppe
On Friday, May 11, 2012 10:00:36 AM UTC-7, Philip Brown wrote:
>
> I've just started experimenting with using some modules on our puppet
> installation, and observing behaviour.
> From these observations, it suddenly struck me, that the current module
> implementation, violates what has previou
24 matches
Mail list logo
