aws_glue_catalog_table fails modification due to implicit column values

[dylanhellems]

I've just recently started to work with Glue tables in terraform, and I'm running into a problem with the Glue schema registry integration. I saw the following comment while searching for solutions in other issues, and I think it does a good job of describing the problem.

---

There is a specific issue relating to aws_glue_catalog_table [...] because only schema_reference OR columns can be specified - it's invalid to specify both. If I specify schema_reference, any future updates to the resource pulls back an implicit value for columns, so that updates attempts to set both values, even though only 1 is explicitly set in my tf files. This appears fine in the plan phase, but in the apply phase you'll see:

aws_glue_catalog_table.my_table: Modifying... [id=<AWS-ACCOUNT-ID>:<database-name>:<table-name>]

Error: Error updating Glue Catalog Table: InvalidInputException: Both SchemaReference and Columns are populated, only one of them should be populated.

This issue is causing any modifications to the table to require me to taint the resource, causing it to destroy and re-create.

Originally posted by @jeremyolliver in #19157 (comment)

[DrFaust92]

Im able to reproduce this, fix coming up.

[DrFaust92]

Opened #19742 to address this issue.

[github-actions]

This functionality has been released in v3.47.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.