If there are outputs in configuration, a destroy plan will always contain a "delete" change for each of these outputs.

This leads to meaningless delete changes being present for outputs which were not present in state and therefore cannot be deleted. Since there is a change in the plan, this plan will then be considered applyable, and the user will be presented with text instructing them to apply a plan in which there are no actual changes.

This commit stops the above from happening in the case of root module outputs.

update json plan docs with drift output

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>

Add "resource_drift" and "relevant_attributes" to the json plan
documentation.

Tiny README heading fix

Update Docs README to support versioned documentation

replace [dir] with [DIR] for consistency

This reverts commit 301174a3.

Add note about module.path and local module sources

Detailing `-chdir` behavior with `terraform.d/plugin` folders

fix grammar: subject-verb agreement

`terraform output` should adhere to Terraform Cloud authorization

always allow computed-only changes in the plan

lgtm
Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>