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 strict subscriber feature flag #6608

Merged

Conversation

creydr
Copy link
Member

@creydr creydr commented Nov 14, 2022

Fixes #5756

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 (#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

  • Remove strict-subscriber feature flag
  • Promote strict subscriber validation to GA

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

Remove the possibility to disable strict subscriber validation.
When the reply field is specified without a subscriber, the reply field won't be used as a subscriber by default and the subscriber validation will fail.

@knative-prow knative-prow bot added 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 Nov 14, 2022
@knative-prow
Copy link

knative-prow bot commented Nov 14, 2022

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 /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.

@knative-prow knative-prow bot added the area/test-and-release Test infrastructure, tests or release label Nov 14, 2022
@codecov
Copy link

codecov bot commented Nov 14, 2022

Codecov Report

Base: 81.94% // Head: 81.90% // Decreases project coverage by -0.04% ⚠️

Coverage data is based on head (95c7a3c) compared to base (82bf83c).
Patch coverage: 100.00% of modified lines in pull request are covered.

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              
Impacted Files Coverage Δ
pkg/apis/messaging/v1/subscription_validation.go 87.71% <100.00%> (-1.99%) ⬇️
pkg/reconciler/subscription/subscription.go 83.33% <0.00%> (-0.80%) ⬇️

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.

@pierDipi
Copy link
Member

/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 Nov 15, 2022
@creydr creydr changed the title 🧹 Remove strict subscriber feature flag Remove strict subscriber feature flag Nov 15, 2022
@creydr creydr force-pushed the remove-strict-subscriber-feature-flag branch from 2bc0be1 to b9edc49 Compare November 16, 2022 11:29
…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>
@creydr creydr force-pushed the remove-strict-subscriber-feature-flag branch from b9edc49 to 95c7a3c Compare November 16, 2022 11:34
Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 16, 2022
@knative-prow
Copy link

knative-prow bot commented Nov 16, 2022

[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 /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 Nov 16, 2022
@knative-prow knative-prow bot merged commit e8fec2a into knative:main Nov 16, 2022
@matzew
Copy link
Member

matzew commented Nov 18, 2022

@creydr Wanna follow up on this: https://github.com/knative/docs/blob/main/docs/eventing/experimental-features/strict-subscriber.md

creydr added a commit to creydr/knative-docs that referenced this pull request Nov 18, 2022
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>
@creydr
Copy link
Member Author

creydr commented Nov 18, 2022

knative-prow bot pushed a commit to knative/docs that referenced this pull request Nov 18, 2022
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>
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. area/test-and-release Test infrastructure, tests or release 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/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.

[Experimental] Spec non-compliance: spec.subscriber MUST be set
3 participants