-backend=false
The init option that skips connecting to the backend, so a pipeline can format, validate or test a configuration without any credentials.
In more detail
Providers and modules are still installed; only the state connection is skipped. You cannot plan or apply real changes in a directory initialised this way.
Example
terraform init -backend=falseRelated terms
- terraform init — The command that prepares a directory for Terraform: it downloads providers, fetches modules, connects the backend and writes the lock file.
- terraform validate — The command that checks a configuration is internally consistent, such as correct syntax, types and references, without contacting any real infrastructure.
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
Taught in
- Initialising The Working Directory — Infrastructure as Code with Terraform
- Running Terraform In CI — Infrastructure as Code with Terraform
- Native Testing With Tftest Files — Infrastructure as Code with Terraform
- Provider Mocking For Tests — Infrastructure as Code with Terraform
- Policy As Code With OPA — Infrastructure as Code with Terraform
- Releasing The Real Cloud Artifact — Infrastructure as Code with Terraform
- Write, Plan, Apply, And What Init Prepares — HashiCorp Terraform Associate (004) Exam Prep
- Runs In HCP Terraform: The cloud Block And Remote Execution — HashiCorp Terraform Associate (004) Exam Prep