You should be including the role, not the profile in your manifests/site.pp
node {
include role::mysshrole
}
On Wednesday, 29 June 2016 15:48:07 UTC+10, Alex Samad wrote:
>
> Hi
>
> I have a new install.
>
> I want to use the node <- role <<- profiles setup.
>
> I want to define a profile for
Not all but most of it. I guess the intention was to use the PuppetDB since
that is already an existing data source. Pushing the info will require
setting up some more infrastructure but I understand that it might need to
happen. Thanks.
On Friday, 8 July 2016 10:52:29 UTC+10, LinuxDan wrote
Hi
Think I have had a miss understanding of the scope of
puppet variables
hiera data..
Think I have been mixing the two
I think my question here is how do you use hiera() in side a yaml to look
up info outside that current yaml.
so if hiera has check 1.yaml then 2.yaml then 3.yaml. How doe
Puppet is, IMHO, the wrong tool for this job.
If you need info every 5 minutes, make a cron script to run and push the info
where it is needed. I am guessing you do not need ALL the facts. Is that
correct ?
> On Jul 7, 2016, at 8:19 PM, Haani Niyaz wrote:
>
> Background:
>
> We are interest
*Background:*
We are interested in building a simple dashboard and looking at leveraging
the PuppetDB API to retrieve the data (facts). However a requirement exists
to have some information update more frequently, say 5mins.
*Question:*
I suspect running the agent every 5mins will create too m
Hi
Using a global ENC - this is allocating facts like location and envornment.
in my hiera I had
# Envornment - YB
- "ybenv/%{::ybenv}"
so I would have say
prod.yaml
and
# Location - YB
- "yblocation/%{::yblocation}"
to id location or datacentre
I setting
yblocation: alc << not su
I have a defined resource type (let's call it `widget`) which gets defined
multiple times per customer. Each customer has their own default
configuration values for their widgets, and these are very rarely (but
occasionally) overridden. I'd like to minimize the amount of typing
necessary wh
I have a defined resource type (let's call it `widget`) which can be
defined multiple times per customer. Each customer has different default
values for their set of widgets which are rarely overridden, and I'd like
to minimize the typing necessary when someone adds a new widget to a
customer'
using PE 2016.1.2 (4.4.2)
On Thursday, July 7, 2016 at 11:15:19 AM UTC-4, mike r wrote:
>
> Hi all, Im writing a module that serves a shell script located in
> $basemodulepath/module/files/script.sh
>
> I recently had to update the shell script, but my agents are receiving the
> old version of
Hi all, Im writing a module that serves a shell script located in
$basemodulepath/module/files/script.sh
I recently had to update the shell script, but my agents are receiving the
old version of the script.
I checked the node's /opt/puppetlabs/puppet/cache but its not cached there.
Cant find
# netstat -ntap | grep 8140
... will show what (if anything) is listening on port 8140.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr..
11 matches
Mail list logo
