Thank you for the context. I have one more question if you don’t mind -
Some of our folks had (quite understandably) assumed the v0.11.15-oci release was GA, installed it on their workstations, and then gone on to
apply against state that had long since been curated by v0.11.14.
In light of your post, I would like to roll us back to the v0.11.14 release.
Terraform doesn't allow running any operations against a state
that was written by a future Terraform version. The state is
reporting it is written by Terraform '0.11.15'
% terraform version
# I fetched state from our backend storage.
% jq -r .terraform_version <state
Would it be safe to manually revert the value of this state key back to
I note that the value of the
version key, which I presume is the true state schema version, did not change between 0.11.14 and 0.11.15 – it is still set at 3. If it helps, we have a complete history of all revisions to state.
Following a successful roll back, we can implement our own measures to block any future accidental installations of the v0.11.15-oci release.
Edit: After diffing the state objects generated by 0.11.14 and 0.11.15, I saw no apparent schema changes that might pose a problem. I proceeded to fudge the values of the
terraform_version keys for some of our smaller, simpler states. This seemed to work OK.