Explanation
A Terraform Enterprise install that is provisioned on a network that does not have Internet access is generally
known as an air-gapped install. These types of installs require you to pull updates, providers, etc. from external
sources vs. being able to download them directly.

Explanation
"Use the depends_on meta-argument to handle hidden resource or module dependencies that Terraform cannot
automatically infer. You only need to explicitly specify a dependency when a resource or module relies on
another resource's behavior but does not access any of that resource's data in its arguments."
https://www.terraform.io/language/meta-arguments/depends_on

Explanation
Terraform has detailed logs that can be enabled by setting the TF_LOG environment variable to any value.
This will cause detailed logs to appear on stderr.
You can set TF_LOG to one of the log levels TRACE, DEBUG, INFO, WARN or ERROR to change the
verbosity of the logs. TRACE is the most verbose and it is the default if TF_LOG is set to something other
than a
log level name.
https://www.terraform.io/docs/internals/debugging.html

Explanation
workspaces allow conveniently switching between multiple instances of a single configuration within its single
backend. They are convenient in a number of situations, but cannot solve all problems.
A common use for multiple workspaces is to create a parallel, distinct copy of a set of infrastructure in order to
test a set of changes before modifying the main production infrastructure. For example, a developer working
on a complex set of infrastructure changes might create a new temporary workspace in order to freely
experiment with changes without affecting the default workspace.
Non-default workspaces are often related to feature branches in version control. The default workspace might
correspond to the "master" or "trunk" branch, which describes the intended state of production infrastructure.
When a feature branch is created to develop a change, the developer of that feature might create a
corresponding workspace and deploy into it a temporary "copy" of the main infrastructure so that
changes can be tested without affecting the production infrastructure. Once the change is merged and deployed
to the default workspace, the test infrastructure can be destroyed and the temporary workspace deleted.
https://www.terraform.io/docs/state/workspaces.html
https://www.terraform.io/docs/state/workspaces.html#when-to-use-multiple-workspaces