Skip to content

Conversation

@rpkr-in
Copy link

@rpkr-in rpkr-in commented Jan 3, 2026

…head

Dead Letter Topic (DLT) setup is currently not fully automated and requires manual configuration, increasing operational effort and making it difficult to adopt in CI/CD and Infrastructure-as-Code (IaC) driven environments.

This change improves DLT subscription handling by clearly addressing gaps that otherwise require human intervention, including:

  • Missing publisher permissions (roles/pubsub.publisher) on the DLT topic, which are required for Pub/Sub to publish failed messages
  • Missing subscriber permissions (roles/pubsub.subscriber) for DLT consumers, which must otherwise be configured per application
  • Lack of automatic DLT subscription creation, forcing consumers to manually create and manage subscriptions

By surfacing and improving handling of these limitations, this change reduces manual effort, improves deployment reliability, and makes DLT usage more predictable in automated provisioning workflows.

We'd love to accept your patches and contributions to this project. There are just a few small
guidelines you need to follow before opening an issue or a PR:

  1. Ensure the issue was not already reported.
  2. Open a new issue if you are unable to find an existing issue addressing your problem. Make sure
    to include a title and clear description, as much relevant information as possible, and a code
    sample or an executable test case demonstrating the expected behavior that is not occurring.
  3. Discuss the priority and potential solutions with the maintainers in the issue. The maintainers
    would review the issue and add a label "Accepting Contributions" once the issue is ready for
    accepting contributions.
  4. Open a PR only if the issue is labeled with "Accepting Contributions", ensure the PR description
    clearly describes the problem and solution. Note that an open PR without an issue labeled with "
    Accepting Contributions" will not be accepted.

See
also CONTRIBUTING.md
.

@rpkr-in rpkr-in requested a review from a team as a code owner January 3, 2026 08:00
…iguration overhead

Dead Letter Topic (DLT) setup is currently not fully automated and requires
manual configuration, increasing operational effort and making it difficult
to adopt in CI/CD and Infrastructure-as-Code (IaC) driven environments.

This change improves DLT subscription handling by addressing gaps that
otherwise require human intervention, including:

- Missing publisher permissions (roles/pubsub.publisher) on the DLT topic,
  which are required for Pub/Sub to publish failed messages
- Missing subscriber permissions (roles/pubsub.subscriber) for DLT consumers,
  which must otherwise be configured per application
- Lack of automatic DLT subscription creation, forcing consumers to manually
  create and manage subscriptions

By surfacing these limitations, this change reduces manual effort, improves
deployment reliability, and makes DLT usage more predictable in automated
provisioning workflows.
@rpkr-in
Copy link
Author

rpkr-in commented Jan 3, 2026

Addressing gap#3 of #4265

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant