On Tuesday, December 16, 2014 7:59:00 AM UTC-6, Abhijeet Rastogi wrote:
[...]
class profile::base {
> anchor { 'base_repos_start': }
> class { '::yum::repo::epel': require => Anchor['base_repos_start']}
> class { '::yum::repo::puppet': require => Anchor['base_repos_start']}
> anchor
Hi John,
Thanks for replying. I tried using contain.
class profile::base {
contain '::yum::repo::epel'
contain '::yum::repo::puppet'
}
Still didn't work for me. Is there a possibility of known bug being
triggered?
On Wed, Dec 17, 2014 at 7:41 PM, jcbollinger
wrote:
>
>
>
> On Tuesday, Dece
Martijn,
Sorry for the delay ... but yes, in the future we don't mind sharing
this 'cert-api' code. Unfortunately today its not in a terribly share-able
state. It was quite literally my 2nd python-program ever, written 3+ years
ago, and written in a short-term hacky way because we naively believ
Hi! I'm taking over someone's code and have found the following class
signature - it's been abbreviated considerably; over 46 vars get used!!:
class showapp (
$amqp_host,
$amqp_password,
$amqp_port,
$amqp_user,
.
.
.
$queue_service_host,
$queue_service_port,
$redis_host,
$redis_p
Guy,
The example you have like..
class showap(
$amqp_host,
.
)
Pattern is a "parameterized class" pattern.
it's so you could have a site/node.pp or an ENC provide the
parameters/values.
node yourserver {
class { 'showap' : amqp_host => 'TRUE'}
}
or if you wish, hiera will do
So I can't use a hash? I'm trying to make a general use parameterized
class using a profile . . . Can I do something like this so I only have to
pass in the service name that I want to configure from my node definition:
class profiles::dropwizard (
$dw_service = 'dw_service_UNDEFINED',
$amqp
Working now! If I quote the hiera call I can get dynamic lookups:
class profiles::dropwizard (
$dw_service = 'dw_service_UNDEFINED',
$amqp_host = hiera("${dw_service}::amqp_host")
)
Thanks!
On Wed, Dec 17, 2014 at 4:48 PM, Guy Matz wrote:
>
> So I can't use a hash? I'm trying to make a gen
We're pleased to announce that Puppet Server 1.0.0 is now available.
This release is the official "one point oh" version of Puppet Server. In
accordance with the [Semantic Versioning](http://semver.org) specification,
we're declaring the existing public API of this version to be the
baseline for b
Hello All
I could successfully declare and realize virtual users in PE 3.2.3. I am
now testing the same with PE 3.7.0. Unfortunately the user is not being
realized and I am getting no warnings/errors.
I am pasting a snippet of my module manifests :
/etc/puppetlabs/puppet/modules/users/manifest
I am using CentOS 6.6 x86_64
uname -a
Linux puppet.xor.in 2.6.32-504.1.3.el6.x86_64 #1 SMP Tue Nov 11 17:57:25
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
On Thursday, 18 December 2014 13:16:44 UTC+5:30, Varun Utagikar wrote:
>
> Hello All
>
> I could successfully declare and realize virtual users i
10 matches
Mail list logo