The -var command line option comes with the disadvantage that a user must
contend both with Terraform's own parser and with the parser in whichever
shell they've decided to use, and different shells on different platforms
have different rules.

Previously we've largely just assumed that folks know the appropriate
syntax for the shell they chose, but it seems that command lines involving
spaces and other special characters arise rarely enough in other commands
that Terraform is often the first time someone needs to learn the
appropriate syntax for their shell.

We can't possibly capture all of the details of all shells in our docs,
because that's far outside of our own scope, but hopefully this new
section will go some way to give some real examples that will help folks
figure out how to write suitable escape sequences, if they choose to
set complex variable values on the command line rather than in .tfvars
as we recommend elsewhere on this page.

Backport of Upgrade cty to v1.8.4 into v1.0

Backport of recent JSON output changes

Previously, if any resources were found to have drifted, the JSON plan
output would include a drift entry for every resource in state. This
commit aligns the JSON plan output with the CLI UI, and only includes
those resources where the old value does not equal the new value---i.e.
drift has been detected.

Also fixes a bug where the "address" field was missing from the drift
output, and adds some test coverage.

The "references" included in the expression representation now properly unwrap for each traversal step, to match what was documented.

* jsonplan and jsonstate: include sensitive_values in state representations

A sensitive_values field has been added to the resource in state and planned values which is a map of all sensitive attributes with the values set to true.

It wasn't entirely clear to me if the values in state would suffice, or if we also need to consult the schema - I believe that this is sufficient for state files written since v0.15, and if that's incorrect or insufficient, I'll add in the provider schema check as well.

I also updated the documentation, and, since we've considered this before, bumped the FormatVersions for both jsonstate and jsonplan.

Backport of blocktoattr fixup dropping MissingItemRange into v1.0

Merge pull request #28954 from hashicorp/backport/jbardin/objchange-unknown-blocks/jointly-tough-lion

Backport of handle unexpected changes to unknown block into v1.0

Merge pull request #28923 from hashicorp/backport/jbardin/noop-deposed-change/needlessly-concrete-bluejay

Backport of account for noop deposed instances in json plan into v1.0

backport changes to refresh error message to v1.0

Seems like we lost a newline in some of the shuffling it took to get this
into the live website, and so it's formatting oddly in the rendered
website. This restores the intended formatting of this as the start of
a bullet list, rather than as a continuation of the previous paragraph.

Merge pull request #28897 from hashicorp/backport/alisdair/fix-remote-backend-multi-workspace-state-migration/seriously-bold-cub

Backport of Fix remote backend multi workspace state migration into v1.0

* tools: remove terraform-bundle.

terraform-bundle is no longer supported in the main branch of terraform. Users can build terraform-bundle from terraform tagged v0.15 and older.

* add a README pointing users to the v0.15 branch

Merge pull request #28824 from hashicorp/backport/alisdair/fix-stuck-lock-when-applying-state-plan/enormously-refined-sheepdog

Backport of backend/local: Fix lock when applying stale plan into v0.15