Is it intended that the Azure Storage provider create containers like blobs?

[VistianOpenSource]

Even with the simpliest of projects, I appear to be in a situation in which, upon deployment to Azure, storage accounts are created, but not blob containers which I have specified.

I have added Aspire.Hosting.Azure.Storage (v9.1) to the AppHost of default demo Aspire app which Visual Studio creates.

I adjusted the code in the AppHost to be:

var builder = DistributedApplication.CreateBuilder(args);

var storage = builder.AddAzureStorage("content");
var blobs = storage.AddBlobs("blobs");

var apiService = builder.AddProject<Projects.AspireApp_ApiService>("apiservice");

builder.AddProject<Projects.AspireApp_Web>("webfrontend")
    .WithExternalHttpEndpoints()
    .WithReference(apiService)
    .WithReference(blobs)
    .WaitFor(blobs)
    .WaitFor(apiService);

builder.Build().Run();

When I hit publish (in Visual Studio), I can see that the content storage account is created, but when the publish is complete, there isn't a blob container called blobs created within it.

Am I missing something here ?

[davidfowl]

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. When we support adding and creating a blob container, there would be a call to AddContainer hanging off AddBlobs.

[davidfowl]

It will do 1. but it doesn't currently. See #8295 and #5167.

Given that isn't the case, would the approach instead be to construct a simplistic initalization application and for the other resources which are dependant upon the blob containers to 'wait' for this initialization application to complete?

You can handle ResourceReadyEvent and write initialization code in there until we do this work, see:

aspire/playground/mongo/Mongo.AppHost/Program.cs

Lines 10 to 32 in 7a3cf00

	var db = builder.AddMongoDB("mongo")
	.WithMongoExpress(c => c.WithHostPort(3022))
	.AddDatabase("db");
	builder.Eventing.Subscribe<ResourceReadyEvent>(db.Resource, async (@event, ct) =>
	{
	// Artificial delay to demonstrate the waiting
	await Task.Delay(TimeSpan.FromSeconds(10), ct);
	// Seed the database with some data
	var cs = await db.Resource.ConnectionStringExpression.GetValueAsync(ct);
	using var client = new MongoClient(cs);
	const string collectionName = "entries";
	var myDb = client.GetDatabase("db");
	await myDb.CreateCollectionAsync(collectionName, cancellationToken: ct);
	for (int i = 0; i < 10; i++)
	{
	await myDb.GetCollection<Entry>(collectionName).InsertOneAsync(new Entry(), cancellationToken: ct);
	}
	});

For an example of database seeding with mongo.

PS: We have plans to implement this but it hasn't been done yet.

[VistianOpenSource]

Okay, thanks, makes sense.

On a related note, the couple of times I've asked questions in this repo, the quick turn around in responses and help has been really good. Thanks to all concerned.

[davidfowl]

Great to hear that! We're going to make it so that what you are trying to do is seamless. It should be really easy to create, connect to and consume any resource with aspire.

[VistianOpenSource]

Just to confirm on this, the sample you provided and the mechanism to subscribe to events like ResourceReadyEvent are only executed if you run the apphost?

i.e it's not something thats 'magically' executed when you deploy to Azure?

[davidfowl]

Correct. If you want the same behavior in azure, you have to drop to the lower level ConfigureInfrastructure and start messing with the cdk constructs. If you know the bicep you need to write it shouldn't be too bad.