read_error value initializes to null and becomes "" after read causing state change on apply

Question

read_error value initializes to null and becomes "" after read causing state change on apply

Closed this issue 2 years ago · 2 comments

After first creating a script resource, read_error is initialized to null (regardless of whether you return output from create or use a read method). A subsequent terraform_apply will cause read_error to change to "" which terraform reports as a Terraform detected the following changes made outside of Terraform since the last "terraform apply":.

Maybe create just needs to set read_error to ""?

Answer 1 · 2022-09-21T15:15:38.000Z

Maybe it's still worth addressing (the state change that occurs is real), but I just upgraded to terraform 1.2.9 and terraform doesn't both telling you about the change anymore. Since it's no longer clutter up the output, it probably isn't that big of a deal.

Answer 2 · 2022-09-21T15:55:50.000Z

Sorry, this is a duplicate of #103