-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[TEP-0091] support remote v1 pipeline verification #6765
[TEP-0091] support remote v1 pipeline verification #6765
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/assign |
} | ||
|
||
warnPolicyRefSource := &v1beta1.RefSource{ | ||
URI: " warnVP", |
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.
what does warnVP signify?
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.
it means warn mode verification policy, we have a warn mode policy and the pattern is warnVP
from vps(verification policies)
.
So this warnPolicyRefSource could match that policy for testing
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.
I will refactor the tests code later when feature PRs are merged. So we could improve the test readability.
signer, _, k8sclient, vps := test.SetupVerificationPolicies(t) | ||
tektonclient := fake.NewSimpleClientset() | ||
|
||
v1beta1UnsignedPipeline := &v1beta1.Pipeline{ |
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.
does it make sense to have also testing with v1UnsignedPipeline/ v1Signed?
this also felt like something we might be able to use as a helper function for the taskRef verification PR as well?
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.
I think this test is testing v1UnsignedPipeline and v1signed? The v1beta1UnsignedPipeline
is used to check the resolvedTask
is expected (refer to a v1 task, verify and convert the v1 task, then return a v1beta1 task).
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 @Yongxuanzhang
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 @Yongxuanzhang
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 @Yongxuanzhang
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom, JeromeJu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
c532bc3
to
f44fc90
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
f44fc90
to
d32c5ee
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
This commit adds the support for v1 pipeline verification. Previously we only support v1beta1 verification. Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
2e54919
to
896f0fd
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
Changes
This commit adds the support for v1 pipeline verification. Previously we only support v1beta1 verification.
Part of #6729
/kind feature
Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes