Today, when a lifecycle policy removes an artifact version from a registry, the only option is deletion. We'd like the ability to optionally configure a registry with a "cold storage" destination, a customer-managed cloud storage target (e.g., S3 Glacier or equivalent), so that instead of deleting the artifact when a lifecycle policy triggers, Harness moves it there. Goal is to preserve older artifact versions (for various reasons) without keeping them in the primary registry (which is priced/optimized for active use)

Key points:

• Cold storage is opt-in per registry; default behavior (delete) is unchanged if not configured

• Admins would provide the cloud storage account/bucket and credentials to upload to, but the "connection" would be managed within Harness settings.

• Multiple registries could optionally share the same cold storage destination for consolidation.