t functions, you have the entire catalog at your disposal and can
> do with the data what you will.
>
> Good Luck,
>
> Trevor
>
> On Fri, Dec 16, 2016 at 5:52 PM, Johnson Earls > wrote:
>
>> Hello all,
>>
>> I was just wondering - has anyone come across a
Hello all,
I was just wondering - has anyone come across a plugin or something that
would allow the use of exported resources in Puppet 4.x *without* using
PuppetDB? The company I work for has declared PostgreSQL taboo within the
corporate network and so I cannot run PuppetDB, and the lack of
Hey all,
Just wondering: Is there a reason I'm not understanding for why property
values that include a :required_features option will raise a puppet error
if the feature is not available, but parameters that include
:required_features are silently [except for a debug message] ignored if the
Another rspec question:
Is there any way to get rspec to tell you, when a test fails, what the
contents of the catalog was, at a high level at least, that generated the
failure?
I've got a code block that looks right to me, and an rspec test that looks
right to me. the test is failing and I h
Thanks, I'll try that.
- Johnson
On Monday, July 20, 2015 at 1:30:14 PM UTC-7, Hunter Haugen wrote:
>
> There is no helper built in to rspec-puppet to do this, but you can do it
> by using an rspec expect() around a catalogue.resources check:
>
> it "has no file resources with ensure => directory
RSpec question for all the helpful folks here:
How do I test that there is no resource in the catalog that matches certain
parameters?
I know how to test that a specific resource does not exist, or a specific
resource does not match certain parameters.
I want to test that, for example, there a
All of my systems get the puppet-agent package installed and enabled as
part of kickstart. The puppetserver package only later gets installed for
servers that will be puppet servers. Is this ordering really that
unexpected?
On Thursday, May 7, 2015 at 12:06:53 PM UTC-7, Josh Cooper wrote:
>
>
never mind. puppet agent ignores the user/group config settings, so those
should be kept at puppet, and ${::settings::user} / ${::settings::group}
should not be used to configure agent-related options (such as file
ownership).
On Tuesday, May 5, 2015 at 10:40:00 PM UTC-7, Johnson Earls wrote
I'm running into a frustrating issue, and I'm wondering if I'm just not
doing something right.
My understanding is that the puppet agent has to run with the config "user"
and "group" set to "root" so that it can make changes to the system.
The puppet server, on the other hand, runs as user and g
ohnson
On Monday, May 4, 2015 at 12:25:24 PM UTC-7, Johnson Earls wrote:
>
> Hey folks,
>
> I just wanted to find out if anyone has been successful in setting up
> puppet server 2.0.0 and running it?
>
> I ask because, in my test deployment with the puppet server and one pup
Hey folks,
I just wanted to find out if anyone has been successful in setting up
puppet server 2.0.0 and running it?
I ask because, in my test deployment with the puppet server and one puppet
agent, the puppet server crashed after less than 5 hours with an out of
memory error. I've just resta
As a follow-up to my own post - is it a "bad thing" to use the
/opt/puppetlabs/puppet version of "gem" to install librarian-puppet into
the puppetlabs area?
- Johnson
On Tuesday, April 28, 2015 at 2:34:02 PM UTC-7, Johnson Earls wrote:
>
> Hello!
>
> This is m
Hello!
This is my first time posting here, and I freely admit I'm a complete
newbie to Puppet and librarian-puppet. I briefly had a puppet 3.7.4
"playground" set up and started learning about coding modules and
incorporating stuff from the Forge and was starting to work my way into the
Roles
7;ve
> patched our code to use an updated repo location with Passenger 4.x, but
> we'd like to be able to use 5. We are seeing the exact same behavior.
> Puppet 3.7.4 (installed via debian packages), Ubuntu 12.04.
>
> On Friday, March 13, 2015 at 5:14:32 PM UTC-7, Johnson Earls
t the end of auth.conf, my
access started working again.
Am I reading the logs and auth.conf file correctly in my conclusion that
the default deny-all ACL is preventing the puppet-inserted ACLs from taking
effect, or am I misconfigured somewhere else?
Thanks in advance,
- Johnson Earls
--
You rec
15 matches
Mail list logo
