feat(uptime): Use UptimeSubscriptionRegion
to direct config updates to the appropriate region topic
#82441
+184
−86
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 uses
UptimeSubscriptionRegion
to determine which regions a subscription should be run in, and sends config updates to each of those regions.Changes the config producer to use
UPTIME_REGIONS
to route messages to the appropriate topic, instead of being hardcoded.Also includes hacks to use the default region when no regions exist for a subscription. This is temporary until we start writing
UptimeSubscriptionRegion
rows.We should wait until https://github.com/getsentry/ops/pull/13422 is merged before going ahead, so that regions are appropriately configured in production.