Repository navigation
feat: support shared ECS image registry mode - #80
Conversation
Allow ECS deployments to pull platform images from the shared leopard-platform repository while preserving environment repositories by default.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (9)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details🔇 Additional comments (9)
WalkthroughThe change adds configurable ECS registry repository templates. The default template is Suggested reviewers: Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to No actionable merge-blocking risk remains after confirming that slashless image values behave as before. Caution Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional.
❌ Failed checks (1 error, 1 warning)
✅ Passed checks (2 passed)
Full details: Title checkExplanation The title identifies ECS image registry changes, but it claims support for a Full details: Docstring CoverageExplanation Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 7 files. (2 skipped: 2 unsupported.)
Comment |
Remove platform-specific registry configuration and keep shared image resolution independent of repository naming.
…feat-shared-registry-mode
Replace registry modes with a template that preserves environment-specific repositories by default and supports custom service paths.
Use registry.repository as the public template setting while preserving its existing expansion and default path.
50bccbd
Summary
registry.mode: sharedfor ECS task definitions that pull<ECR_URL>/leopard-platform/<app>:<tag>ops configTest plan
go test ./...