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

feat: multitenant blocklist support #1450

Merged
merged 11 commits into from
Jan 29, 2025
Merged

Conversation

vishalnarkhede
Copy link
Contributor

@vishalnarkhede vishalnarkhede commented Jan 27, 2025

CLA

  • I have signed the Stream CLA (required).
  • Code changes are tested

Description of the changes, What, Why and How?

Changelog

This PR introduces team parameter on blocklist related endpoints. Basically customer should be able to create blocklist per team (multitenant). Until now, blocklist was uniquely identified by "name". Moving forward, blocklist will be identified by (name, team). This is backwards compatible change, since team for existing blocklist will remain as "".

Backend changes are here: https://github.com/GetStream/chat/pull/7904

Copy link
Contributor

github-actions bot commented Jan 27, 2025

Size Change: +1.21 kB (+0.26%)

Total Size: 469 kB

Filename Size Change
dist/browser.es.js 102 kB +305 B (+0.3%)
dist/browser.full-bundle.min.js 57.4 kB +5 B (+0.01%)
dist/browser.js 103 kB +296 B (+0.29%)
dist/index.es.js 102 kB +304 B (+0.3%)
dist/index.js 103 kB +296 B (+0.29%)

compressed-size-action

@vishalnarkhede vishalnarkhede changed the title [MOD-337] Multitenant blocklist feat: multitenant blocklist support Jan 29, 2025
@vishalnarkhede vishalnarkhede merged commit e06d1bb into master Jan 29, 2025
6 checks passed
@vishalnarkhede vishalnarkhede deleted the multitenant-blocklist branch January 29, 2025 14:32
@github-actions github-actions bot mentioned this pull request Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants