Christopher Warrington

My feedback

  1. 120 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Christopher Warrington supported this idea  · 
  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
  3. 820 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Storage » Blobs  ·  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 azurestoragefeedback@microsoft.com.

    Christopher Warrington commented  · 

    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.

    Christopher Warrington supported this idea  · 
  4. 1,284 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    38 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    Christopher Warrington supported this idea  · 
    Christopher Warrington commented  · 

    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.

  5. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Christopher Warrington supported this idea  · 
  6. 13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Container Registry  ·  Flag idea as inappropriate…  ·  Admin →
    Christopher Warrington supported this idea  · 
  7. 103 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Container Registry  ·  Flag idea as inappropriate…  ·  Admin →
    Christopher Warrington commented  · 

    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.

    Christopher Warrington supported this idea  · 

Feedback and Knowledge Base