Mitch Denny

Looping in @tg-msft. This is one of the areas where having "deep linked connection strings" are really helpful. When you define a database resource via Aspire like the following: ```csharp...

Glad you raised this @aaronpowell ... I was writing up an example of how you could plumb through the deployment name and found a bug. Fixing that now and will...

OK here is a code sample that I put together as part of this bug fix: #3092 ```csharp var openai = builder.AddAzureOpenAI("openai", (_, _, _, deployments) => { var deployment...

My idea was silly and unncessary, just do this: ```csharp var deploymentAndModelName = "gpt-35-turbo"; var openai = builder.AddAzureOpenAI("openai").AddDeployment( new(deploymentAndModelName, deploymentAndModelName, "0613") ); builder.AddProject("webstory") .WithReference(openai) .WithEnvironment("OpenAI__DeploymentName", deploymentAndModelName); ```

One of the benefits of Aspire is you can use plain old C# :)

Proposing we close this if you are happy @aaronpowell

I think that gets messy pretty quickly. What if you have two OpenAI accounts both with the same deployment name. The variable that you inject for the deployment name now...

This should be fixed now in P5. @christiannagel can you confirm from your end?

I think we should consider the `Use` verb as the way we handle targetting execution during local development. We already have precedent with the Azurite storage emulator support on the...

The challenge there is that `AsContainerInLocalDev` would need to know how to translate `PostgresServerResource` to `ContainerResource` correctly. We would need to some kind of standardized mechanism so components can opt...