Terraform-provider-aws: CodePipeline: ECR as Source Action

Created on 2 Jan 2019  路  2Comments  路  Source: hashicorp/terraform-provider-aws

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

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)

  • aws_codepipeline

Potential Terraform Configuration

resource "aws_codepipeline" "this" {
  name     = "test-pipeline"
  role_arn = "${aws_iam_role.codepipeline.arn}"

  artifact_store {
    location = "${aws_s3_bucket.this.bucket}"
    type     = "S3"
  }

  stage {
    name = "Source"

    action {
      name             = "Source"
      category         = "Source"
      owner            = "AWS"
      provider         = "ECR"
      version          = "1"
      output_artifacts = ["source"]

      configuration {
        RepositoryName = "${aws_ecr_repository.this.name}"
        ImageTag       = "latest"
      }
    }
  }
}

References

  • N/A

  • enhancement serviccodepipeline

    Most helpful comment

    So sad :-( Any suggested workarounds to this?

    All 2 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?

    Was this page helpful?
    0 / 5 - 0 ratings