Skip to content
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

Deprectate time_partitioning.require_partitioning_filter and add new top-level field #6496

Conversation

modular-magician
Copy link
Collaborator

Deprecated the require_partitioning_filter inside the time_partitioning block, and add the new top-level field. Added conditional reading logic to use the old or new field, so that the old terraform plans don't break.

API: https://cloud.google.com/bigquery/docs/reference/rest/v2/tables
Fixes: hashicorp/terraform-provider-google#6725

Release Note Template for Downstream PRs (will be copied)

bigquery: deprecated `time_partitioning.require_partition_filter` and used the new top level field `require_partition_filter` instead in resource `google_bigquery_table`

Derived from GoogleCloudPlatform/magic-modules#9199

…top-level field (hashicorp#9199)

* Deprectate time_partitioning.require_partitioning_filter and add new top-level field

* Use deprecated require_partition_filter field in one of the tests
[upstream:f195c3a9da467e7aaf3a43c1a096f763dd6f2646]

Signed-off-by: Modular Magician <[email protected]>
@modular-magician modular-magician merged commit d3412d7 into hashicorp:main Oct 12, 2023
@modular-magician modular-magician deleted the downstream-pr-f195c3a9da467e7aaf3a43c1a096f763dd6f2646 branch November 16, 2024 05:00
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.

BigQuery - add optional 'require_partition_filter' to range partitioning
1 participant