David Fowler
David Fowler
It’s not clear how we’d generalize this yet. We did a minimum implementation for dev only. Running script in deployment environments is something we want to do but it’s non...
That should already work if you do ```RunAsContainer(c => c.WithCreationScript(..))```
Ah, I see. @sebastienros @RussKie We should do this as part of the database work in 9.3
I understand the problem and can talk to @RussKie
@sebastienros as part of this work we should make these annotations public
@joperezr This should be built into the resiliency package.
> Changing the default behavior to not retry non-idempotent calls would be a breaking change, since some customers already rely on current default behavior. I understand but this feels like...
At a minimum let's make a new top-level method where this is the default behavior. That seems like a reasonable compromise.
@IEvangelist we should have a blurb like this https://learn.microsoft.com/en-us/dotnet/aspire/azure/integrations-overview?tabs=dotnet-cli#add-connection-to-existing-azure-resources closer to where people are using integrations. We could consider a better page rather than external parameters for this information https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/external-parameters#connection-string-values...