In diagnostics we recently moved to V3 Publishing. We set a special target in publishing.props to generate add a nupkg to ItemsToPushToBlobFeed with the ManifestArtifactData having Category=OTHER. The resulting manifest having a Category attribute in the manifest, and the package would get published to blob storage. However, V3 publishing doesn't preserve such metadata when generating MergedManifest.xml (The Blob class in arcade-services doesn't have a field for it) and the item ends up in the feed assigned to the default channel. This causes it to not be available through an aka.ms link nor in blob storage, and we use this in the dotnet-docker repo to generate the images. Is there any way to get this back in v3, or is this expected?
cc: @jander-msft
In diagnostics we recently moved to V3 Publishing. We set a special target in publishing.props to generate add a nupkg to
ItemsToPushToBlobFeedwith theManifestArtifactDatahavingCategory=OTHER. The resulting manifest having a Category attribute in the manifest, and the package would get published to blob storage. However, V3 publishing doesn't preserve such metadata when generatingMergedManifest.xml(TheBlobclass in arcade-services doesn't have a field for it) and the item ends up in the feed assigned to the default channel. This causes it to not be available through an aka.ms link nor in blob storage, and we use this in thedotnet-dockerrepo to generate the images. Is there any way to get this back in v3, or is this expected?cc: @jander-msft