Skip to content
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]: aws_pipes_pipe > target_parameters > ecs_task_parameters > overrides > container_override > name is not optional #37658

Closed
HikaruEgashira opened this issue May 23, 2024 · 2 comments
Labels
bug Addresses a defect in current functionality. service/pipes Issues and PRs that pertain to the pipes service.

Comments

@HikaruEgashira
Copy link

HikaruEgashira commented May 23, 2024

Terraform Core Version

v1.5.7

AWS Provider Version

5.49.0

Affected Resource(s)

aws_pipes_pipe

Expected Behavior

name is required

Actual Behavior

name is optional

Relevant Error/Panic Output Snippet

no error

Terraform Configuration Files

resource "aws_pipes_pipe" "xxx" {
  name     = "xxx"
  role_arn = aws_iam_role.xxx.arn
  source   = aws_sqs_queue.xxx.arn
  target   = aws_ecs_cluster.xxx.arn

  target_parameters {
    ecs_task_parameters {
      task_count          = 1
      task_definition_arn = aws_ecs_task_definition.xxx.arn
      launch_type         = "FARGATE"
      platform_version    = "LATEST"
      network_configuration {
        aws_vpc_configuration {
          subnets          = [aws_subnet.xxx.id]
          security_groups  = [aws_security_group.xxx.id]
          assign_public_ip = "DISABLED"
        }
      }
      overrides {
        container_override {
          name = "xxx" # This parameter is optional but this value required
          environment {
            name  = "MESSAGE"
            value = "$.body"
          }
        }
      }
    }
  }
}

Steps to Reproduce

always

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/pipes_pipe#container_override
https://docs.aws.amazon.com/ja_jp/AmazonECS/latest/APIReference/API_ContainerOverride.html
aws/aws-sdk-go#2553

Would you like to implement a fix?

Yes

@HikaruEgashira HikaruEgashira added the bug Addresses a defect in current functionality. label May 23, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/pipes Issues and PRs that pertain to the pipes service. label May 23, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label May 23, 2024
@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label May 24, 2024
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/pipes Issues and PRs that pertain to the pipes service.
Projects
None yet
Development

No branches or pull requests

2 participants