You got it. Note that the arrow operators do exactly the same thing as the
before and require metaparameters so you could have add one of those to one
of the resources. Personally when a manifest has resources that are more
serial or scripty I prefer the obvious expression adding a chain of ->'d
re
>
> As simple as that? Great. I tried it and the reload did run after the
> add, but I can't see from the logs that the reload has the add as
> dependency.
>
> With your suggested change:
>
> Debug:
> /Stage[main]/Main/Node[default]/Zendserver::Vhost[vhost1test91]/Zendserver::Vhost::Add[vhost
On Thursday, June 1, 2017 at 11:39:26 PM UTC-4, Matthew Kennedy wrote:
>
> Because puppet is declarative you can only have one instance of a resource
> with a particular title in the catalog. This means you cannot have two
> instances of a class in the catalog (though you can include a class
>
On Thursday, June 1, 2017 at 6:08:01 PM UTC-4, Pete Brown wrote:
>
> The require meta parameter will do that.
>
Ok, but how to formulate it with the variables?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and
Because puppet is declarative you can only have one instance of a resource
with a particular title in the catalog. This means you cannot have two
instances of a class in the catalog (though you can include a class
multiple times but it only exists in the catalog once)
Luckily you do not have two i
The require meta parameter will do that.
On Thu, 1 Jun 2017 at 14:08, Ugo Bellavance wrote:
> Hi,
>
> I would need to execute a command after the execution of another and I
> didn't find anything on the web regarding this. Here's the code:
>
> if $vhost_name_fact != undef {
>
> } else {
>
Hi,
I would need to execute a command after the execution of another and I
didn't find anything on the web regarding this. Here's the code:
if $vhost_name_fact != undef {
} else {
zendserver::sdk::command { "vhost_add_${vhostname}_${port}":
target => $target,
ap
