Allow to reuse variables from other YAML files

[kwin]

Currently the functional logic (loops, variables, ...) only work on a per YAML-file basis. It is not possible to declare variables once in one YAML file and use it then in multiple others. This is often desirable though for more complex setups.

Currently the code in

accesscontroltool/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/configreader/YamlMacroProcessorImpl.java

Line 59 in 65f4dfd

return transform(o, new HashMap<String, Object>(), installLog, session);

leads to the fact that for each YAML file the variables map is being empty.

In addition one would need to clarify the order in which YAML files are processed (depth first vs. breadth first or all in alphabetical order).

[otarsko]

How about importing other yaml files and introducing new configuration section "import_config"? E.g.:

- import_config:

  - imports:
      
      - name: groupNames
        path: groupNames.yaml

      - name: userNames
        path: ../folderA/userNames.yaml

On evaluation, we export variables definitions into the parent scope (so the yaml file these imports are defined in), and then make them accessible as ${userNames.userA}.

It looks like a big change though.

[ghenzler]

@otarsko So I tried a few things back and forth - the issue with importing a yaml file is that normally all yaml files are taken into account (so you would import it and you would have to exclude it from "normal operations"). Please have a look at https://github.com/Netcentric/accesscontroltool/blob/cf858eec512f01dc408e993647b7d575f297ad47/docs/AdvancedFeatures.md#global-variables if that works for you - together with the multiline syntax of https://github.com/Netcentric/accesscontroltool/blob/cf858eec512f01dc408e993647b7d575f297ad47/docs/AdvancedFeatures.md#variables this should really allow for anything that is needed