-
Notifications
You must be signed in to change notification settings - Fork 1.8k
google_pubsub_subscription - add 'filename_datetime_format' to cloud_storage_config #17911
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
google_pubsub_subscription - add 'filename_datetime_format' to cloud_storage_config #17911
Comments
Added note: The google_pubsub_subscription resource will actually silently overwrite any filename_datetime_format config on the subscription that has been set on the subscription. I discovered this as follows:
This could be a bit of an issue as if any of my subscriptions are updated in TF, they will then revert to the default datetime format and files will appear in a different directory in GCS than they should |
Apologies for the trouble. I'm working on adding filename_datetime_format support and hope to have it in your hands soon! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Uh oh!
There was an error while loading. Please reload this page.
Community Note
Description
Hi
Pub/Sub Subscriptions with Cloud Storage config now allow definition of the filenameDatetimeFormat. Links below to Gcloud CLI and Pub/Sub API contain further information.
I suggest adding a field
filename_datetime_format
to thecloud_storage_config
block forgoogle_pubsub_subscription
to handle this.References to Pub/Sub API in reference section and sample configuration provided. Please note that the Pub/Sub service/API enforces some constraints on this field - namely than all of YYYYMMDDhhmmss must be used, but can be broken up with characters like
/
,-
,_
,:
New or Affected Resource(s)
Potential Terraform Configuration
References
See:
b/336319061
The text was updated successfully, but these errors were encountered: