-
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
Add ResolutionRequest v1beta1, without serving yet #5495
Add ResolutionRequest v1beta1, without serving yet #5495
Conversation
The following is the coverage report on the affected files.
|
@abayer needs a small rebase 🙏🏼 |
This is the first part of moving remote resolution to beta. Here, we add a new `v1beta1` version of `ResolutionRequest`, with conversion, though the new version is neither served nor stored. The difference between the `v1alpha1` and `v1beta1` version is that we're switching from `Parameters`, a `map[string]string`, to `Params`, a `[]pipelinev1beta1.Param`, so that we can end up passing array and object parameters to resolution requests. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
18ca1c0
to
5ee580b
Compare
The following is the coverage report on the affected files.
|
@vdemeester done! |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop, lbernick 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 |
Changes
part of #4710
This is the first part of moving remote resolution to beta. Here, we add a new
v1beta1
version ofResolutionRequest
, with conversion, though the new version is neither served nor stored. The difference between thev1alpha1
andv1beta1
version is that we're switching fromParameters
, amap[string]string
, toParams
, a[]pipelinev1beta1.Param
, so that we can end up passing array and object parameters to resolution requests./kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes