feat: Run GCM through FCMv1 HTTP API #455
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This runs GCM messages through the FCMv1 HTTP API (Using existing FCM OAuth credentials, but GCM routing IDs.) This patch is part of an emergency deploy to address 100% GCM failure rates.
Delivery errors for GCM WILL NOT DELETE the GCM route, but will record a metric. This is to prevent potential loss.
It is recommended that this branch be deployed to a canary.
BREAKING CHANGE:
Please alter GCM credentials in
AUTOEND__FCM__CREDENTIALS
These should use the same credential set as main FCM channel.
(e.g.
should become:
Issue: Sync-3943