feat(hybrid-cloud): Ensure release registry cache is available in control #86400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
Scope: Backend
markstory
approved these changes
Mar 5, 2025
philipphofmann
pushed a commit
that referenced
this pull request
Mar 6, 2025
…trol (#86400) When [setting up the AWS integration in Sentry](https://docs.sentry.io/organization/integrations/cloud-monitoring/aws-lambda/) and trying to automatically add the lambda layer to lambda functions the underlying code encounters an empty release-registry cache: https://sentry.sentry.io/issues/5289437499/events/f3e461d3164a442587c3f9da8ef86255/ This happens from this view:  But it is possible to do from this view:  From the linked issue above, it looks like that code runs in the control silo, but the task to populate the cache with release-registry data is only running for region silos. This PR adds the celery task to the control queue. Related: #85322, #86365 Might stem from: #53038
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When setting up the AWS integration in Sentry and trying to automatically add the lambda layer to lambda functions the underlying code encounters an empty release-registry cache: https://sentry.sentry.io/issues/5289437499/events/f3e461d3164a442587c3f9da8ef86255/
This happens from this view:
But it is possible to do from this view:
From the linked issue above, it looks like that code runs in the control silo, but the task to populate the cache with release-registry data is only running for region silos.
This PR adds the celery task to the control queue.
Related: #85322, #86365
Might stem from: #53038