-
Notifications
You must be signed in to change notification settings - Fork 61
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
docs/test: Documentation for image validation, improve validation test coverage #88
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.
very concise description of the algorithm! I like the sentence that ends with "validated in previous steps for later files" :)
Personally, I'd say that unrelated things (missing tests, and docs of something else) should go into different commits. I like having the upside of being able to revert a commit (e.g. when you don't want the tests anymore) without loosing something else unintentionally. (I'll approve regardless.)
a0f7c59
to
6ec43c1
Compare
f4e69d9
to
ddae980
Compare
This commit documents the existing image validation procedure employed by Connaisseur
This commit adds some test cases for all supported and one unsupported Kubernetes resource, tests more invalid trust data and checks the combination of valid and invalid delegations alongside each other
ddae980
to
64f7c84
Compare
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.
lgtm!
This PR documents the existing validation procedure employed by Connaisseur. In addition, it adds some test cases for all supported and one unsupported Kubernetes resource, tests more invalid trust data and checks the combination of valid and invalid delegations alongside each other. Also typos