-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AEMaaCS: Startup Hook executed too early for ACLs on mutable content #545
Comments
It turned out that in our case we had an issue with the Startup Hook being executed during the Docker build because we relied on Cloud Manager Environment variables for a service user key which were not accessible during the Docker build.
The problem is that failures in the Startup Hook are not propagated back to the Cloud Manager, i.e. the according step will not fail. |
Probably the startup hook should implement This hook has been implemented in the context of SLING-5456 and is only available in AEM 6.3 or newer though. |
exceptions properly This closes #545 partially
exceptions properly This closes #545 partially
exceptions properly This closes #545 partially
Using the Install Hook instead of the Startup Hook does not work due to the issue outlined at Netcentric/aem-cloud-validator#3. |
exceptions properly This closes #545 partially
exceptions properly This closes #545 partially
Maybe one can leverage somehow https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/packaging/events/PackageEventListener.html to defer installation or trigger it again when mutable packages have been installed. Not sure how to distinguish regular mutable package installation via WebUI from the one triggered as part of the Cloud Manager Deployment, though. |
Hi, I am also facing that issue. Is there any plan to deliver a fix for that ? Is there any workaround ? Regards, Francis BONHEUR. |
Currently the Install Hook is disabled by default in AEMaaCS (
accesscontroltool/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/installhook/AcToolInstallHook.java
Line 80 in 48e1bfe
When the Startup Hook is executed during the Docker build (when first starting the instance) it works on top of the already set up immutable repo (being initialized with https://github.com/apache/sling-org-apache-sling-jcr-packageinit/blob/master/src/main/java/org/apache/sling/jcr/packageinit/impl/ExecutionPlanRepoInitializer.java). That works fine.
When the Startup Hook is executed while the new Kubernetes pod is starting, the mutable content packages are not yet installed (i.e. the content to which to apply the ACLs might not be there yet), so this execution might fail during the first deployment (but works then on subsequent ones).
The text was updated successfully, but these errors were encountered: