Could someone please confirm if, as of October 25, 2024, it is possible to override the default version purge configuration in AEM as a Cloud Service? The documentation suggests a future configuration option (in mt.yaml) to override this setting—is that correct?
Currently, it seems that versions are retained for seven years with no limit on the number of versions until a future update is released. Is this accurate?
Views
Replies
Total Likes
Hi @kartheekd203042 ,
Version purge is currently disabled by default, but the policy can be configured.
AEM is shipped with various mechanisms to help you manage your repository. The Version Manager
This can be configured to purge old versions when new versions are create. Second one is Purge Version tool . This is used as part of monitoring and maintaining your repository. It lets you intervene to remove old versions of a node, or a hierarchy of nodes.
You can follow below link for more details:
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/conf...
-Tarun
Thanks, @TarunKumar, for the response! I'm specifically looking for details about AEM as a Cloud Service. The links you shared cover AEM 6.5, but for AEM as a Cloud Service, we’d handle this through the config pipeline, correct? And this configuration would apply in future releases, not currently?
Views
Replies
Total Likes
Hi @kartheekd203042 ,
You can try to configure.
Seems as per https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/maint... the purging feature is currently not enabled by default, but it can be configured now. In the future, this feature will become the default setting for new environments.
So, for now, you can set it up manually, but soon it will be automatically applied to new environments without needing configuration.
Thanks
Views
Replies
Total Likes
Hi @MukeshYadav_ @TarunKumar ,
Steps followed are outlined below:
Create a MaintenanceTask.yaml (or any preferred name) file as specified in the Adobe documentation, including all properties for both version and audit purge configuration.
Place this file in the top-level config folder of the codebase.
Create a configuration pipeline, selecting the file from this top-level folder location.
Create a granite_weekly/granite_daily config in the code based on custom requirements.
Create an Ad Hoc Purge Task under the weekly/daily config node (is this required?).
Deploy the code using the deployment pipeline to the cloud instance.
Trigger the config pipeline after the deployment.
Wait for the time in UTC as configured in the granite_weekly/granite_daily configuration.
We haven't observed versions being cleaned up and are wondering if a step or configuration might be missing.
Please let me know if you have any suggestions on this.
Config file values below:
kind: "MaintenanceTasks"
version: "1"
metadata:
envTypes: ["dev"]
data:
versionPurge:
maximumVersions: 5
maximumAgeDays: 0
paths: ["/content"]
minimumVersions: 1
retainLabelledVersions: false
auditLogPurge:
rules:
- replication:
maximumAgeDays: 15
contentPath: "/content"
types: ["Activate", "Deactivate", "Delete", "Test", "Reverse", "Internal Poll"]
- pages:
maximumAgeDays: 15
contentPath: "/content"
types: ["PageCreated", "PageModified", "PageMoved", "PageDeleted", "VersionCreated", "PageRestored", "PageValid", "PageInvalid"]
- dam:
maximumAgeDays: 15
contentPath: "/content"
types: ["ASSET_EXPIRING", "METADATA_UPDATED", "ASSET_EXPIRED", "ASSET_REMOVED", "RESTORED", "ASSET_MOVED", "ASSET_VIEWED", "PROJECT_VIEWED", "PUBLISHED_EXTERNAL", "COLLECTION_VIEWED", "VERSIONED", "ADDED_COMMENT", "RENDITION_UPDATED", "ACCEPTED", "DOWNLOADED", "SUBASSET_UPDATED", "SUBASSET_REMOVED", "ASSET_CREATED", "ASSET_SHARED", "RENDITION_REMOVED", "ASSET_PUBLISHED", "ORIGINAL_UPDATED", "RENDITION_DOWNLOADED", "REJECTED"]
Hi all
Any inputs on this as we are still not able to control the time/day of version purging following these steps.
Any one using this currently in their projects?
Views
Replies
Total Likes
@kartheekd203042 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Hi @kautuk_sahni - Thanks for following up
I am still requiring details on my question as outlined above.
Views
Replies
Total Likes
Hi @kartheekd203042, from the configuration shared above, I can see "maximumAgeDays: 0". Please note: If the value is 0, purging is not performed based on the age of the version.
Views
Replies
Total Likes
Views
Likes
Replies