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

Remove the template.Name field #898

Merged
merged 1 commit into from
Jan 13, 2021

Conversation

MarcelMue
Copy link
Member

@MarcelMue MarcelMue commented Jan 13, 2021

Changes

Simple PR which removes the already deprecated field.

Closes: #791

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Release Notes

action required: The Template.Name field has been removed from the Trigger Spec. Please use Template.Ref instead.

@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 13, 2021
@tekton-robot
Copy link

Hi @MarcelMue. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@MarcelMue
Copy link
Member Author

I did a quick skim of the docs but couldn't find anything referencing this name field. I could have very well missed something, so please double check if docs changes are necessary.

@dibyom
Copy link
Member

dibyom commented Jan 13, 2021

/ok-to-test

@tekton-robot tekton-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 13, 2021
@dibyom
Copy link
Member

dibyom commented Jan 13, 2021

I did a quick skim of the docs but couldn't find anything referencing this name field. I could have very well missed something, so please double check if docs changes are necessary.

The field was deprecated a while back so we might have removed it from the docs. I'll take a look.

@tekton-robot
Copy link

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

File Old Coverage New Coverage Delta
pkg/apis/triggers/v1alpha1/trigger_validation.go 94.5% 94.2% -0.3
pkg/template/resource.go 98.3% 100.0% 1.7

@tekton-robot
Copy link

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

File Old Coverage New Coverage Delta
pkg/apis/triggers/v1alpha1/trigger_validation.go 94.5% 94.2% -0.3
pkg/template/resource.go 98.3% 100.0% 1.7

@MarcelMue MarcelMue force-pushed the remove-template-name branch from acb1b71 to fd6afe2 Compare January 13, 2021 18:40
@tekton-robot
Copy link

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

File Old Coverage New Coverage Delta
pkg/apis/triggers/v1alpha1/trigger_validation.go 94.5% 94.2% -0.3
pkg/template/resource.go 98.3% 100.0% 1.7

@dibyom
Copy link
Member

dibyom commented Jan 13, 2021

Nice. Thanks!

One small thing: Can we update the release note to contain an action-required e.g.

action required: The Template.Name field has been removed from the Trigger Spec. Please use Template.Ref instead.

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2021
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 13, 2021
@tekton-robot tekton-robot merged commit 58b4655 into tektoncd:master Jan 13, 2021
@tekton-robot tekton-robot added release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Jan 13, 2021
@MarcelMue MarcelMue deleted the remove-template-name branch January 13, 2021 20:53
@MarcelMue
Copy link
Member Author

Nice. Thanks!

One small thing: Can we update the release note to contain an action-required e.g.

action required: The Template.Name field has been removed from the Trigger Spec. Please use Template.Ref instead.

/approve
/lgtm

Should be done - I guess it's still okay with an already merged PR.

@cameronbraid
Copy link

How do I workaround this ?

❯ kubectl  delete eventlistener gitea-backup
Error from server (BadRequest): admission webhook "validation.webhook.triggers.tekton.dev" denied the request: decoding request failed: cannot decode incoming old object: json: unknown field "name"

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. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove template.Name field
4 participants