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

Removes the deprecated DeadLetterChannel in ChannelableStatus #6722

Merged
merged 2 commits into from
Mar 2, 2023

Conversation

vishal-chdhry
Copy link
Member

@vishal-chdhry vishal-chdhry commented Feb 4, 2023

Signed-off-by: Vishal Choudhary sendtovishalchoudhary@gmail.com

Fixes #6720

Proposed Changes

Pre-review Checklist

  • At least 80% unit test coverage
  • E2E tests for any new behavior
  • Docs PR for any user-facing impact
  • Spec PR for any new API feature
  • Conformance test for any change to the spec

Release Note

removes deprecated DeadLetterChannel in favor of DeliveryStatus

Docs

Signed-off-by: Vishal Choudhary <sendtovishalchoudhary@gmail.com>
@knative-prow knative-prow bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 4, 2023
@knative-prow
Copy link

knative-prow bot commented Feb 4, 2023

Hi @vishal-chdhry. Thanks for your PR.

I'm waiting for a knative 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.

@vishal-chdhry
Copy link
Member Author

vishal-chdhry commented Feb 4, 2023

@aliok I had the following doubts

  • There are a few references of DeadLetterChannel in v1beta1 as well
    type DeliveryStatus struct {
    // DeadLetterChannel is a KReference that is the reference to the native, platform specific channel
    // where failed events are sent to.
    // +optional
    DeadLetterChannel *duckv1.KReference `json:"deadLetterChannel,omitempty"`
    // DeadLetterChannel is a KReference and is set by the channel when it supports native error handling via a channel
    // Failed messages are delivered here.
    // +optional
    DeadLetterChannel *duckv1.KReference `json:"deadLetterChannel,omitempty"`
    but these two are not deprecated, should i remove them too? I have verified that these two are not in use.
  • How do I send the emails to knative users email list?
  • What is the command for codegen, i could not find the makefile

@vishal-chdhry
Copy link
Member Author

/hold

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 4, 2023
@vishal-chdhry vishal-chdhry changed the title Removes the deprecated DeadLetterChannel in ChannelableStatus #6720 Removes the deprecated DeadLetterChannel in ChannelableStatus Feb 4, 2023
@aliok
Copy link
Member

aliok commented Feb 4, 2023

@vishal-chdhry

There are a few references of DeadLetterChannel in v1beta1 as well

No, the ones in v1beta1 need to stay.

How do I send the emails to knative users email list?

Here's the link to the Google Group: https://groups.google.com/g/knative-users
There is also knative-dev: https://groups.google.com/g/knative-dev

I think sending an email to both makes more sense.

What is the command for codegen, i could not find the makefile

You can run ./hack/update-codegen.sh. That will regenerate the zz_generated.deepcopy.go file relevant here.

@aliok
Copy link
Member

aliok commented Feb 4, 2023

/assign

Assigning myself as a reviewer

@aliok
Copy link
Member

aliok commented Feb 4, 2023

/ok-to-test

@knative-prow knative-prow bot 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 Feb 4, 2023
@aliok
Copy link
Member

aliok commented Feb 4, 2023

Ah, one more thing. Can you also fill the Release Note section in the PR description that this field is removed? It would be nice to note that in the release notes. For example, #6665 has a release note that is shown in the 1.9.2 release

Signed-off-by: Vishal Choudhary <sendtovishalchoudhary@gmail.com>
@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 4, 2023
@codecov
Copy link

codecov bot commented Feb 4, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (8b7551c) 80.53% compared to head (936956c) 80.53%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6722   +/-   ##
=======================================
  Coverage   80.53%   80.53%           
=======================================
  Files         236      236           
  Lines       12100    12100           
=======================================
  Hits         9745     9745           
  Misses       1867     1867           
  Partials      488      488           
Impacted Files Coverage Δ
pkg/apis/duck/v1/channelable_types.go 96.61% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@aliok
Copy link
Member

aliok commented Feb 6, 2023

There are some failures in some Github actions.

  • Downstream / Unit Test (eventing-natss, knative-sandbox): We should simply create a ticket in https://github.com/knative-sandbox/eventing-natss, referencing this PR and the ticket
  • KinD e2e tests / e2e tests (v1.25.3, ./test/experimental): Needs to be checked
  • KinD e2e tests / e2e tests (v1.25.3, ./test/e2e): Needs to be checked
  • KinD e2e tests / e2e tests (v1.25.3, ./test/rekt/...): Needs to be checked

Let's first do the sanity check for the last 3. Are they passing on other PRs? Or, are they really getting broken by this PR?

@vishal-chdhry
Copy link
Member Author

we have failing tests in this PR as well #6696

@aliok
Copy link
Member

aliok commented Feb 6, 2023

Are they failing the same way?
Also KinD e2e tests / e2e tests (v1.25.3, ./test/e2e) is not failing there. I am triggering these again now

@vishal-chdhry
Copy link
Member Author

@aliok Yes both have the same error

runtime.main
	/opt/hostedtoolcache/go/1.18.10/x64/src/runtime/proc.go:250
--- PASS: ExampleWithRetry (0.00s)
PASS
ok  	knative.dev/eventing/test/rekt/resources/trigger	0.271s
FAIL
Error: Process completed with exit code 1.

@aliok
Copy link
Member

aliok commented Feb 7, 2023

ok, then we're all good. Can you unhold after a week from your email you sent to the community?

@aliok
Copy link
Member

aliok commented Feb 7, 2023

/lgtm
/approve

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Feb 7, 2023
@knative-prow
Copy link

knative-prow bot commented Feb 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, Vishal-Chdhry

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

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 7, 2023
@matzew
Copy link
Member

matzew commented Feb 7, 2023

I am OK w/ this direct removal, since the API has been deprecated in 2021, and was meant to be removed. So we are OK in NOT bumping to v2alpha1 ... 😄

Usually we should do the migration etc.

Note: NATSS downstream has issues, we just ignore this.

@matzew
Copy link
Member

matzew commented Feb 7, 2023

Thanks for the contribution, @vishal-chdhry

@vishal-chdhry
Copy link
Member Author

vishal-chdhry commented Feb 7, 2023

@matzew I have opened an issue in natss regarding this knative-extensions/eventing-natss#388.
Should I go ahead and remove the references to DeadLetterChannel there as well??

@pierDipi
Copy link
Member

pierDipi commented Feb 8, 2023

/cc aliok
/uncc

@knative-prow knative-prow bot requested review from aliok and removed request for pierDipi February 8, 2023 11:20
@aliok
Copy link
Member

aliok commented Feb 8, 2023

Should I go ahead and remove the references to DeadLetterChannel there as well??

@vishal-chdhry I don't know the latest status of Nats repository. If you think you can fix the issue there, feel free and give it a try.

@aliok
Copy link
Member

aliok commented Mar 2, 2023

/unhold

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 2, 2023
@knative-prow knative-prow bot merged commit 7d7df2d into knative:main Mar 2, 2023
vishal-chdhry added a commit to vishal-chdhry/eventing that referenced this pull request Mar 14, 2023
…e#6722)

Signed-off-by: Vishal Choudhary <sendtovishalchoudhary@gmail.com>

Fixes knative#6720 

<!-- Please include the 'why' behind your changes if no issue exists -->

## Proposed Changes

<!-- Please catagorize your changes:
- 🎁 Add new feature
- 🐛 Fix bug
- 🧹 Update or clean up current behaviour
- 🗑️ Remove feature or internal logic
-->

-  🗑️ Remove feature or internal logic
- removes deprecated `DeadLetterChannel`
https://github.com/knative/eventing/blob/main/pkg/apis/duck/v1/channelable_types.go#L70-L74

### Pre-review Checklist

<!-- If these boxes are not checked, you will be asked to complete these
requirements or explain why they do not apply to your PR. -->

- [x] **At least 80% unit test coverage**
- [x] **E2E tests** for any new behavior
- [ ] **Docs PR** for any user-facing impact
- [ ] **Spec PR** for any new API feature
- [ ] **Conformance test** for any change to the spec

**Release Note**

<!--
:page_facing_up: If this change has user-visible impact, write a release
note in the block
below. Include the string "action required" if additional action is
required of
users switching to the new release, for example in case of a breaking
change.

Write as if you are speaking to users, not other Knative contributors.
If this
change has no user-visible impact, no release note is needed.
-->

```release-note
removes deprecated DeadLetterChannel in favor of DeliveryStatus
```


**Docs**

<!--
:book: If this change has user-visible impact, link to an issue or PR in
https://github.com/knative/docs.
-->

---------

Signed-off-by: Vishal Choudhary <sendtovishalchoudhary@gmail.com>
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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get rid of the deprecated DeadLetterChannel in ChannelableStatus
4 participants