We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Mutable content packages are deployed to publish via replication from author in AEMaaCS. In case they contain an install hook the replication fails, as the replication-receiver system user does neither have admin privileges and nor is configured as allowed user for install hooks (compare with https://issues.apache.org/jira/browse/JCRVLT-427). This limitation is currently not documented at https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/build-and-deployment.html?lang=en#debugging but having a mutable package with an install hook leads to a failed deployment.
The text was updated successfully, but these errors were encountered:
Add rule to prevent mutable content packages containing install hooks
6b294fb
This closes #3
906acf7
dd1fb70
986bace
Add rule to prevent mutable content packages containing install hooks (…
6af8a18
…#4) This closes #3
Successfully merging a pull request may close this issue.
Mutable content packages are deployed to publish via replication from author in AEMaaCS.
In case they contain an install hook the replication fails, as the replication-receiver system user does neither have admin privileges and nor is configured as allowed user for install hooks (compare with https://issues.apache.org/jira/browse/JCRVLT-427). This limitation is currently not documented at https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/build-and-deployment.html?lang=en#debugging but having a mutable package with an install hook leads to a failed deployment.
The text was updated successfully, but these errors were encountered: