-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
CodePipeline: ECR as Source Action #7012
Comments
So sad :-( Any suggested workarounds to this? |
With pipelines becoming a standard, this is has become a big issue. This is going to force many to move to the CDK. Is this on the roadmap to be addressed? 20 months and still nothing... given the lack of tags I assume there is no movement on this? |
This is still busted. Creating |
For anyone who needs to Terraform the CloudWatch Event Rule + Target, here is a TF |
@tmegow Thank you for this, having the Since I prefer to keep things as much in HCL as possible for readability, I made this change to the event rule (I added the IAM permissions to existing roles and policies):
|
Closing this issue as I have verified that |
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. |
Community Note
Description
ECR was recently added to CodePipeline as a Source Stage/Action (link). The provider allows to use the ECR as Source but the CloudWatch Event configuration is missing, so the pipeline is never triggered.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: