Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle non-matching tag names between manifest and image info file #693

Merged
merged 1 commit into from
Nov 11, 2020

Conversation

mthalman
Copy link
Member

In cases where a dynamically named tag is defined in the manifest, such as with the use of $(System:TimeStamp), there's likely to be discrepancies in the tag names between the manifest and the tag names defined in the image info file that was generated during the build. The logic in CopyAcrImagesCommand doesn't handle this and explicitly expects there to be a matching tag name. When it can't find one, an exception occurs.

I've updated the logic to gracefully handle this scenario by simply ignoring the fact that it couldn't find a match and not attempt to process the syndication data. I think it's fine to say that, for now, syndication won't be supported for such dynamically named tags. I do think this could eventually be supported with the manifest redesign by allowing tags to have statically defined identifiers.

Fixes #686

@mthalman mthalman merged commit 21bf941 into dotnet:master Nov 11, 2020
@mthalman mthalman deleted the issue686 branch November 11, 2020 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New logic for tag syndication breaks publishing of tags with dynamic names
2 participants