beda7bcaf8
- This removes the ci.yml filtering which means all projects can be discovered - This eliminates the need for the yml parsing module for most common scenarios - This does introduce some potential issues with duplicate package names for languages like java. The only known case currently is azure-storage-blobs and if there is ever a need to explicitly pick the correct one someone can pass in the ServiceDirectory filter similar to "storage/azure*" for new and "storage/microsoft*" for the older sdk. By default azure usually comes first so the new one gets discovered which is likely all we need for now. If this turns out not to be true we might need another way to disambiguate. Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com> Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| docgeneration | ||
| pipelines/templates | ||
| scripts | ||
| TestResources | ||
| InterdependencyGraph.html | ||
| README.md | ||
| Update-Change-Log.ps1 | ||
Common Engineering System
Updates under this directory should only be made in the azure-sdk-tools repo as any changes under this directory outside of that repo will end up getting overwritten with future updates. For information about making updates see common engineering system docs