Package Deployment overwrites changes from old deployment. | Community
Skip to main content
H
hemantsav
Level 2
July 5, 2023

Package Deployment overwrites changes from old deployment.

  • July 5, 2023
  • 3 replies
  • 1899 views

Hello Team,

Few days back we had an AEM release; after installing all packages (specifically ui-content) we found that it overwrote the last release changes.

We do have a merge filter added in vault folder.

 

We only changed the package versioning , previously it was like company-site-external.all-2.4.30.zip  and now its company-site-external.all-release_2023.1.0___4.zip.

 

It works perfectly fine on lower environment however it fails on prod environment.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
July 5, 2023

@hemantsav is it on-prem, AMS or AEM Cloud?

If on-prem or AMS, How are you deploying packages in lower environment? Via cloud manager or Any other deployment tool? In that case need to check package version snapshot vs major vs minor release numbers.

 

If all the above good, whats really getting override,  ui.content? Can you post your filter.xml? 

    H
    hemantsavAuthor
    Level 2
    July 5, 2023

    It's on-prem.

    On lower environments we are deploying via CI/CD using AEM API for deployment.

    While in PROD we did manual deployment.

    "whats really getting override ? " ==> we have one folder (has html under it) under content as  content/company-site-external/us/en/articles/5787280/5787280.html ; after new release package installation folders those are created after our last release (in Feb 2023) got deleted. Other child folders (created prior to Feb 2023 release) are there without any issues.

    Content that is published under content/company-site-external/us/en/articles are created dynamically and uploaded to AEM dynamically .i.e we create a AEM package with html into it, upload it to Author using API , then install it via API then trigger the replication to get it to other publisher instances.

    Content of filter.xml in content package's vault folder

    <?xml version="1.0" encoding="UTF-8"?>
<workspaceFilter version="1.0">
    <filter root="/conf/company-site-external" mode="merge"/>
    <filter root="/content/company-site-external" mode="merge"/>
</workspaceFilter>

     

    After this issue I realised my new versioning is not semver ; Could that be issue? Because we haven't change anything in config except versioning.

     

     

      Sudheer_Sundalam
      Community Advisor
      Sudheer_SundalamCommunity Advisor
      Community Advisor
      July 5, 2023

      @hemantsav 

      Unzip the ui.content package that was last installed and check the filter.xml file and the mode option, if specified. The filter mode if specified as "merge" for all the filter path definitions, should by definition, should only add the new nodes from the ui.content package and shouldn't update the existing nodes.

      Also, check the source of the ui.content package itself.

        aanchal-sikka
        Community Advisor
        aanchal-sikkaCommunity Advisor
        Community Advisor
        July 6, 2023

        Hello @hemantsav 

         

        The versioning should not have caused issues, as you have changed the name of the package also.

         

        I would suggest taking a backup on local and try deploying the release package.

         

        Mode=merge shouldn't have modified anything. Also, can you please post what specifically has changed?

         

        If it possible that you have similar filters in some other module as well? 

        Aanchal Sikka
          H
          hemantsavAuthor
          Level 2
          July 6, 2023

          "can you please post what specifically has changed?" ==> we have one folder (has html under it) under content as  content/company-site-external/us/en/articles/5787280/5787280.html ; after new release package installation folders those are created after our last release (in Feb 2023) got deleted. Other child folders (created prior to Feb 2023 release) are there without any issues.

          Content that is published under content/company-site-external/us/en/articles is created dynamically and uploaded to AEM dynamically .i.e we create a AEM package with html into it, upload it to Author using API , then install it via API then trigger the replication to get it to other publisher instances.

          Content of filter.xml in content package's vault folder

          <?xml version="1.0" encoding="UTF-8"?>
<workspaceFilter version="1.0">
    <filter root="/conf/company-site-external" mode="merge"/>
    <filter root="/content/company-site-external" mode="merge"/>
</workspaceFilter>

           

            Tanika02
            Tanika02
            Level 7
            July 6, 2023

            Hello @hemantsav - 

             

            The issue seems to be related to the deletion of folders that were created after the last release in the content/company-site-external/us/en/articles path. Here are a few steps to investigate further:

             

            • Review the contents of the release package (company-site-external.all-release_2023.1.0___4.zip) to ensure that the folders and content you expect to be included are present. Verify that the package includes the HTML file and all the necessary child folders.
            • Confirm that the release package is installed after any other dependent packages or content that should be merged together. The installation order can impact the merging behavior and determine which content takes precedence during the merge process.
            • Since the content under content/company-site-external/us/en/articles is dynamically created and uploaded using the AEM API, check the logic and code responsible for this process. Ensure that it is correctly handling the creation and update of content, and that it does not inadvertently delete or overwrite existing content during the upload and installation process.
            • Verify the replication process that transfers the content from the author to the publisher instances. Confirm that the replication configuration is correctly set up and that it replicates the dynamically created content to the other publisher instances as expected.
            • Check the AEM audit logs to identify any actions or events that might have triggered the deletion of the folders. The audit logs can provide insights into who performed the action and what might have caused the deletion. (You can also try ruling out the possibility of manual deletion..maybe !?)
            • Examine the AEM logs for any relevant error messages or warnings during the package installation, content upload, and replication processes. (Can you share those logs?)
              Terms & ConditionsAccessibility statement

              Loading footer...