Repository navigation
Conversation
Slim images now mirror to public.ecr.aws/supabase-registry/cli/<service>, pushed with the `ecr-push-public-cli` role from the central registry account instead of PROD_AWS_ROLE. The registry stack owns the repositories, so the workflow checks the destination exists and points at the enrollment file when it does not, rather than creating it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SNJube4L1c7kHu88o2JXZG
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
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.
Summary
Moves the slim image ECR Public mirror to the central registry account.
public.ecr.aws/supabase/cli/<service>topublic.ecr.aws/supabase-registry/cli/<service>.mirror-slim-image.ymlassumes theecr-push-public-clirole in the registry account instead ofPROD_AWS_ROLE, with a per-run session name.ensure-repobecomescheck-repo: it only confirms the repository exists, and when it doesn't, it fails with the enrollment file to edit. It no longer tries to create the repository.No CLI release pulls from the ECR mirror yet (the client still reads
ghcr.io/supabase/cli), so changing the prefix doesn't affect shipped users.Merge order:
supabase-registrypublic alias is claimed.ECR_MIRROR_PREFIXdefault in supabase/slim-services land together.validaterejects any payload destination that doesn't match the derived one.Linked issue
None.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SNJube4L1c7kHu88o2JXZG
Generated by Claude Code