v6.7.4

v6.7.4

⚠️ This release is deprecated, please use v6.7.5 instead

This patch appropriately handles the cases when a Terraform resource has an Update function defined (which was recently added), the Terraform SDK requires that any field that can change must either have ForceNew: true (meaning changes require resource recreation) or for that field to be a computed-only field.

The destroy_on_drift field is a provider config setting that controls how drift detection works - it's not a field that maps to the GitHub API. When implementations try to change this field Terraform will execute the plan properly but fail on the apply because the Update function didn't know how to handle the destroy_on_drift change.

Lastly reads now handle setting encrypted_value and plaintext_value to nil to trigger an update when the "stored" update dates do not match.

Full Changelog: v6.7.3...v6.7.4