On Wed, Apr 27, 2011 at 2:47 PM, Nigel Kersten wrote:
>
>
> On Wed, Apr 27, 2011 at 3:40 PM, Stig Sandbeck Mathisen
> wrote:
>>
>> Martin Harrigan writes:
>>
>> > Hi all,
>> >
>> > Does a subscription result in an auto-requirement?
>>
>> A "subscribe" should imply a "require", although this is n
On Wed, Apr 27, 2011 at 3:40 PM, Stig Sandbeck Mathisen wrote:
> Martin Harrigan writes:
>
> > Hi all,
> >
> > Does a subscription result in an auto-requirement?
>
> A "subscribe" should imply a "require", although this is not explicitly
> stated at
> http://docs.puppetlabs.com/references/stable/
Martin Harrigan writes:
> Hi all,
>
> Does a subscription result in an auto-requirement?
A "subscribe" should imply a "require", although this is not explicitly
stated at
http://docs.puppetlabs.com/references/stable/metaparameter.html#subscribe
The answer is a firm "I think so". :)
--
Stig Sa
Hi all,
Does a subscription result in an auto-requirement?
For example, in the service below, is the require redundant?
package { 'PACKAGE':
ensure => latest
}
file { 'CONFIG-FILE':
...
require => Package['PACKAGE']
}
service { 'SERVICE':
...
subscribe => File['CONFIG_FILE'],
Hi,
I'd like to be able to use subscribe with exec to refresh when files change,
but I'd like each refresh to be dependent on another exec--e.g., to test
configuration syntax. The closest I've been able to come is what I have
below (I've removed some of the rest of the detail), but the problem is
