Aspire integration extensions #10759
-
|
I just want to ask which |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Anything the team decides is important enough to be part of dotnet/aspire. It's a little fuzzy but the aspire teams owns and maintains whatever is in dotnet/aspire, where the CommunityToolkit has a distributed set of owners for each integration. Right now there are a set of resources that we want out of this repository and into the owners of the integration (for e.g. Seq, Nats, etc). As an example, we moved AWS, elastic search and more to the owners of those libraries at companies. Right now the azure resources are part of this repository but longer term it'll be part of the azure sdk repo. That's the long way of saying, "we get to decide" 😄. By default new integraton proposals that are not azure resources should go into the toolkit repo. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for clarification :) |
Beta Was this translation helpful? Give feedback.
Anything the team decides is important enough to be part of dotnet/aspire. It's a little fuzzy but the aspire teams owns and maintains whatever is in dotnet/aspire, where the CommunityToolkit has a distributed set of owners for each integration.
Right now there are a set of resources that we want out of this repository and into the owners of the integration (for e.g. Seq, Nats, etc). As an example, we moved AWS, elastic search and more to the owners of those libraries at companies.
Right now the azure resources are part of this repository but longer term it'll be part of the azure sdk repo.
That's the long way of saying, "we get to decide" 😄. By default new integraton proposals that are n…