you can remove it after apply, and don’t have to commit it (but that means CI will need to generate it) so i thought i could just remove the file after init, but no dice. i’m using terraform-bundle already, setting up the plugin-cache in advance, restricting versions, and restricting network connectivity in CI. it really clutters up the repo when you have a lot of root modules, and means you have to init each root somehow to generate the file, and commit it, anytime you want to update providers? no thanks! but, unfortunately, there is no way to disable it. the workflow around the new lock file.changing it to '' fixed it :man-shrugging::skin-tone-2: worked fine in tf 0.13.5, but not in tf 0.14.4. in some places, outputting null as the false condition caused a persistent diff. some of the output handling is a little odd, particularly with conditional resources/modules and accordingly conditional outputs.

any outputs containing provider-marked sensitive values must also be marked sensitive you cannot for_each over objects containing these values, but you can for_each over non-sensitive keys and index into the object. sensitive values may be marked in the provider, i.e.Fwiw, updated a decent number of tf states from 0.13.5 to 0.14.4 over the last week… no significant issues, but a few things took a little while to understand:

Password depot 10.0.8.0