-
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
Change the storage version to v1beta1 types #2577
Conversation
@@ -22,7 +22,6 @@ import ( | |||
"github.com/tektoncd/pipeline/pkg/apis/config" | |||
"github.com/tektoncd/pipeline/pkg/apis/pipeline/v1alpha1" | |||
"github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1" | |||
"github.com/tektoncd/pipeline/pkg/reconciler/taskrun/resources" |
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.
We should never import pkg/reconciler
packages outside of pkg/reconciler
😈
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.
💯
The following is the coverage report on the affected files.
|
very exciting. cant wait for v1beta1 everywhere! |
d378b44
to
2ac5e0e
Compare
The following is the coverage report on the affected files.
|
2ac5e0e
to
c76feb3
Compare
The following is the coverage report on the affected files.
|
c76feb3
to
9c16f2a
Compare
The following is the coverage report on the affected files.
|
9c16f2a
to
55427ec
Compare
The following is the coverage report on the affected files.
|
55427ec
to
c71660e
Compare
The following is the coverage report on the affected files.
|
I don't understand 🤔 |
aa8e64c
to
5b92e22
Compare
The following is the coverage report on the affected files.
|
5b92e22
to
79734a2
Compare
@sbwsg @bobcatfish we can provide a |
Conflicting files
D: my apologies, i guess these all stem from the cmp.Diff changeset. |
🙀 |
79734a2
to
ca8ff88
Compare
@sbwsg should be fixed 🎐 |
I like the idea of documenting this in its first iteration. Would it become a part of any future release, do you think? I guess the idea is to not break anyone who's happy with their alpha tasks and doesn't want to rock the boat with an upgrade. But are these folks even upgrading? And then how long should we be supporting them? That might be a bigger question than we can answer here though. |
The following is the coverage report on the affected files.
|
ca8ff88
to
d21e298
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-integration-tests |
want *corev1.PodSpec | ||
wantAnnotations map[string]string | ||
}{{ | ||
desc: "simple", | ||
ts: v1alpha1.TaskSpec{TaskSpec: v1beta1.TaskSpec{ | ||
Steps: []v1alpha1.Step{{Container: corev1.Container{ | ||
ts: v1beta1.TaskSpec{ |
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.
🎉
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 read through and I guess my only question is: are we at a point where chunks of the v1alpha1
packages can start to be deleted? Or is that still a ways off?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
We can start to think about it but… if it affects the API served, we need to make a deprecation notice on the CRDs not in v1alpha1 anymore (and I think we should take some time). But in a gist, yes, after this PR gets merged, we can start cleaning the |
@@ -21,7 +21,8 @@ import ( | |||
|
|||
"github.com/google/go-cmp/cmp" | |||
"github.com/google/go-cmp/cmp/cmpopts" | |||
"github.com/tektoncd/pipeline/pkg/apis/pipeline/v1alpha1" | |||
"github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1" | |||
resourcev1alpha1 "github.com/tektoncd/pipeline/pkg/apis/resource/v1alpha1" |
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.
much cleaner 👍
Type: "image", | ||
Params: []v1alpha1.ResourceParam{{ | ||
Params: []v1beta1.ResourceParam{{ |
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.
Should this be Params: []resourcev1alpha1.ResourceParam
instead of Params: []v1beta1.ResourceParam
? 🤔
thanks @vdemeester |
d21e298
to
8d250e4
Compare
The following is the coverage report on the affected files.
|
- switch storage to v1beta1 for CRDs (config/) - use v1beta1 in controllers, … Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
8d250e4
to
a01d514
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-integration-tests |
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.
Nice work, thank you so much!!!
/lgtm
@@ -0,0 +1,81 @@ | |||
/* | |||
Copyright 2019 The Tekton Authors |
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 NIT: should we update the year in the copyright statements of the new files in the beta folder?
/test pull-tekton-pipeline-integration-tests |
YAAAAASSS!!!! 🎉 |
Changes
This changes the stored version to
v1beta1
👼 This will reduce some confusion on where to add fields and how to work with which version in most of the tektoncd/pipeline code.Still a little bit of work to do:
ResolvedTask…
builders are gone, use struct for thoseCloses #2410
/kind cleanup
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes