Great article, thanks ! Is this package available publicly now ?    

Hello @maryw24753203 any updates here ? 

I found another documentation that states that on envs managed via Cloud Manager a special env-related variables can be used for secrets and regular configurations like. { "connection.timeout": 1000, "api-key": "$[secret:server-api-key]", "url": "$[env:server-url]" } So I far as I understand this is...

Hi @krishna_chaita2, thanks for the answer but I am still not sure how this should be handled on AEM as a Cloud environment.  I can configure the key locally and then encrypt secrets using /system/console/crypto on my local instance and resuse this key pair on all development instances that we creat...

Also using groovy-all package can help here, then issue with groovy-json is not showing. The only problem is to find proper version

I found a blog post https://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html that addresses the issue I had below. To fix that I added the following bundles to the instance:   <!-- Dependencies needed to run Vault upgrade hook with plain groovy --> <dependency> ...

Thanks for your response. How did you install groovy console on author ? Did you use filevault-package-maven-plugin for that with groovy all package (see snippet below)?  <embedded> <groupId>org.cid15.aem.groovy.console</groupId> ...

Hi @velmuruganv38, have you raised that issue ? was it resolved ?