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"]
