Blob Storage Integration - No container created on initialization

[mpab1410]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I searched around for this, and found one issue over in the docs-aspire repo that went over this same issue for Queue Storage (dotnet/docs-aspire#2558), though I did not find one here so I figured I would report this over here just in case this is supposed to have the behavior the docs describe. If not, I can make a comment on that issue.

Per the docs here (https://github.com/dotnet/docs-aspire/blob/f68027cc12ae8d6d53b3510e0065b621e7d31415/docs/storage/azure-storage-blobs-integration.md?plain=1#L40), the Blob Storage integration should be creating a container with the name given for the Blob connection reference.

When running locally and after provisioning into Azure, no Blob container with the passed name from .AddBlobs(name) exists.

Expected Behavior

When calling .AddBlobs("randomfiles") on a Storage resource, a new container called "randomfiles" is created on initialization of the Storage resource, both locally via the emulator and once provisioned into Azure

Steps To Reproduce

Basic repro with some API endpoints can be found here: https://github.com/mpab1410/AspireBlobIssueRepro

Exceptions (if any)

No response

.NET Version info

> dotnet --info
.NET SDK:
 Version:           9.0.200
 Commit:            90e8b202f2
 Workload version:  9.0.200-manifests.41784c06
 MSBuild version:   17.13.8+cbc39bea8

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\9.0.200\

.NET workloads installed:
 [ios]
   Installation Source: VS 17.13.35825.156
   Manifest Version:    18.2.9180/9.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.sdk.ios\18.2.9180\WorkloadManifest.json
   Install Type:              Msi

 [aspire]
   Installation Source: VS 17.13.35825.156
   Manifest Version:    9.0.0-preview.1.24079.4/9.0.100-preview.1
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\9.0.100-preview.1\microsoft.net.sdk.aspire\9.0.0-preview.1.24079.4\WorkloadManifest.json
   Install Type:              Msi

 [android]
   Installation Source: VS 17.13.35825.156
   Manifest Version:    35.0.39/9.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.sdk.android\35.0.39\WorkloadManifest.json
   Install Type:              Msi

 [maui-windows]
   Installation Source: VS 17.13.35825.156
   Manifest Version:    9.0.14/9.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.sdk.maui\9.0.14\WorkloadManifest.json
   Install Type:              Msi

 [maccatalyst]
   Installation Source: VS 17.13.35825.156
   Manifest Version:    18.2.9180/9.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.sdk.maccatalyst\18.2.9180\WorkloadManifest.json
   Install Type:              Msi

Configured to use loose manifests when installing new manifests.

Host:
  Version:      9.0.2
  Architecture: x64
  Commit:       80aa709f5d

.NET SDKs installed:
  9.0.200 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Anything else?

No response

[davidfowl]

Closing as duplicate of #8295

[davidfowl]

You can see #8402 for the current state of the art.

[davidfowl]

@IEvangelist our docs are wrong here

That name is the name of the aspire resource, not the name of the container within the blob. All aspire resources have names that are used to uniquely identity them.

[RussKie]

Steps To Reproduce
Basic repro with some API endpoints can be found here: mpab1410/AspireBlobIssueRepro

@mpab1410 is your repro still available?

[mpab1410]

@RussKie Apologies, the repo should be restored now 👍

[RussKie]

Sweet, thanks

[RussKie]

@mpab1410 please have a look at #9008. In the next version you will be able to write the following:

Host:

var blobs = storage.AddBlobs("blobs");
blobs.AddBlobContainer("mycontainer1", blobContainerName: "test-container-1");

builder.AddProject<Projects.AzureStorageEndToEnd_ApiService>("api")
       .WithReference(blobs).WaitFor(blobs);

Client:

builder.AddAzureBlobContainerClient("foocontainer");

var app = builder.Build();
app.MapGet("/", async (BlobContainerClient bcc) =>
{
}

or

builder.AddKeyedAzureBlobContainerClient("foocontainer");

var app = builder.Build();
app.MapGet("/", async ([FromKeyedServices("foocontainer")] BlobContainerClient bcc) =>
{
}

[mpab1410]

Awesome, thanks a bunch!