Hello,
I have tried and it was working, extend the pp as per your requirements.
I haven't set any metaparameter. please add as per your requirements.
Let me know if you find any difficulty.
# Testing
class locate {
Exec { path = /usr/bin:/usr/sbin:/bin:/sbin }
exec { replace :
as explained here:
http://docs.puppetlabs.com/puppet/latest/reference/lang_defined_types.html#title-and-name
resource *title* is guaranteed to be unique for each instance.
I thought that resource *name* was not required to be unique.
however this code suggests the opposite:
my_resource { r1:
The resource title and namevar must be unique for any resource as
documented here...
http://docs.puppetlabs.com/puppet/latest/reference/lang_resources.html#uniqueness
Defined resource types follow the same rules and the $name variable is
always assumed to be a namevar.
Craig
On Mon, Mar 31,
On Sunday, March 30, 2014 11:24:30 PM UTC-5, Atom Powers wrote:
Over the years I've heard a lot of people declare one
function/method/implementation of something to be evil. I've found that,
more often than not, the person declaring it to be bad has simply been
burned by trying to use it
On Friday, March 28, 2014 3:48:47 PM UTC-4, jcbollinger wrote:
Puppet DSL provides no mechanism, however, for selecting resources via a
search expression without realizing all virtual resources among those
selected.
This is really awkward for what I see as a natural operation. Am I doing
On Saturday, March 29, 2014 8:48:26 AM UTC-5, Vishwa Kumba wrote:
I was wondering if there is a way to define ordering between 2
create_resources in puppet manifests.
For example:
create_resources('php::install', $php_packages) -
create_resources('webapps::deploy', $apps)
The above
great, thanks!
On Monday, March 31, 2014 4:00:30 PM UTC+2, Craig Dunn wrote:
The resource title and namevar must be unique for any resource as
documented here...
http://docs.puppetlabs.com/puppet/latest/reference/lang_resources.html#uniqueness
Defined resource types follow the same
On Mon, Mar 31, 2014 at 10:09 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
This is really awkward for what I see as a natural operation. Am I doing
something wrong in my setup?
And also... this is funny, but I discovered a change including this syntax
had already been rolled out into
I disagree that ensure_resource is evil and should not be used. It is
however, potentially problematic, and it's issues are worth discussing. It
was written (full disclosure by me) as an improvement over defined(). While
it is not perfect (it suffers from parse-order issues), it is intended as
an
I ran into the same issue this weekend, and discovered that the Amazon yum
repo's latest Puppet package (2.7.25) has ruby1.8 shebang'd. With that
puppet release, you can have ruby2.0 on the system as the default and still
have puppet running correctly. If your hosts are running the puppet
On 2014-31-03 20:08, Dan Bode wrote:
I disagree that ensure_resource is evil and should not be used. It is
however, potentially problematic, and it's issues are worth discussing.
It was written (full disclosure by me) as an improvement over defined().
While it is not perfect (it suffers from
Not yet released. Entered RC3 on March 31, 2014. (RC1: March 14. RC2: March
24.) RC3 fixed a regression in the RPM package provider that prevented managing
architecture-specific packages (PUP-2039). RC2 included a fix for the manifest
setting not allowing certain directories as its value
12 matches
Mail list logo
