-
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
Rename deprecated Step and StepTemplate fields #4866
Conversation
/assign @vdemeester |
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
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
Interesting... |
Thanks! I just added them to the exceptions list-- I think we have a good reason here for this OpenAPI violation |
This change renames the deprecated fields of Step and StepTemplate to indicate that they are deprecated, and updates the deprecations table. This commit does not affect JSON keys, meaning that it does not change the user-facing API. It also adds these fields to the ignored OpenAPI rule violations list, as there is a good reason for these field names not to match their JSON keys.
/test pull-tekton-pipeline-alpha-integration-tests |
/lgtm |
/test pull-tekton-pipeline-alpha-integration-tests |
/test pull-tekton-pipeline-integration-tests |
/test pull-tekton-pipeline-unit-tests |
/test all |
1 similar comment
/test all |
/test pull-tekton-pipeline-alpha-integration-tests |
Changes
This change renames the deprecated fields of Step and StepTemplate to indicate
that they are deprecated, and updates the deprecations table. This commit does not
affect JSON keys, meaning that it does not change the user-facing API.
Follow-up for #4737.
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes