google_cloudfunctions_function does not support setting dead letter queue on the topic

[jonesaaronj]

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 the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

When creating a google cloud function with a pub/sub event trigger there is no way to set the dead letter queue of the created subscription

New or Affected Resource(s)

• google_cloudfunctions_function

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

resource "google_cloudfunctions_function" "my_cloud_function" {
   ...
  event_trigger {
    event_type = "google.pubsub.topic.publish"
    resource = "projects/GCP_PROJECT/topics/my_topic"
    failure_policy {
      retry = false
    }
    dead_letter_policy {
      dead_letter_topic = "projects/GCP_PROJECT/topics/my_dead_letter_topic"
      max_delivery_attempts = 5
    }
  }
}

References

• b/274818382

[lemoo5sg]

Hello,
We have the same need here.
Thanks in advance for your help.
(adding a comment as the issue seems stuck in a realm ;) )

[roaks3]

Unfortunately this option does not seem to be possible using our API at the moment (v1 or v2). Please correct me if there are API or gcloud docs that describe this configuration being applied directly to the Cloud Function, but until then, this will need to be handled upstream before we can add the fields to this Terraform resource.