Difference between revisions of "Example: terraform init"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
commands will detect it and remind you to do so if necessary. | commands will detect it and remind you to do so if necessary. | ||
</pre> | </pre> | ||
| + | |||
| + | == Related == | ||
| + | * [[Terraform init examples]] | ||
| + | |||
== See also == | == See also == | ||
Revision as of 14:49, 14 February 2022
terraform init Initializing modules... - compute in ../terraform-templates-infra/modules/compute Initializing the backend... Initializing provider plugins... - Reusing previous version of hashicorp/aws from the dependency lock file - Installing hashicorp/aws v3.57.0... - Installed hashicorp/aws v3.57.0 (signed by HashiCorp) Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.
Related
See also
terraform init[-upgrade | -reconfigure | -backend-config | -get-plugins=false | -verify-plugins=false ],--help, Execution examples, Execution with errors,~/.terraformrc, required_providersterraform[untaint | fmt|apply|show|state|init | plan | console | output|validate|destroy|debug|import|providers|get|graph|workspaces|resource|login|-var-file|state mv|state pull|state push|state replace-provider|state rm|force-unlock|env|tfe|--version|remote-exec|delete on termination| deprecated commands |terraform --help]
Advertising:
