feat: add Assume Role ARN field for cross-account ECR registries#3085
Conversation
Added assumeRoleArn to the ECR registry form and API payload, allowing users to configure cross-account ECR access via STS AssumeRole. The field is available for both EC2 IAM Role and User auth modes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
There was a problem hiding this comment.
Pull request overview
Adds support for configuring cross-account AWS ECR access by introducing an optional Assume Role ARN field in the container registry (ECR) configuration UI and including it in the registry payload sent to the backend.
Changes:
- Extended
RegistryPayloadTypeto include an optionalassumeRoleArn. - Plumbed
assumeRoleArnthrough the Docker registry list → form props/state → API payload construction. - Added an ECR-only form input for “Assume Role ARN (cross-account)” (shown for both EC2 IAM Role and User auth modes, and only for private ECR storage mode).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/config/constants.ts |
Adds assumeRoleArn?: string to the registry payload type. |
src/components/dockerRegistry/Docker.tsx |
Adds form state + UI field for AssumeRole ARN and includes it in the ECR payload. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
|
Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n |
|



Added assumeRoleArn to the ECR registry form and API payload, allowing users to configure cross-account ECR access via STS AssumeRole. The field is available for both EC2 IAM Role and User auth modes.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes https://github.com/devtron-labs/sprint-tasks/issues/2868
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: