fo...@cfengine.com writes:
>> body common control
>> {
>> bundlesequence => { "base", @(test.bundles) };
>> inputs => {"test.cf", @(test.inputs) };
>> }
>
> I don't see how this can work. There are no variables defined until
> inputs is processes. Variable resolution in bundlesequence seems delayed until the information is available, I thought I could be the same for inputs, loading non variable first and using variable when they are finally defined... > Inputs cannot be processes until the given variable is defined. You > might try defining a common bundle in promises.cf that you can draw > variables from. My idea was to avoid editing promises.cf as much as possible, maybe speaking about some sort of delegation. The DBA rules a services/rdbms/ tree with some version control system, services/main.cf promise to load everything under services/ (class based) and the "sub promises" do what they needs, including adding bundles to bundlesequence and files to inputs. I use this with cf2 and its import, maybe this hierarchical management is the wrong way? Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1
pgpeyqXUJCr22.pgp
Description: PGP signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
