google_bigquery_table
configured as a Biglake table show permadiff on partition column
#16907
Labels
google_bigquery_table
configured as a Biglake table show permadiff on partition column
#16907
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
hashicorp/google v5.8.0
hashicorp/google-beta v5.8.0
Affected Resource(s)
google_bigquery_table
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Terraform should show the diff when rows are changed in the table schema, if rows are not changed, there should be no diff.
Actual Behavior
Permadiff of the tables, due to the partition column not being declared in the schema, forcing a replacement.
Steps to Reproduce
terraform apply
successfullyImportant Factoids
Functionally this isn't blocking our use of biglake tables via terraform - as the recreate of the tables doesn't affect the underlying data which is in GCS. But it does make reviewing the plan output for future releases that much more noisy, and generally recreating tables where not required is a bad thing.
The workaround is to use the lifecycle meta argument like below, but this means we'd be unable to make any schema changes to tables once created, which is less desirable.
References
b/318873211
The text was updated successfully, but these errors were encountered: