-
Notifications
You must be signed in to change notification settings - Fork 128
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
Add option to control enable_exactly_once_delivery
for subscriptions.
#91
Comments
Any other information that I can provide here? |
Howdy folks - checking in again, would this be a change that we'd be open to taking in? |
Hello, I would also like to +1 this. I have the code changes that I've made myself, however it's annoying to apply the changes after init-ing the module. |
because that i will have to create my own module :(.. |
@hdavila146 @ttacon @notobsd2 Happy to review a PR adding this |
Hello @bharathkkb I already got the code change an tested please let me know how can I delivery I don't have permission do a push in this repository and neither a PR 👎 |
Hi @hdavila146 - Thanks for reaching out. The standard practice is to create your own fork of this repo and upload your changes to a branch on your fork. You should then be able to create a pull request from the branch in your fork to this repository. |
Hello, now google doesn't support enable_exactly_once_delivery for push subscription only for pull I will do a new PR 👎 @apeabody |
Thanks @hdavila146 - Once you open the PR please @ me in a comment and I'll try to take a look. |
TL;DR
Currently, enabling exactly once delivery is a preview feature for GCP PubSub subscriptions. I'm curious if y'all are open to adding this flag while it's in a preview state to this module (the official provider supports it).
Terraform Resources
The official
pubub_subscription
provider supports theenable_exactly_once_delivery
.Detailed design
Implementing this should be a similar change to this one here.
The only major constraint would be that
enable_exactly_once_deliver
andenable_message_ordering
are mutually exclusive. However, handling that doesn't feel like this module's responsibility (the provider should handle it, which it doesn't).Additional information
No response
The text was updated successfully, but these errors were encountered: