Eventarc dead_letter_topic configuration

[SilverCory]

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.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

Allow configuring and setting the dead_letter_topic for EventArc, along with all the other configuration options for the Subscription

New or Affected Resource(s)

• google_eventarc_trigger
• google_pubsub_subscription

Potential Terraform Configuration

resource "google_eventarc_trigger" "events-trigger" {
  name     = "trigger"
  location = var.region
  project  = var.project

  matching_criteria {
    ...
  }

  transport {
    pubsub {
      subscription {
        message_retention_seconds = 50000
        expiry = 0
        dead_letter {
          topic = google_pubsub_topic.topic.id
          delivery_attempts = 15
        }
      }
    }
  }

  destination {
    ...
  }
}

References

No response

b/331667689
b/331667948
b/331668569

[shuyama1]

Thanks for filing the ticket!
It doesn't look like the API supports this feature at this point. The subscription field is output-only and users can't specify this field explicitly. We can't add this to Terraform until the API supports it.

[SilverCory]

Thanks @shuyama1.

A bit iffy but if we get the subscriber from the response we can update it. It would be a multi-step process in the provider if it was done that way.

CreateEventArcTrigger(), UpdateSubscription(eventArcTrigger.transport.subscription)