Skip to content

v1.6.0

Compare
Choose a tag to compare
@jinglouMSFT jinglouMSFT released this 05 Dec 01:06

12/4/2018

Welcome to version 1.6.0 of Microsoft Azure Storage Explorer. This release focuses on supporting RBAC for Blobs and ADLS Gen2 Storage accounts.

New

  • You can now use Storage Explorer to access your Blob data via RBAC. If you are signed in and Storage Explorer is unable to retrieve the keys for your Storage account, then an OAuth token will be used to authenticate when interacting with your data.

  • Storage Explorer now supports ADLS Gen2 Storage accounts. When Storage Explorer detects that hierarchical namespace is enabled for a Storage account, you will see "(ADLS Gen2 Preview)" next to the name of your Storage account. Storage Explorer is able to detect whether or not hierarchical namespace is enabled when you are signed in, or if you have attached your Storage Account with name and key. For ADLS Gen2 Storage accounts, you can use Storage Explorer to:

    • Create and delete containers.
    • Manage container properties and permissions (left-hand side).
    • View and navigate data inside of containers.
    • Create new folders.
    • Upload, download, rename, and delete files and folders.
    • Manage file and folder properties and permissions (right-hand side).

    Other typical Blob features, such as Soft Delete, and Snapshots, are not currently available. Managing permissions is also only available when signed in. Additionally, when working in an ADLS Gen2 Storage account, Storage Explorer will use AzCopy for all uploads and downloads and default to using name and key credentials for all operations if available.

  • After strong user feedback, break lease can once again be used to break leases on multiple blobs at once.

Known Issues

  • When downloading from an ADLS Gen2 Storage account, if one of the files being transferred already exists, then AzCopy will sometimes crash. This will be fixed in an upcoming hotfix.

  • Detatching from a resource attached via SAS URI, such as a blob container, may cause an error that prevents other attachments from showing up correctly. To work around this issue, just refresh the group node. See #537 for more information.

  • If you use VS for Mac and have ever created a custom AAD configuration, you may be unable to sign-in. To work around the issue, delete the contents of ~/.IdentityService/AadConfigurations. If doing so does not unblock you, please comment on this issue.

  • Azurite has not yet fully implemented all Storage APIs. Because of this, there may be unexpected errors or behavior when using Azurite for development storage.

  • In rare cases, the tree focus may get stuck on Quick Access. To unstick the focus, you can Refresh All.

  • Uploading from your OneDrive folder does not work because of a bug in NodeJS. The bug has been fixed, but not yet integrated into Electron. To workaround this issue when uploading to or downloading from a blob container, you can use the experimental AzCopy feature.

  • When targeting Azure Stack, uploading certain files as append blobs may fail.

  • After clicking "Cancel" on a task, it may take a while for that task to cancel. This is because we are using the cancel filter workaround described here.

  • If you choose the wrong PIN/Smartcard certificate, then you will need to restart in order to have Storage Explorer forget that decision.

  • Renaming blobs (individually or inside a renamed blob container) does not preserve snapshots. All other properties and metadata for blobs, files and entities are preserved during a rename.

  • Azure Stack does not support the following features:

    • File shares
    • Access tiers
    • Soft Delete

    Attempting to use these features while working with Azure Stack resources may result in unexpected errors.

  • The Electron shell used by Storage Explorer has trouble with some GPU (graphics processing unit) hardware acceleration. If Storage Explorer is displaying a blank (empty) main window, you can try launching Storage Explorer from the command line and disabling GPU acceleration by adding the --disable-gpu switch:
    ./StorageExplorer.exe --disable-gpu

  • For Linux users, you will need to install .NET Core 2.0.

  • For users on Ubuntu 14.04, you will need to ensure GCC is up to date - this can be done by running the following commands, and then restarting your machine:

    sudo add-apt-repository ppa:ubuntu-toolchain-r/test
    sudo apt-get update
    sudo apt-get upgrade
    sudo apt-get dist-upgrade

  • For users on Ubuntu 17.10, you will need to install GConf - this can be done by running the following commands, and then restarting your machine:

    sudo apt-get install libgconf-2-4