I'm running into similar issues. I understand, @davidfowl, that Aspirate doesn't understand Azure resources. But some kind of supporting documentation to help us get through what is a very simple example would be nice.

I'm trying to build/deploy a .NET Orleans app with Aspire that is leveraging Blob/Table storage as the clustering/grain-state.

When deploying my project via Aspirate, I do get a bicep file for my storage account, but it doesn't appear to be executed as a part of the deployment.

When attempting to deploy via azd, it appears that my only option is to deploy to a Container Apps instance.

I've also attempted to do two separate deployments but continue to run into major problems.

1. The storage account's name is a unique id generated from the resource group name. It is not clear how to pass the storage account's resource group name into the configuration settings for my Aspire AppHost so that it understands where to get the connection string from.

2. Because I'm using Orleans there are way more environment variables that must be assigned instead of just the connection string in order for the Orleans app to even startup and recognize its providers properly. So, checking if the ExecutionContext is running vs publishing to override the connection string doesn't generate the details necessary for the Aspire Orleans package to pickup the configuration settings.

I would think this is a somewhat simple scenario for Aspire/Aspirate. Can we get some help or more documentation to support this?