Thoughts about aspire deploy #11850
-
While However, I also had some issues: When using azd I just needed to set to keep all the configured domains - which no longer works with azd. Using Thanks for your work on the Aspire CLI! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Thanks for using this very early version of aspire deploy. There's A LOT of gaps and things we need to build but we're rapidly iterating, we wanted to get something out of the door in 9.5 so we could start getting feedback.
Interesting, I think we made it so that you can call ConfigureCustomDomain multiple times, so happy to see that it worked 😄.
Can you elaborate?
Yes, automating configuration for custom domains and expanding the options is high on the list of things to improve for the ACA end to end.
Assuming you mean manged identity? No this transition to aspire owned infrastructure happend in 9.1-9.2. If you had a deployment from before then, then you may be managing a multi version transition over to 9.5 and aspire deploy. The main difference is what that the apphost has extensible logic for what deployment means, it is not baked into the CLI. The deployment stage is stored in azure and today if you deploy with the same values it'll create a new deployment but won't re-deploy resources that already exist (that's just ARM logic).
We're working through this in the next release. Today we have a single phase and we're working through what it means to build an extensible pipeline that others can plug into. @captainsafia is leading the charge here along with @vhvb1989 and @eerhardt. |
Beta Was this translation helpful? Give feedback.
-
Seeing this, and it's great 🥇
After updating .NET Aspire, the workflow I had with Using AddAzureContainerAppEnvironment, the
No, I'm managing all the managed identities with Aspire :-) I was thinking about when adding authentication with the Azure portal, adding an identity provider, Microsoft Entra. Is this setting similar lost to the domain names?
I've seen this - but the domain names are lost if not configured with
This is great. Looking forward to it 💯 |
Beta Was this translation helpful? Give feedback.
@christiannagel Thanks for sharing the feedback!
Good note. We should probably add a note documenting this behavior for 9.5. This happens because
aspire deploy
and the Azure provisioning that we do during run-mode share the same core API in Aspire that we use for sending deployment requests to Azure. Both components read th…