-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: ECR repository policy creation fails when using newly created IAM role #39064
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I have a similar problem with Lightsail Container and ECR. ECR repo created through terraform, Lightsail through console. Connecting the container to the private repo via AWS management console produces this error:
|
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.67.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.9.5
AWS Provider Version
5.64.0
Affected Resource(s)
Expected Behavior
terraform apply
should succeed.Actual Behavior
Applying the repository policy fails the first time. Running it a second time succeeds.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
terraform apply
Debug Output
https://gist.github.com/imre-kerr-sb1/79968926a388f95da1bd6c994eaf57a1
Panic Output
No response
Important Factoids
No response
References
This is a regression of #1164, which was fixed in #1165. The retry logic checks the error message:
But AWS has since changed the error message to be more specific. ('Invalid repository policy provided' replaced with 'Principal not found').
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: