Not strictly true. There is no reason why common bundles should not be
included in the bundlesequence. Indeed, it increases the chances of
variables being expanded with multiple indirection. If any reports are
made in common bundles these will only be executed if the bundles are in
the sequence.
The reason why it is not usually *necessary* to put them there is that
Cfengine needs to sneak-peek through all bundles to converge class/var
circular dependencies, so you get a lot of variables and classes defined
by "discovery".
M
On 03/08/2011 09:38 PM, Seva Gluschenko wrote:
> That was false advice. Common bundles aren't included into the
> bundlesequence. What it meant to be done is to declare a local slist
> inside the target bundle as follows:
>
> bundle agent foo
> {
> vars:
> "user_name" slist => { @(g.user_name) };
>
> ...
> }
>
> 2011/3/7 Mikhail Gusarov <mikhail.gusa...@cfengine.com>:
>> On 07.03.2011 00:58, Jones, Stephen (MAS) wrote:
>>
>>> bundle common g {
>>
>> Have you got this bundle added to the bundlesequence before the bundle
>> that contains aforementioned commands promise?
>>
>> --
>> Mikhail Gusarov
>> _______________________________________________
>> Help-cfengine mailing list
>> Help-cfengine@cfengine.org
>> https://cfengine.org/mailman/listinfo/help-cfengine
>>
>
>
>
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
