On 11/02/15 18:13, Trevor Vaughan wrote:
Heh, that's probably because it's the third hit in the list when you
search for Apache on the Forge.
Is there a way for people to mark Forge modules as unmaintained?
Not as far as I know. I ought to upload a new release with a big
warning in the
Hi,
can any one help me to work in puppet work..
i am started working in puppetdb, i need to connect to puppetdb and access
some fields.
i have downloaded the puppet source code from the github, they mentioned
some .pem files need to run the junit.
can any one tell me where to get these .pem
can any one help me to work in puppet work..
i am started working in puppetdb, i need to connect to puppetdb and access
some fields.
i have downloaded the puppet source code from the github, they mentioned
some .pem files need to run the junit.
I'm not sure where we mention junit :-). We
- Original Message -
From: Dominic Cleal dclea...@redhat.com
To: puppet-dev puppet-dev@googlegroups.com
Sent: Thursday, February 12, 2015 10:30:21 AM
Subject: Re: [Puppet-dev] Thoughts on Module Namespace Conflicts
On 11/02/15 18:13, Trevor Vaughan wrote:
Heh, that's probably
And this is why he gets awards...
+1
On Thu, Feb 12, 2015 at 9:12 AM, Erik Dalén erik.gustav.da...@gmail.com
wrote:
A related ticket to the interface and redirect functionality is
https://tickets.puppetlabs.com/browse/FORGE-111
There I just suggest the feature to be able to say that module
A related ticket to the interface and redirect functionality is
https://tickets.puppetlabs.com/browse/FORGE-111
There I just suggest the feature to be able to say that module B provides
the interface of module A version X. So either module can satisfy a
dependency on module A version X.
Then if
On 2015-12-02 15:12, Erik Dalén wrote:
A related ticket to the interface and redirect functionality is
https://tickets.puppetlabs.com/browse/FORGE-111
There I just suggest the feature to be able to say that module B
provides the interface of module A version X. So either module can
satisfy a
