KamoCRM

Add the RingCentral JWT and direct-number columns

FeatureInitializerService
Shipped
26 ஆகஸ்ட், 2026 அன்று 1:02 AM UTC
Author
Kamo
Commit
839c259

Order 0, because the shared-library entities map both columns from the moment this build starts: every runner that loads a PhoneExtension or a MemberVoipOAuthToken through JPA emits them in its SELECT, so a runner ordered later would never execute — an earlier one dies on "column ... does not exist" and takes the run down first. Nothing here reads an entity, so there is nothing for it to wait behind. Both statements are ADD COLUMN IF NOT EXISTS and both columns are nullable, so re-running is a no-op and no row is rewritten. The leftover OAuth rows are deliberately left in place: status is read from jwt_assertion now, so a stale row reports "not connected" rather than claiming a member is set up when they are not. The columns were also applied directly to Yugabyte ahead of the VOIPService deploy — pushing this repo ships nothing on its own.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing