IMS Group does not exist during startup_hook_image_build step

[rmussabayev-lmru]

Hello,

Could you please help me with identifying the root of my issue? I have an external group (IMS) that actually exists in the JCR and I can see it via /crx/de. I'd like to use it as a member of the custom group I've defined via the yaml file, but I keep getting the following error during startup_hook_image_build step

ERROR: Could not process yaml files / e=biz.netcentric.cq.tools.actool.authorizableinstaller.AuthorizableCreatorException: java.lang.IllegalStateException: Member ims-brandbook-content-managers does not exist and cannot be added as external member to group brandbook-external-users

It looks like when startup_hook_image_build step is executed the IMS group hasn't been created yet. According to the logs, there were 171 memberships prefetched in startup_hook_image_build, but 287 memberships in startup_hook.

I have created a separate maven module for ACLs in the project and it depends on ui.apps and ui.content modules (both module and filevault-package-maven-plugin) and defined group membership as

• brandbook-external-users:

    - name: Brandbook external users (AEM group)
      memberOf: fragment-external-contentmanager
      members: ims-brandbook-content-managers
      path: global
  

Did I do something wrong?

[blair-robertson]

Do you get the same error when you apply the configuration via the Admin UI?
In this case the whole respository exists (because AEM as started) so there should not be any problem with immutable vs mutable content.