The human-oriented plan output includes a short summary of the meaning of
all of the different "icons" used to describe different kinds of change,
but nothing was previously describing how OpenTofu uses "->" to describe
the transition between current and planned values for update in-place, "~".
We'll now include a concise note about that as part of the icon summary,
keeping things still relatively compact but nonetheless giving something
to refer to if a reader is unsure about the meaning of this notation.
Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
* Introduce a snapshot check for equivalence tests
* New snapshots
* Allow overriding plan timestamp for snapshots
* Allow setting the seed externally (as an env var) for testing purposes
* Remove an equivalence test that depends on a random number
* add some basic equivalence tests and execute them in the build pipeline
* remove old file, now unused
* update terraform-equivalence-testing to v0.2.0
* add separate action
* make sure to read from hashicorp repo
* remove elevated github token where possible
* Don't need elevated token anymore
* update with official mock provider
* last change: don't need the authorization header for public repositories.
