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
{{ message }}
Repository navigation
Azure Storage should expose a "WithStorageExplorer" API #3778
Similar to pgAdmin and RedisCommander, it would be convenient to expose an Azure Storage Explorer webpage (similar to the one in the Azure Portal) that allows us to browse our Azurite emulator managed instances
Reacted by Kislenko Mikhail, Mrxx99, Einstein Essibu and Niklas Eicker
I've added the following into AppHost, but I can't seem to get the connectionstring passed along. I've tried to grab fragments with no luck
AppHost/Program.cs:
varstorage=builder.AddAzureStorage("storage");if(builder.Environment.IsDevelopment()){storage.RunAsEmulator(config =>{if(Environment.OSVersion.Platform==PlatformID.Win32NT)config.WithDataBindMount("C:\\Temp\\AzureStorage");elseconfig.WithDataBindMount("/tmp/AzureStorage");});}builder.AddContainer("storage-explorer","sebagomez/azurestorageexplorer").WithHttpEndpoint(targetPort:8080);// .WithEnvironment("AZURE_STORAGE_CONNECTIONSTRING", $"""// Use the Azurite AccountName and Key:// DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;// AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;// BlobEndpoint={blobs.Resource.ConnectionStringExpression}/devstoreaccount1;// """);
RunAsEmulator will be used in run mode and not publish mode, so no need to guard it behind the IsDevelopment method.
I also swapped from using a bind mount (which needs a host volume) to using a volume (https://docs.docker.com/storage/bind-mounts/). Our azure storage resource only exposes connection strings for specific resources like blob, queue or table. We don't expose the uber connection string since with all 3.
I also added ExcludeFromManifest to remove this container from being deployed assuming that's what you want to do.
When you call WithReference, this is what happens under the covers (we make a ConnectionStringReference). There's an API coming post GA that will make this a bit easier:
Very cool! That appears to have that container running and connecting to the storage service. I really need to access the tables browser, so I changed the connectionstring over to the tables instance and it doesn't appear to be connecting like the blobs connectionstring does.
There appears to be a few issues with the Storage Explorer container. I'll connect with that package owner and see if we can get that in a better working order
Hi please is this solution for the azure storage explorer going to eventually be officially integrated to .NET aspire as a container like pgAdmin? That would be so helpful if possible. I am having issues connecting the Microsoft azure monitor to the azurite instance created by aspire.
Configuring the storage explorer like shown above doesn't seem to work as expected for me. The explorer fails to log me in using the supplied connection string. Did someone get this to work for a local Azurite blob storage?
On the first glance, it looks like an issue on the side of storage explorer, not Aspire, so I opened sebagomez/azurestorageexplorer#173 with more details.
Edit: this seems to be a general connectivity issue from Aspire on Linux without Docker Desktop.
Our azure storage resource only exposes connection strings for specific resources like blob, queue or table. We don't expose the uber connection string since with all 3.
David Fowler (@davidfowl) it would be useful to get this uber connection string. Happy to contribute.
Activity
davidfowl commentedon Apr 17, 2024
That sounds great, how would it work? Is there a container that runs the storage explorer that exposes an http endpoint?
csharpfritz commentedon Apr 17, 2024
The team has a slimmed down version that runs in the Azure Portal. I don't think its available as a container though.
I'm exploring the image at https://github.com/sebagomez/azurestorageexplorer to attach and work with my Aspire hosted Azure Storage instances
csharpfritz commentedon Apr 18, 2024
I am having a hard time getting that StorageExplorer container connected with a proper connectionstring to a host Azurite emulator.
Any ideas how to pull the connectionstring in AppHost and pass it as an environment variable?
davidfowl commentedon Apr 18, 2024
Show me what you have currently?
csharpfritz commentedon Apr 18, 2024
I've added the following into AppHost, but I can't seem to get the connectionstring passed along. I've tried to grab fragments with no luck
AppHost/Program.cs:
davidfowl commentedon Apr 18, 2024
RunAsEmulator will be used in run mode and not publish mode, so no need to guard it behind the IsDevelopment method.
I also swapped from using a bind mount (which needs a host volume) to using a volume (https://docs.docker.com/storage/bind-mounts/). Our azure storage resource only exposes connection strings for specific resources like blob, queue or table. We don't expose the uber connection string since with all 3.
I also added
ExcludeFromManifestto remove this container from being deployed assuming that's what you want to do.When you call WithReference, this is what happens under the covers (we make a
ConnectionStringReference). There's an API coming post GA that will make this a bit easier:csharpfritz commentedon Apr 18, 2024
Very cool! That appears to have that container running and connecting to the storage service. I really need to access the tables browser, so I changed the connectionstring over to the tables instance and it doesn't appear to be connecting like the blobs connectionstring does.
There appears to be a few issues with the Storage Explorer container. I'll connect with that package owner and see if we can get that in a better working order
Huge thanks for the help with this solution!
19essibusa commentedon Aug 7, 2024
Hi please is this solution for the azure storage explorer going to eventually be officially integrated to .NET aspire as a container like pgAdmin? That would be so helpful if possible. I am having issues connecting the Microsoft azure monitor to the azurite instance created by aspire.
NiklasEi commentedon Sep 3, 2024
Configuring the storage explorer like shown above doesn't seem to work as expected for me. The explorer fails to log me in using the supplied connection string. Did someone get this to work for a local Azurite blob storage?
On the first glance, it looks like an issue on the side of storage explorer, not Aspire, so I opened sebagomez/azurestorageexplorer#173 with more details.Edit: this seems to be a general connectivity issue from Aspire on Linux without Docker Desktop.
swissarmykirpan commentedon Sep 24, 2024
Our azure storage resource only exposes connection strings for specific resources like blob, queue or table. We don't expose the uber connection string since with all 3.David Fowler (@davidfowl) it would be useful to get this uber connection string. Happy to contribute.
swissarmykirpan commentedon Sep 24, 2024
Jeffrey T. Fritz (@csharpfritz) another alternative may be change the Azure Storage Resource Endpoints (in the resources table) to use Azure Storage Explorer Direct Links https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-direct-link
davidfowl commentedon Oct 16, 2024
Filed an issue #6234.
Closing this as there's no locally hostable storage explorer that we would embed by default.