You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on an IoT Edge deployment, and will be using the blob storage module (provided as a container via mcr.microsoft.com/azure-blob-storage) for local storage and automatic syncing.
I'm currently trying to set up a devcontainer that includes that module and this extension as an interface to it, so that I can access the info for debug. Unfortunately this extension currently works extremely poorly with the module. I have to fall back to using the Azure Storage Explorer, which I'd like to avoid as it's an additional tool to tell other developers to install.
There's a number of issues I've encountered, however some of them may stem simply from being forced to use an older, pinned version of the extension; the blob storage module only accepts API versions before 2022-11-02, so I have to pin to v1.15.0, and I think some of the other errors I'm seeing were otherwise fixed in v1.15.1....
The text was updated successfully, but these errors were encountered:
I'm working on an IoT Edge deployment, and will be using the blob storage module (provided as a container via
mcr.microsoft.com/azure-blob-storage
) for local storage and automatic syncing.I'm currently trying to set up a devcontainer that includes that module and this extension as an interface to it, so that I can access the info for debug. Unfortunately this extension currently works extremely poorly with the module. I have to fall back to using the Azure Storage Explorer, which I'd like to avoid as it's an additional tool to tell other developers to install.
There's a number of issues I've encountered, however some of them may stem simply from being forced to use an older, pinned version of the extension; the blob storage module only accepts API versions before
2022-11-02
, so I have to pin tov1.15.0
, and I think some of the other errors I'm seeing were otherwise fixed inv1.15.1
....The text was updated successfully, but these errors were encountered: