Files
buzz/migrations/0043_push_gateway_dogfood_profile.sql
Tom Brow 42b42447b0 feat(mobile): prepare buzz-push-gateway for deployment (#7158)
A few things to prepare for deploying the Buzz push gateway as
implemented in #6269:
- Cut `buzz-push-gateway` chart `0.2.0` from the current config
(certificate auth, dogfood client)
- Datadog-compatible metrics
- Align the desired schema, metrics docs, and production ingress
guidance with the current dogfood deployment contract

## Links

- [BUZZ-17: Publish the MVP-compatible gateway
chart](https://linear.app/squareup/issue/BUZZ-17/publish-the-mvp-compatible-gateway-chart)
- [BUZZ-26: Add Datadog-compatible push-gateway metrics and correct
source
drift](https://linear.app/squareup/issue/BUZZ-26/add-datadog-compatible-push-gateway-metrics-and-correct-source-drift)

---------

Signed-off-by: Tom Brow <tomb@block.xyz>
Co-authored-by: Codex <noreply@openai.com>
2026-09-01 12:19:48 -07:00

20 lines
807 B
SQL

-- The internal MVP accepts only the dogfood application profile. The legacy
-- profile names encoded APNs transport environment rather than a verified
-- application identity, so they cannot be mapped safely to dogfood authority.
-- Retire their delegations and installations before narrowing the constraint.
DELETE FROM push_gateway_delegations
WHERE installation_id IN (
SELECT id
FROM push_gateway_installations
WHERE app_profile <> 'buzz-ios-dogfood'
);
DELETE FROM push_gateway_installations
WHERE app_profile <> 'buzz-ios-dogfood';
ALTER TABLE push_gateway_installations
DROP CONSTRAINT push_gateway_installations_app_profile_check;
ALTER TABLE push_gateway_installations
ADD CONSTRAINT push_gateway_installations_app_profile_check
CHECK (app_profile = 'buzz-ios-dogfood');