Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

Unable to see the changes in RDE Environment

Avatar

Level 5

I am trying to push changes in yaml file for AC Tool from git repo to aem rde instance.

the build is stable and compiling on local successfully.

 

the changes in yaml are reflecting fine on local.

when i use the aio:aem:install to push all module's target zip it is uploading correctly.

 

in packmgr at rde one can see the installation with the correct time but the changes in yaml are not promoted to the cloud instance.

 

why would this behave this way?

filter rules are correct - target package is building correctly - its deploying on cloud but changes are not there.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Please send the build logs too.

Also once reconfigure the AEM plugin for RDE by using the below commands -

$ aio config:set cloudmanager_orgid <org-id>

$ aio config:set cloudmanager_programid <program-id>

$ aio config:set cloudmanager_environmentid <env-id>

 

You can verify the current config values by running the following command.

$ aio config:list

View solution in original post

12 Replies

Avatar

Community Advisor

Hi @aem_noob 

Check your pom.xml file 

Under VAULT PACKAGE PLUGINS section's filevault-package-maven-plugin 

accessControlHandling

 

 

Thanks

Himanshu 

Himanshu Jain

Avatar

Level 5

The optional parameter for <accessControlHandling> is not defined

should i add merge_preserve to it?

Avatar

Community Advisor

Try pushing only the ui.apps target artifact once to see if the changes are being reflected.

If yes then you might want to look at all module's pom.xml

If not, then try unzipping the target and see if your changes are there.

Avatar

Level 5

deploying ui.apps is also not working, when i look at the target zip file it doesn't have the changes!

Avatar

Community Advisor

Then the issue is not with RDE or using AIO CLI to push changes to RDE.

Can you send the pom.xml for ui.apps once?

As @Himanshu_Jain has suggested, you want to look at the

filevault-package-maven-plugin

This plugin should have the below dependency -  

<!-- Netcentric ACL Tool -->
<dependency>
<groupId>biz.netcentric.cq.tools.accesscontroltool</groupId>
<artifactId>accesscontroltool-package</artifactId>
<classifier>cloud</classifier>
<type>content-package</type>
<scope>provided</scope>
</dependency>
<!--Oak Index for Netcentric ACL Tool -->
<dependency>
<groupId>biz.netcentric.cq.tools.accesscontroltool</groupId>
<artifactId>accesscontroltool-oakindex-package</artifactId>
<classifier>cloud</classifier>
<type>zip</type>
</dependency>

Avatar

Level 5

I have already declared this dependency in the pom.xml for ui.apps

Avatar

Community Advisor

Please send the build logs and pom.xml once.
We will review it once.

Avatar

Community Advisor

Hi @aem_noob ,

Check your parent pom.xml file whether all your modules included in it or not?

 

Thanks

Himanshu

Himanshu Jain

Avatar

Level 5

yes, here is parent pom

<modules>
<module>all</module>
<module>core</module>
<module>ui.apps</module>
<module>ui.apps.structure</module>
<module>ui.config</module>
<module>ui.content</module>
<module>it.tests</module>
<module>dispatcher</module>
<module>ui.tests</module>
</modules>

Avatar

Correct answer by
Community Advisor

Please send the build logs too.

Also once reconfigure the AEM plugin for RDE by using the below commands -

$ aio config:set cloudmanager_orgid <org-id>

$ aio config:set cloudmanager_programid <program-id>

$ aio config:set cloudmanager_environmentid <env-id>

 

You can verify the current config values by running the following command.

$ aio config:list

Avatar

Community Advisor

I am not exactly sure why this would have happened.

It should not have pushed the packages in that case altogether.
Is it possible you are using multiple environments ? Can you check the other environments just to see if packages got promoted to another environment?

Ideally the combination of Org ID + Program ID + Env ID narrows down the instance uniquely.