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. 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.I'm looking at the code and have a hard time to understand the difference in the processing of bundlesequence and inputs. Running cf-promises with debug give me this: If a variable, like @(test.bundles), appears in bundlesequence, its expansion is delayed, when test.cf is parsed, the expansion happens. So, according to my debug, with the body common control at the beginning, the bundle test is promised. I'm trying to understand the code to provide a patch to do the same with inputs but fail for now. The only difference I see for now is that inputs appears in cf3parse.y and not bundlesequence... Any hint to guide me a little? Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1
pgpVqaN9gloIr.pgp
Description: PGP signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
