Hello, I found out a small issue with Coral UI Select Field and I would like to share with you in case you will find yourself in a similar situation   In my project there is a custom select field used on Asset Metadata schema which builds the Coral Select using JS API. One of the requirements was t...

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...

Hi, I am investigating ways of working for new AEM as a Cloud Service. One of the common features used in AEM projects was Crypo support that allowed to encrypt any secret as password, API key and keep it in the repository in OSGI config. Usually we shared one crypto key pair for our test envs and t...

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> ...

Hi, I am trying to use vault upgrade hook with plain groovy (not groovy console) to work with latest AEM as a Cloud Service instance (local setup, I know that this will not work on AMS isntance at the moment due to issue with FileVault, for more see this link) As I read to do so I need to install Ap...

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> ...