[
https://issues.apache.org/jira/browse/CAMEL-23341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-23341:
--------------------------------
Fix Version/s: (was: 4.20.0)
> camel-azure-storage-blob - Add support for changing access tier of existing
> blobs
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-23341
> URL: https://issues.apache.org/jira/browse/CAMEL-23341
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.21.0
>
>
> The camel-azure-storage-blob component supports setting the AccessTier (Hot,
> Cool, Archive) during blob upload, but does not support changing the tier of
> an already-existing blob.
> Changing the access tier of existing blobs is a common requirement for
> lifecycle management and cost optimization, allowing users to move blobs
> between Hot, Cool, and Archive tiers based on access patterns.
> The Azure SDK provides BlobClient.setAccessTier() and
> BlobClient.setAccessTierWithResponse() but these are not exposed as a
> standalone operation in the Camel component.
> Proposed new operation:
> - setBlobTier
> The operation should accept the target AccessTier, optional RehydratePriority
> (for rehydrating from Archive), and return appropriate response headers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
