chore: promote dev to production - #52652
Merged
Merged
Conversation
This branch was successfully deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue for this PR
Legacy lake retirement in #52515.
Type of change
What does this PR do?
Promote the verified development cleanup to production. Remove the seven retired S3 lake resources while preserving the deployed VPC, cluster and R2 Stats service.
All 20,772,423,321 production raw records are verified in R2, alongside development history and recovered deliveries. The inference R2 reader and its normal hourly and mixed-source Requests refreshes are verified; legacy AWS bindings and repository credentials are removed. Manual historical refreshes remain on hold.
How did you verify your code works?
All cleanup PR checks pass. Development deployment at
1ddb0873aee50d209d1a8d7f91b89c5daf692d49succeeded; AWS confirms all seven development lake resources are gone. Shared Stats service, cluster and VPC identities are preserved, and the services read R2. Production preview adds the same seven deletions without replacing those shared resources.Screenshots / recordings
No UI change.
Checklist