vault-upgrade-hook
vault-upgrade-hook copied to clipboard
Jackrabbit FileVault Install Hook to perform additional actions during package installation
As Groovy console was moved from [icfnext](https://github.com/icfnext/aem-groovy-console) to [CID15](https://github.com/CID15/aem-groovy-console) it might be useful to update the dependency to the current version [org.cid15.aem.groovy.console](https://mvnrepository.com/artifact/org.cid15.aem.groovy.console). Next release of the groovy console will hopefully...
Since the package install hook event is not working for this use case, a content marker will have to be used (similar to what the implementation in https://github.com/Netcentric/accesscontroltool/issues/405 does)
As the groovy console is relying on the OSGi installer to deploy the bundle the according service is only available after a certain delay. That makes it impossible to deploy...
It would be nice to pass properties from the hook to all contained scripts (e.g. to influence the root node from which to start). Otherwise this information has to be...
See https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp/index.html The API ControlledProcessManager can be used as follows to control it (groovy console example): ``` import com.adobe.acs.commons.mcp.ControlledProcessManager ControlledProcessManager cpm = getService(ControlledProcessManager.class) def processDef = cpm.findDefinitionByNameOrPath("Asset Report") println ("count...
As the package installation log is kind of transient, it should in addition be stored below `/var/upgrade` for post-mortem debugging.
When the package contains some conflicting changes (like nt:unstructured under nf:folder) so they can not be saved - then out status cannot be saved as well _Originally posted by @otarsko...
For groovy scripts we implemented a MD5 hash mechanism to detect changes in a file and decide when to re-run it. This functionality has yet to be implemented for Sling...