Skip to content

[WPB-22549] add type field to user#5022

Merged
fisx merged 2 commits intodevelopfrom
WPB-22549-add-type-field-to-user
Feb 11, 2026
Merged

[WPB-22549] add type field to user#5022
fisx merged 2 commits intodevelopfrom
WPB-22549-add-type-field-to-user

Conversation

@fisx
Copy link
Contributor

@fisx fisx commented Feb 11, 2026

https://wearezeta.atlassian.net/browse/WPB-22549

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@fisx fisx requested review from a team as code owners February 11, 2026 09:39
@fisx fisx added the not-ok-to-test Not approved for running tests in CI, this label is ignored if ok-to-test also exists on a PR label Feb 11, 2026
@fisx fisx mentioned this pull request Feb 11, 2026
2 tasks
@supersven
Copy link
Contributor

@fisx I'm wondering how this PR can be Open and not-ok-to-test at the same time. IMHO a green test run is mandatory to approve a PR that touches Haskell files. 🤔

Base automatically changed from WPB-22549-connect-user-to-app to develop February 11, 2026 11:34
@fisx
Copy link
Contributor Author

fisx commented Feb 11, 2026

@fisx I'm wondering how this PR can be Open and not-ok-to-test at the same time. IMHO a green test run is mandatory to approve a PR that touches Haskell files. 🤔

i see it as a parallel thing: PR needs a positive review and green from CI, in any order.

but you may decide to wait for CI, of course. :-)

(or am i being annoying?)

@fisx fisx force-pushed the WPB-22549-add-type-field-to-user branch from 7b325e9 to c22d053 Compare February 11, 2026 13:10
@fisx fisx added ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist and removed not-ok-to-test Not approved for running tests in CI, this label is ignored if ok-to-test also exists on a PR labels Feb 11, 2026
@@ -0,0 +1 @@
Cassandra (`brig.user`) now keeps track of user types, only for newly created users. **Read this paragraph if you have already created apps before their official support:** For existing users and bots, the user type is inferred, but existing apps will show as regular users. Please remove those users from your team and create them again.
Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, I know too little about apps: Is the audience of the changelog the same as the people adding apps? (I.e. sys admins deploying Wire?)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

changelog should be read by everybody who is dealing with wire-server i guess, so yes, team admins adding apps are covered?

of in this case: the site admin should read this and then make sure nobody is using any apps in prod already (which they shouldn't, it hasn't been released yet).

1 -> pure UserTypeBot
2 -> pure UserTypeApp
n -> Left $ "unexpected user type: " ++ show n
fromCql _ = Left "user type: int expected"
Copy link
Contributor

Choose a reason for hiding this comment

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

Have you considered to add the unbound value (_) to the error message? Maybe, it could be helpful in case this goes wrong and needs to be debugged?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i would, but it's like this in all the other cql instances, and i've just go CI green... :-)

Copy link
Contributor

@supersven supersven left a comment

Choose a reason for hiding this comment

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

Besides my nitpicks, LGTM 👍

@fisx fisx merged commit 6bdd7c9 into develop Feb 11, 2026
11 checks passed
@fisx fisx deleted the WPB-22549-add-type-field-to-user branch February 11, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants