120 votes18 comments · Azure Active Directory » Developer Experiences · Flag idea as inappropriate… · Admin →
Our apologies for not updating this ask earlier. Renaming Blobs is on our backlog, but is unlikely to be released in the coming year. Today, you can use the “Copy Blob” API as a workaround.
Using the Azure Files service you can address Azure Storage like a network share using the SMB2.1 protocol. This enables usage of normal Windows API’s to rename files and directories. You can get started with the Files service by visiting https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-how-to-use-files.
For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
I would like to be able to rename blobs so I can have them in a different namespace while they are being created/uploaded to. Then, after they are finalized, they can be renamed to their "published" location. Couple this with per-blob expiration and implement atomic rename-and-reset-TTL, then blob upload error recovery becomes trivial: start uploading to a temporary blob with a short TTL, when done, rename-and-reset-TTL to the final name. If anything goes wrong, the partial blob will just go away automatically.
Thank you for your feedback. We are currently in public preview of blob storage lifecycle management. The feature set offers a rich, rule-based policy engine which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle. See our post on the Azure Blog to get started: https://azure.microsoft.com/en-us/blog/azure-blob-storage-lifecycle-management-public-preview/preview/.
For any further questions, or to discuss your specific scenario, send us an email at DLMFeedback@microsoft.com.
The storage lifecycle management preview is fine, but doesn't address the issue I have. I want to be able to create a blob and set it to expire in, say, 3 hours. When 3 hours have elapsed, the blob should be deleted (perhaps subject to the container's soft delete policy). If I create a different blob, I want to set the expiration to say 15 minutes. I also want to be able to extend and shrink a blob's TTL after it has been created. The once-a-day, policy based approach doesn't let me do this any of this.
Thank you for your suggestion.
At this time this feature is not on our road map. We will leave this marked as unplanned for now and will revisit this in upcoming cycles and will update here if this changes.
Thank you for your suggestion and votes.
We’ve started the design, and would welcome any additional feedback.
We’ve started the Auto-Purge work, with this current design: https://github.com/AzureCR/specs/tree/master/auto-purge
Please provide feedback here: https://github.com/AzureCR/specs/issues/1
It would be awesome if this were also integrated with VSTS's Docker Container build/push tasks, so that when it deletes a build, it also deletes the images pushed.