-
Notifications
You must be signed in to change notification settings - Fork 597
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 strict subscriber feature flag #6608
Remove strict subscriber feature flag #6608
Conversation
Hi @creydr. 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 Once the patch is verified, the new status will be reflected by the 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. |
Codecov ReportBase: 81.94% // Head: 81.90% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #6608 +/- ##
==========================================
- Coverage 81.94% 81.90% -0.05%
==========================================
Files 235 235
Lines 11774 11763 -11
==========================================
- Hits 9648 9634 -14
- Misses 1650 1653 +3
Partials 476 476
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. |
/ok-to-test |
2bc0be1
to
b9edc49
Compare
…o GA As per knative/specs#30 the spec was changed from requiring one of `spec.subscriber` or `spec.reply` to be set to require that `spec.subscriber` is set. As part of this change the `strict-subscriber` feature flag was introduced to disable this validation and promoted to beta (enabled by default) in 1.7 (knative#6473). This commit removes this feature flag again so the validation can't be disabled anymore. Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
b9edc49
to
95c7a3c
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: creydr, pierDipi 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 |
@creydr Wanna follow up on this: https://github.com/knative/docs/blob/main/docs/eventing/experimental-features/strict-subscriber.md |
The strict-subscriber feature flag was removed in knative/eventing#6608 so the validation cannot be disabled anymore. This commit adjusts the docs too. Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
The strict-subscriber feature flag was removed in knative/eventing#6608 so the validation cannot be disabled anymore. This commit adjusts the docs too. Signed-off-by: Christoph Stäbler <cstabler@redhat.com> Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
Fixes #5756
As per knative/specs#30 the spec was changed from requiring one of
spec.subscriber
orspec.reply
to be set to require thatspec.subscriber
is set.As part of this change the
strict-subscriber
feature flag was introduced to disable this validation (#5762) and promoted to beta (enabled by default) in 1.7 (#6473).🧹 This commit removes this feature flag again so the validation can't be disabled anymore.
Proposed Changes
strict-subscriber
feature flagPre-review Checklist
Release Note