Incomplete DLT Automation in Spring Cloud Stream GCP Pub/Sub Binder

[rpkr-in]

DLT configuration exists, but it is not fully automated and still requires manual human intervention, making it unsuitable for CI/CD and IaC-driven environments.

Missing Automations (3 Gaps)

1. Publisher Permission
   • roles/pubsub.publisher is NOT automatically granted on the DLT topic
   • Required for Pub/Sub to publish failed messages
2. Subscriber Permission
   • roles/pubsub.subscriber is NOT automatically granted for DLT consumers
   • Must be manually configured per application
3. DLT Subscription Creation
   • No automatic subscription is created for the DLT topic
   • Consumers must manually create and manage DLT subscriptions

Impact

• Runtime-only failures
• Environment drift
• Broken CI/CD & IaC workflows
• Messages will fall into an endless retry loop though DLT is configured
• DLT appears configured but is non-functional by default

Why This Matters

DLT without IAM automation is half-implemented reliability.

• It looks configured
• It deploys successfully
• It fails only at runtime
• It results in endless retry loops for any failure
• It requires tribal knowledge to diagnose and fix
  This is worse than not supporting DLT at all.

[jinseopkim0]

Thanks for opening this issue. If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.