Christopher, Felix, I got the idea. Thank you very much!
--
Best regards,
Sergey Arlashin
On Jun 18, 2014, at 7:04 PM, Felix Frank
wrote:
> Wow, Christopher gave an exhaustive answer :-)
>
> I'll try and Keep It Simple.
>
> On 06/18/2014 04:22 PM, Sergey Arlashin wrote:
>> I do need to ha
Wow, Christopher gave an exhaustive answer :-)
I'll try and Keep It Simple.
On 06/18/2014 04:22 PM, Sergey Arlashin wrote:
> I do need to have 2 separate modules. I need the class 'testmode' to run
> before class 'test mod::nginxtest'. And I need to restart service 'nginx'
> when I change '/tmp
Also see these for interesting ideas:
http://www.craigdunn.org/2012/05/239/
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/
In your place, this is how I would arrange what you want, because I often cram
configs togeth
Hm, ok.
But when I use 'subscribe' instead of 'notify'
class testmod {
package { 'nginx': ensure => installed }
service { 'nginx':
ensure=> running,
enable=> true,
require => Package['nginx'],
subscribe => File['/tmp/nginx.test']
}
}
class testmod::nginxtest {
Hi,
On 06/18/2014 03:51 PM, Sergey Arlashin wrote:
> Could you please help me figure out why this is happening ? It seems there is
> nothing in test mod whih requires testmod::nginxtest .
actually yes, there is.
file { '/tmp/nginx.test':
ensure => present,
notify => Service['nginx'];
Hi,
I have a weird dependency cycle issue. This is just a test module which I
created while trying to solve this issue:
modules/testmod/manifests/init.pp:
class testmod {
package { 'nginx': ensure => installed }
service { 'nginx':
ensure => running,
enable => true,
require =
