Currently, the Azure component tests don't run on CI as they need test resources in Azure to run. This issue is to decide whether to move these tests to the Azure sdk repo, and utilize the test framework there. And if so, what needs to be done to make it happen.
@eerhardt:
What is the medium-to-long-term vision for where the Azure Hosting code lives? If we intend to move it to [Azure/azure-sdk-for-net](https://github.com/Azure/azure-sdk-for-net/), it may make sense to wait until then to hook it up to automated tests.
On the Components side, my goal is to eventually move them to the Azure repo, so they can ship and service along with the Azure SDK packages.
Currently, the Azure component tests don't run on CI as they need test resources in Azure to run. This issue is to decide whether to move these tests to the Azure sdk repo, and utilize the test framework there. And if so, what needs to be done to make it happen.
context: https://github.com/dotnet/aspire/issues/2689#issuecomment-2045664700
@eerhardt:
What is the medium-to-long-term vision for where the Azure Hosting code lives? If we intend to move it to [Azure/azure-sdk-for-net](https://github.com/Azure/azure-sdk-for-net/), it may make sense to wait until then to hook it up to automated tests.
On the Components side, my goal is to eventually move them to the Azure repo, so they can ship and service along with the Azure SDK packages.
cc @joperezr @mitchdenny