Azurite doesn't support Set Blob Tier operation on lease blob and snapshot blob.

Error Description: In Azure, it will return error “BlobNotFound” when use Set Blob Tier operation with invalid leaseId or snapshot. But in Azurite, it will set blob tier successfully in this case. Azure error is shown as following:

To Reproduce

import {
  BlobServiceClient
} from "@azure/storage-blob";
import * as assert from "assert"


async function main() {
  const blobServiceClient = await BlobServiceClient.fromConnectionString("Azurite-https-connectionString");
  const containerClient = await blobServiceClient.getContainerClient("<container-name>");
  const blockBlobClient = await containerClient.getBlockBlobClient("<blob-name>");
  const fakeVersion = "2020-04-23T03:21:50.5338150Z";
  const snapshotBlobClient = blockBlobClient.withSnapshot(fakeVersion);
  try{
    await snapshotBlobClient.setAccessTier("Cool");
  }catch(err){
    console.log(err);
    assert.ok((err as any).response.parsedBody.Code === "BlobNotFound");
  }
}

main();

Error Track: The reason maybe is that the parameter leaseId and snapshot are not be processed in Blob Set Tier handler method in azurite. The code is shown as following: https://github.com/Azure/Azurite/blob/master/src/blob/handlers/BlobHandler.ts#L872

Expected Behavior When use Set Blob Tier operation with invalid leaseId or snapshot, it doesn’t set blob tier successfully and return the error “BlobNotFound”.

@jongio for notification.

[blueww]

@dennisdietrich Thanks for the information! We will priority the fix.

We welcome contribution to Azurite. It would be great if you could contribute the the fix of this issue.

[v-xuto]

azsdk-azurite