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

Incorrect maximum for ses_event_destination #6689

Closed
david-wells-1 opened this issue Dec 3, 2018 · 3 comments · Fixed by #6690
Closed

Incorrect maximum for ses_event_destination #6689

david-wells-1 opened this issue Dec 3, 2018 · 3 comments · Fixed by #6690
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ses Issues and PRs that pertain to the ses service.
Milestone

Comments

@david-wells-1
Copy link
Contributor

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

Terraform Version

Terraform v0.11.10

Affected Resource(s)

  • resource_aws_ses_event_destination

Terraform Configuration Files

resource "aws_ses_configuration_set" "dev" {
  name = "hcom"

  lifecycle {
    create_before_destroy = "true"
  }
}

resource "aws_ses_event_destination" "cloudwatch-all" {
  name                   = "dev-all"
  configuration_set_name = "${aws_ses_configuration_set.dev.name}"
  enabled                = true
  matching_types         = ["bounce", "complaint", "reject", "send", "delivery"]

  cloudwatch_destination = {
    default_value  = "${aws_ses_configuration_set.dev.name}"
    dimension_name = "ses:configuration-set"
    value_source   = "messageTag"
  }

  cloudwatch_destination = {
    default_value  = "default"
    dimension_name = "ses:caller-identity"
    value_source   = "messageTag"
  }

  cloudwatch_destination = {
    default_value  = "default"
    dimension_name = "ses:from-domain"
    value_source   = "messageTag"
  }

  cloudwatch_destination = {
    default_value  = "default"
    dimension_name = "ses:source-ip"
    value_source   = "messageTag"
  }

  cloudwatch_destination = {
    default_value  = "default"
    dimension_name = "ses:outgoing-ip"
    value_source   = "messageTag"
  }

  cloudwatch_destination = {
    default_value  = "default"
    dimension_name = "to"
    value_source   = "emailHeader"
  }
}

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

  1. terraform apply

Important Factoids

References

  • #0000
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/ses Issues and PRs that pertain to the ses service. labels Dec 3, 2018
@bflad bflad added this to the v1.51.0 milestone Dec 3, 2018
@bflad
Copy link
Contributor

bflad commented Dec 3, 2018

Support for multiple cloudwatch_destination configuration blocks has been merged and will release with version 1.51.0 of the AWS provider, in the next day or two. 👍

@bflad
Copy link
Contributor

bflad commented Dec 5, 2018

This has been released in version 1.51.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

@ghost
Copy link

ghost commented Apr 1, 2020

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ses Issues and PRs that pertain to the ses service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants