Documentation
¶
Overview ¶
Package tofu drives the OpenTofu provider against a real cluster.
The other cluster suite walks the phases from inside the process. This one does not call cargoship at all: it runs the `tofu` binary over the module in example/terragrunt, which loads the provider out of a filesystem mirror, which starts the same phases in a subprocess the test does not control. That is the whole point -- everything between a practitioner's configuration and the phases is what has no coverage otherwise: the schema decoding, the map-keyed host set, the computed attributes a plan has to be able to promise, state, and a destroy.
Click to show internal directories.
Click to hide internal directories.