-
Notifications
You must be signed in to change notification settings - Fork 332
WPB-27912: Deprecate backgroundEffects feature flag at API v17 #5431
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
Merged
blackheaven
merged 11 commits into
develop
from
gdifolco/WPB-27912-background-effects-ff-deprecation
Aug 18, 2026
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
60e6e51
WPB-27912: Deprecate backgroundEffects feature flag at API v17
blackheaven df0faa2
Hello CI
blackheaven ae0ad03
Update docs/src/developer/reference/config-options.md
blackheaven e021fd1
Update integration/test/Test/FeatureFlags/BackgroundEffects.hs
blackheaven c968bab
Update integration/test/Test/FeatureFlags/BackgroundEffects.hs
blackheaven 7230bb3
WPB-27912: use assertStatus helper and exact [] match in backgroundEf…
blackheaven ff1a829
Hello CI
blackheaven 9e21ab5
Hello CI
blackheaven 3fbc0e7
Hello CI
blackheaven bffb339
WPB-27912: collapse backgroundEffects feature route and attach Haddock
blackheaven 4a052bc
Hello CI
blackheaven File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| * The `backgroundEffects` team feature flag is **deprecated** (WPB-27912). Its | ||
| default is now **enabled and locked**, and the Helm configuration override for | ||
| `backgroundEffects` has been removed from `charts/wire-server`. The flag's | ||
| data type and its public/internal HTTP endpoints are retained for backward | ||
| compatibility; any Helm overrides for `backgroundEffects` are now ignored and | ||
| can be removed. The public/internal HTTP endpoints return 404 at API version | ||
| v17 and remain available through v16; the flag type remains deprecated. The | ||
| aggregate `GET /feature-configs` and `GET /teams/:tid/features` endpoints | ||
| continue to include `backgroundEffects` at all API versions, including v17. |
7 changes: 7 additions & 0 deletions
7
changelog.d/1-api-changes/WPB-27912-background-effects-endpoint
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| The `backgroundEffects` team feature endpoints are deprecated and return 404 for | ||
| clients on API version v17: the public `GET`/`PUT /teams/:tid/features/backgroundEffects` | ||
| and the internal legacy lock `PUT /i/teams/:tid/features/backgroundEffects/(un)?locked`. | ||
| They remain available through v16. The aggregate endpoints | ||
| `GET /feature-configs` and `GET /teams/:tid/features` are unaffected and continue | ||
| to include `backgroundEffects` at all API versions: the aggregate feature list is | ||
| version-agnostic, like other version-gated features such as MLS. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
AFAIK we don't use internal endpoints in a versioned manner. Please check that this doesn't break e.g.
stern.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.
The
Until 'V17on the internal endpoint is safe: internal calls omitX-Wire-API-Version, sogetVersionHeaderdefaults toV0, and the gateV0 >= V17isFalse(never fires). Matches the existingMeetingsPremiumConfigprecedent on the adjacent line; plus, there is no reference instern.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.
@blackheaven Have you considered to completely remove the internal endpoint? Or, who will use the versioned internal endpoint? 🤔