Skip to content

Depend on PostgreSQL token server if building PostgreSQL sync server#2194

Open
ntninja wants to merge 2 commits intomozilla-services:masterfrom
ntninja:fix-tokenserver-postgresql
Open

Depend on PostgreSQL token server if building PostgreSQL sync server#2194
ntninja wants to merge 2 commits intomozilla-services:masterfrom
ntninja:fix-tokenserver-postgresql

Conversation

@ntninja
Copy link
Copy Markdown

@ntninja ntninja commented Apr 6, 2026

Description

Building the PostgreSQL syncserver should also build the PostgreSQL token server, currently one gets a mixed build which is kinda weird and pretty annoying for packaging.

Testing

How should reviewers test?

$ cd syncserver
$ cargo build --no-default-features -F pgsql,py_verifier

Should build the PostgreSQL Sync- and Token-Server.
Not, the PostgreSQL Sync-Server with the MySQL Token-Server.

@pjenvey
Copy link
Copy Markdown
Member

pjenvey commented Apr 7, 2026

This looks reasonable but this breaks some CI assumptions within our Dockerfile, where the default build arg of TOKENSERVER_DATABASE_BACKEND=mysql currently doesn't emit any tokenserver backend --feature, assuming tokenserver-db defaults to mysql.

I think simplifying that to always specifying --feature=tokenserver-db/$TOKENSERVER_DATABASE_BACKEND as is done for the syncstorage-db backend should fix this

ntninja added 2 commits April 8, 2026 22:02
…ckend when testing

As of the previous commit, the MySQL TokenServer backend is only enabled if
SyncServer is also using MySQL or Spanner, otherwise it needs to be enabled
explicitely.
@ntninja ntninja force-pushed the fix-tokenserver-postgresql branch from 2a298b3 to 9c92cf7 Compare April 8, 2026 20:02
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