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

Add ResolutionRequest v1beta1, without serving yet #5495

Merged
merged 1 commit into from
Sep 15, 2022

Conversation

abayer
Copy link
Contributor

@abayer abayer commented Sep 14, 2022

Changes

part of #4710

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.

/kind feature

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs included if any changes are user facing
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

@abayer abayer added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 14, 2022
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Sep 14, 2022
@tekton-robot tekton-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Sep 14, 2022
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/resolution/v1alpha1/resolution_request_conversion.go Do not exist 92.0%
pkg/apis/resolution/v1beta1/register.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_conversion.go Do not exist 66.7%
pkg/apis/resolution/v1beta1/resolution_request_defaults.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_lifecycle.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_types.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_validation.go Do not exist 0.0%

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 14, 2022
@vdemeester
Copy link
Member

@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>
@abayer abayer force-pushed the unserved-resolution-v1beta1 branch from 18ca1c0 to 5ee580b Compare September 15, 2022 12:37
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/resolution/v1alpha1/resolution_request_conversion.go Do not exist 92.0%
pkg/apis/resolution/v1beta1/register.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_conversion.go Do not exist 66.7%
pkg/apis/resolution/v1beta1/resolution_request_defaults.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_lifecycle.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_types.go Do not exist 0.0%
pkg/apis/resolution/v1beta1/resolution_request_validation.go Do not exist 0.0%

@abayer
Copy link
Contributor Author

abayer commented Sep 15, 2022

@vdemeester done!

Copy link
Member

@jerop jerop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2022
@tekton-robot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot merged commit 75ac2fb into tektoncd:main Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants