dotnet
Support non-flat layouts in BlobArtifacts
- [ ] This issue is blocking
- [ ] This issue is causing unreasonable pain
Right now we only allow for a flat layout in BlobArtifacts when PushToAzureDevOpsArtifacts runs. This is normally fine because all repos in .NET create uniquely named artifacts. These can then be uploaded to arbitrary locations (like subpaths on dotnetcli). This works because basically all the artifacts we publish are containers (e.g. we're not publishing dotnet.exe, which would be duplicated in different artifacts).
The diagnostics folks want to upload individual executables for publishing. These executables have the same name across different RIDS. Because BlobArtifacts has a flat layout, this becomes impossible. We need to explore allowing BlobArtifacts to not have a flat layout to support these scenarios.
There are some initial investigations that are necessary:
- [ ] Why did we decide on this in the first place (pretty sure it was a conscious decision)?
- [ ] What locations assume the flat layout of BlobArtifacts?
As far as places that assume the flat layout right now, for sure there is at least:
- [ ] SDL
- [ ] Publishing
- [ ] Sign checks, other validation stages
This may be a breaking change requiring a rev in the version number of the manifest and new publishing infra.
