-
Notifications
You must be signed in to change notification settings - Fork 267
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
Document ADR 0008 about unrecognized fields #1343
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, thanks @MVrachev! This should help us move forward with some of the TAPs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for capturing this @MVrachev. I made a few minor comments, otherwise this looks good.
@joshuagl I addressed your comments and amend the commit so it can be ready to be merged. PS: I had to force-push a couple of times to fix some formatting issues. |
73fa130
to
6a68dfb
Compare
Even though, this ADR documents something already implied in the TUF spec in [document formats](https://theupdateframework.github.io/specification/latest/#document-formats) it seems better to document this decision clearly so that it could be referenced and give an explanation why someone can load a metadata file with additional unrecognized fields. Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
I am not sure why, but we have a CI failure again on Windows |
Not at all, this is tox calling pip and pip failing to download "typed-ast" in some fantastic way... |
For reference: the CI failure seems like a pypi problem (made worse by our decision to use pre-release build tooling so downloading more often). Disappeared on re-run, I'm not filing any issues on that. Merging this. |
Please fill in the fields below to submit a pull request. The more information
that is provided, the better.
Fixes #1266
Description of the changes being introduced by the pull request:
Even though, this ADR documents something already implied in the TUF
spec in document formats
it seems better to document this decision clearly so that it could be
referenced and give an explanation why someone can load a metadata file
with additional unrecognized fields.
Signed-off-by: Martin Vrachev mvrachev@vmware.com
Please verify and check that the pull request fulfills the following
requirements: