docs: record the retirement of the superseded artefact stores - #50
Merged
Conversation
The pre-migration ECR repo and SAM-managed S3 bucket were deleted on 2026-08-25, along with their owning stacks, once the first CI deploy against the bootstrap stores was confirmed to land its artefacts there and nowhere else. Records what the deletion actually required (ECR images removed first because the companion stack's repository sets neither EmptyOnDelete nor a retain policy; all 158 S3 object versions and delete markers purged, since `aws s3 rm --recursive` only writes delete markers on a versioned bucket) and the one consequence worth knowing: the stack can no longer roll back to a version deployed before that date. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Follow-up to #49. The pre-migration artefact stores were deleted on 2026-08-25 once the first CI deploy against the bootstrap stores was confirmed, so the "Superseded resources" section in
.claude/rules/build-test-deploy.mdnow describes resources that no longer exist.What was deleted
nzimageapi40221342/jp2converterfunctione92cbfdcrepo+ stacknzimageapi-40221342-CompanionStack. The 3 remaining images had to go first: the companion stack'sAWS::ECR::Repositorysets neitherEmptyOnDeletenor a retain policy, so the stack delete would have failed with the repo non-empty.aws-sam-cli-managed-default-samclisourcebucket-tfqwkahyri86+ stackaws-sam-cli-managed-default. 158 object versions and delete markers were purged first, becauseaws s3 rm --recursiveonly writes delete markers on a versioned bucket and leaves the stack delete blocked.The account now holds exactly one ECR repository and one S3 bucket, both from
infra/bootstrap.yaml.Consequence recorded
CloudFormation can no longer roll the
nzimageapistack back to a version deployed before 2026-08-25 — those templates and images are gone. Everything from that date on is in the bootstrap stores under their retention policies.Verified after deletion:
/imagereturned 200 on 20/20 requests.🤖 Generated with Claude Code