You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With .NET Aspire 9.1 releasing I was wondering if we should add the new relationships to the SQL database projects resources so that could become nested under the server resource in the dashboard. Haven’t looked yet at what would be required but should be fairly simple.
Usage example
I don’t think this would require new public API’s. Technically the relationship is already there, we just don’t model it currently
Breaking change?
No
Alternatives
I guess we could just not do it, but I think it makes sense and removes a fair amount of clutter for folks with many database projects being deployed to the same server.
Yep, and it looks like we need to do a bit of a review of how the dependency/waiting happens too, especially in tests (I had to disable a test for the release).
My understanding is that if you configure relationships you get an implicit set of "wait for" behaviour, so we can possibly leverage that. This is why a child resource (eg, a database) doesn't need a WaitFor on the parent (eg: db server).
Related to an existing integration?
Yes
Existing integration
SqlDatabaseProjects
Overview
With .NET Aspire 9.1 releasing I was wondering if we should add the new relationships to the SQL database projects resources so that could become nested under the server resource in the dashboard. Haven’t looked yet at what would be required but should be fairly simple.
Usage example
I don’t think this would require new public API’s. Technically the relationship is already there, we just don’t model it currently
Breaking change?
No
Alternatives
I guess we could just not do it, but I think it makes sense and removes a fair amount of clutter for folks with many database projects being deployed to the same server.
Additional context
@ErikEJ Any thoughts?
Help us help you
Yes, I'd like to be assigned to work on this item
The text was updated successfully, but these errors were encountered: