DylanBruzenak

We need this as well, or at least the ability to output variables from custom CDK code to the rest of amplify. Our use case is that we have a...

The key thing here appears to be the "graphql": "^15.7.0" line. That's all it took to fix things for me.

We're doing everything with pure CDK these days. Works pretty well once you get everything rolling.

I do wonder if the overall idea could be taken and run with in a different form. I think the handlebars style language could be a bit more readable, but...

That looks like exactly what I'd want. Maybe a separate issue for that ?

I also still have this issue in 3.21.0.

@blueww I am using azure-storage-blob 12.12.0. Just created the project last week. Manually calculating the hashes does fix it: ``` const md5 = createHash('md5').update(blobContents).digest('hex') await blockClient.uploadStream(Readable.from(blobContents), blobContents.length, 5, { blobHTTPHeaders:...

I'm hitting #1. I cannot browse azurite after uploading a blob using the latest version of the vs code plugin (Azurite v3.21.0), js SDK 12.12.0, and mcr.microsoft.com/azure-storage/azurite:latest for the docker...

@blueww I am browsing to the file in the Azurite v3.21.0 VS Code plugin on the left bar. I am writing the file with the latest version of the SDK.

Microsoft provides a few visual studio code plugins for azurite. https://marketplace.visualstudio.com/items?itemName=Azurite.azurite and https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurestorage. I'm assuming this is a bug with the vscode-azure storage and I should open this over there...