is resolved by #30

@royteeuwen Thanks for the PR. Do you know if install hooks in mutable packages work meanwhile in Cloud Manager as well? Adobe recently updated FileVault to a newer version so potentially they have fixed this...

I just checked the OSGi configuration of an AEM Cloud instance version 2023.4.11873.20230421T153841Z and it still doesn't contain the necessary OSGi config for PID org.apache.jackrabbit.vault.packaging.impl.PackagingImpl to grant the sling-distribution-importer the rights to execute install hooks, unfortunately.

But as the configuration PID org.apache.jackrabbit.vault.packaging.impl.PackagingImpl is not listed as protected (https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/docs/api-regions.md#configurations) in https://repo1.maven.org/maven2/com/adobe/aem/aem-sdk-api/2023.4.11873.20230421T153841Z-230200/aem-sdk-api-2023.4.11873.20230421T153841Z-230200-aem-publish-sdk.slingosgifeature it is possible to allow hooks with a custom OSGi configuration extending the default one:

"org.apache.jackrabbit.vault.packaging.impl.PackagingImpl":    {
    "overwritePrimaryTypesOfFolders":"false",
    "isStrict":"false",
    "defaultIdConflictPolicy":"LEGACY"
  },

with the following option

"org.apache.jackrabbit.vault.packaging.impl.PackagingImpl":    {
   "authIdsForHookExecution":[
     "sling-distribution-importer"
   ]
},

@kwin ok, good to know! Nowadays we just use the startuphooks for cloud, dont know if it covers all cases though.

what do you recommend for this PR? I can update the readme with the osgi conf you show, or we can create support cases to request the osgi conf ;)?

I will take care of both :-) and go ahead with your PR as is first.