Skip to content
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.

Make vault-upgrade-hook compatible to AEMaaCS #45

Open
ghenzler opened this issue Mar 3, 2020 · 3 comments
Open

Make vault-upgrade-hook compatible to AEMaaCS #45

ghenzler opened this issue Mar 3, 2020 · 3 comments

Comments

@ghenzler
Copy link
Member

ghenzler commented Mar 3, 2020

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 Netcentric/accesscontroltool#405 does)

@kwin
Copy link
Member

kwin commented Jun 3, 2020

Which event is not working? We are talking here about mutable parts of the repository which are touched/upgraded/migrated only once. Obviously this package should be installed only when the right content is mounted in the AEM instance.

@tommix1987
Copy link

Correct me if Im wrong but basically if we deploy this alongside a package containing mutable content we should be good to run groovies on mutable content just fine (obviously you should not try to modify /apps with a groovy script)

@kwin
Copy link
Member

kwin commented Feb 10, 2021

@tommix1987 The problem is that install hooks on mutable content packages are not supported (details in https://github.com/Netcentric/aem-cloud-validator#prevent-using-install-hooks-in-mutable-content-packages). Also the Groovy Console is currently not compatible with AEMaaCS either (CID15/aem-groovy-console#1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants