chore(ci): publish tenant image to staging ecr via ssot publisher #1649
Reference in New Issue
Block a user
Delete Branch "chore/publish-staging-ecr-with-ssot-publisher"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary\n- remove staging AWS access-key secrets from publish-workspace-server-image\n- always tag the tenant image for both primary ECR and staging ECR in the same build\n- rely on the staging ECR repository policy that grants the SSOT-managed primary publisher principal push access\n\n## IAM / ECR setup\n- staging ECR repo policy now grants arn:aws:iam::153263036946:user/molecule-cp push/read actions on 004947743811/molecule-ai/platform-tenant only\n- no persistent staging AWS access keys were created\n- validated staging image exists: 004947743811.dkr.ecr.us-east-2.amazonaws.com/molecule-ai/platform-tenant:staging-498ce4e and :staging-latest\n\n## Tests\n- python3 .gitea/scripts/lint-workflow-yaml.py --workflow-dir .gitea/workflows\n- python3 -m pytest tests/test_lint_workflow_yaml.py -q\n- git diff --check\n\n## Review\n- self-reviewed with five-axis checklist; no findings. Broader SSOT debt remains in unrelated AWS workflows and should be handled separately.
Founder-authorized review bypass for CI workflow-only SSOT/staging ECR change. Local workflow lint and focused tests passed; staging ECR push was validated.
Founder-authorized review bypass for CI workflow-only SSOT/staging ECR change. Local workflow lint and focused tests passed; staging ECR push was validated.