-
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
misc: promote stepAction to beta #7920
misc: promote stepAction to beta #7920
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
df7352a
to
f612352
Compare
The following is the coverage report on the affected files.
|
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.
Quick early comment.
We should not be adding StepAction types in V1. Only add it to v1beta1.
We need to still keep them in v1alpha1 as well otherwise we would be deprecate it immediately which is breaking for the users. For now, we will have it in v1alpha1 and v1beta1 and have conversion between them. Nothing in v1.
We will add it to v1 when we make StepActions stable. At that point, we will remove v1alpha1 and leave v1beta1 and v1. And 9 months after we send out a deprecation notice for v1beta1, we can remove the types from v1beta1.
Happy to discuss more.
f612352
to
5c4cd78
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
32f5a43
to
33dd911
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.
|
/hold cancel |
33dd911
to
fed03dc
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
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.
Minor comments regarding coverage. Otherwise all good!
fed03dc
to
6bb6a73
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@tektoncd/core-collaborators PTAL. |
6bb6a73
to
10bc79c
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
10bc79c
to
c60148d
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.
Generally LGTM - also learned offline from Chitrang that the trusted StepAction
will be something we pursue post-Beta or GA.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chitrangpatel, 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 |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
WG @tektoncd/core-maintainers PTAL for the v0.60 milestone |
Merging this now since everyone has been on board with promoting stepactions to beta. Happy to resolve any friction/comments in a follow-up PR if needed. /lgtm |
Promote StepAction to Beta.
This PR promotes
StepActions
to beta. It adds the necessary types and configs and conversion webhooks. It also updates the internal storage type to usev1beta1
forStepActions
.Changes
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