Well...I had never called 'downcase' myself but it appears to be a function
defined in in the puppet stdlib module.
But I seem to have narrowed down the cause to having an unused 'classes:'
line in my hostname.domain.com.yaml when there is also a 'classes:' line in
my common.yaml
It seems as so
On Wednesday we put yum.puppetlabs.com and apt.puppetlabs.com behind the
CloudFront CDN in order to accelerate downloads for overseas users. Both
repositories have historically been served from the Linode Fremont
datacenter, and download performance from Australia and Asia in particular
are dramati
I will look into that John, thanks. I haven't gotten to the Yaml level
yet, but we already have a temple we use now that is standard across the OS
we support. We then add in lines accordingly.
I had some luck with the sudo::config setup, so I may try to merge the two.
With having a class per
I use a template for a single /etc/sudoers:
# /etc/sudoers #
# This file MUST be edited with the 'visudo' command as root.
#
# Of course, if you do, Puppet will completely rewrite it 30 minutes later.
#
Defaultsenv_reset
<% unless @cmd_aliases.empty? -%>
# Cmnd alias specificati
BTW. I am running Foreman 1.14.3 and Puppet 4. All class assignments to
nodes are done via Foreman versus the site.pp.
On Friday, April 21, 2017 at 1:33:38 PM UTC-4, James Perry wrote:
>
> Thanks. I looked at saz/sudo, but at least they I did it, it didn't for my
> needs. We have a wide range o
Thanks. I looked at saz/sudo, but at least they I did it, it didn't for my
needs. We have a wide range of hosts that would have oracle, dba and tomcat
sudo rules. On another it would only have dba rules.
I didn't quite get how I would have it setup the sudo::conf blocks to do
what I would nee
I'm no expert by far, but since I have been doing a lot of reading lately
for an issue I am trying to resolve, would it make sense to do a define
block for this? Looking at
https://docs.puppet.com/puppet/4.9/lang_defined_types.html it seems this
*may* work for you with some tweaking / testing.
I take it you want to have one manifest that is agnostic to all
environments and copy the right files? Your files have to be put into each
environment respectively. When the manifest runs it will pull the file from
that environment on the server.
- A goes in
/etc/puppetlabs/code/environ
Check out saz/sudo (https://forge.puppet.com/saz/sudo). By default it
manages /etc/sudoers.d with `sudo::conf` instances and purges
/etc/sudoers.d of anything it didn't create, but if something else is
managing files in that directory you can set `sudo::purge: false` so they
can share nicely.
Rob
I'm at an impasse.
Due to changing requirements we have different local service accounts being
added 'ad hoc' to various servers. Each needs their own set of sudoers
lines. When moving from Puppet 0.25 to Puppet 4 I had to kludge something
together in a hurry. It works, but not well.
I look
First step would be to find where you're using 'downcase' ...
Error while evaluating a Function Call, undefined method `downcase' for
nil:NilClass
... and work from there.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from th
11 matches
Mail list logo
