Ensure that we have test coverage for Microsoft Defender usage scenarios in the SDK test suite #648
Description
To improve the quality of the SDK Containers feature and improve confidence in the rollout of the feature across MDE, we need to
- audit MDE deployment methods to determine the 'axis of uniqueness' across the different repos. interesting pivots are:
- 'scope' of publishing: project vs solution-level
- project type: console vs web
- TFM usage: multi-targeting or single-target
- publish destination: tarball vs local daemon vs remote registry
We should cross-check these pivots against existing SDK container test cases and write SDK tests to address the gaps, if any.
Known Gaps
Container Test Re-enablement
As part of infrastructure work, many container tests have been Skipped. We need to re-enable those tests, which will likely mean investigating the configuration of the Docker daemon on the Ubuntu build agents, making sure they are configured to use the containerd backend, etc.
Azure Container Registry
Single- and multi-arch publish to ACR. We don't have any ACR publish coverage today, but that would be good to improve as time/resources allow. In the interim, multi-arch publish to registry:2 will is a good baseline for coverage.