Examples: terraform init
Jump to navigation
Jump to search
Contents
Terraform Cloud: terraform init examples[edit]
terraform init Initializing Terraform Cloud... Initializing provider plugins... Terraform Cloud has been successfully initialized! You may now begin working with Terraform Cloud. Try running "terraform plan" to see any changes that are required for your infrastructure. If you ever set or change modules or Terraform Settings, run "terraform init" again to reinitialize your working directory.
Terraform has been successfully initialized![edit]
Terraform init: AWS 3.56.0[edit]
Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/aws... - Installing hashicorp/aws v3.56.0... - Installed hashicorp/aws v3.56.0 (signed by HashiCorp) Terraform has created a lock file .terraform.lock.hcl to record the provider selections it made above. Include this file in your version control repository so that Terraform can guarantee to make the same selections by default when you run "terraform init" in the future. 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.
Terraform init: AWS 3.1.0[edit]
Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/random... - Installing hashicorp/random v3.1.0... - Installed hashicorp/random v3.1.0 (signed by HashiCorp) The following providers do not have any version constraints in configuration, so the latest version was installed. To prevent automatic upgrades to new major versions that may contain breaking changes, we recommend adding version constraints in a required_providers block in your configuration, with the constraint strings suggested below. hashicorp/random: version = "~> 3.1.0" 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.
Terraform init: 3.24.0[edit]
terraform init Initializing modules... Downloading terraform-aws-modules/ec2-instance/aws 2.19.0 for ec2_cluster... - ec2_cluster in .terraform/modules/ec2_cluster Initializing the backend... Initializing provider plugins... - Finding hashicorp/aws versions matching ">= 3.24.0"... - Installing hashicorp/aws v3.55.0... - Installed hashicorp/aws v3.55.0 (signed by HashiCorp) Terraform has created a lock file .terraform.lock.hcl to record the provider selections it made above. Include this file in your version control repository so that Terraform can guarantee to make the same selections by default when you run "terraform init" in the future. 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.
Terraform init: v3.55.0[edit]
terraform init Initializing modules... - ec2_with_t2_unlimited in ../.. Downloading terraform-aws-modules/security-group/aws 4.3.0 for security_group... - security_group in .terraform/modules/security_group Initializing the backend... Initializing provider plugins... - Finding hashicorp/aws versions matching ">= 2.42.0"... - Installing hashicorp/aws v3.55.0... - Installed hashicorp/aws v3.55.0 (signed by HashiCorp) Terraform has created a lock file .terraform.lock.hcl to record the provider selections it made above. Include this file in your version control repository so that Terraform can guarantee to make the same selections by default when you run "terraform init" in the future. 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.
Terraform init: downloading modules from private repository[edit]
terraform init Initializing modules... Downloading github.com/your-project/path/to/your/modules/alb for alb... Username for 'https://github.com':
Terraform init with errors[edit]
terraform init Terraform initialized in an empty directory! The directory has no Terraform configuration files. You may begin working with Terraform immediately by creating Terraform configuration files.
terraform init Error: Error checking configuration: <nil>: Failed to read module directory; Module directory /var/lib/snapd/void does not exist or cannot be read.
Error: Module not found[edit]
Initializing modules... Downloading github.com/your_wrong_path/ for yourmodulename... ╷ │ Error: Module not found │ │ The module address "github.com/your_wrong_path/e" could not be resolved. │ │ If you intended this as a path relative to the current module, use "./github.com/your_wrong_path/" │ instead. The "./" prefix indicates that the address is a relative filesystem path. ╵
AWS region value[edit]
Initializing modules... Initializing the backend... region AWS region of the S3 Bucket and DynamoDB Table (if used). Enter a value:
Related: provider.tf
Migration to s3 backend[edit]
Initializing modules... Initializing the backend... Do you want to copy existing state to the new backend? Pre-existing state was found while migrating the previous "local" backend to the newly configured "s3" backend. No existing state was found in the newly configured "s3" backend. Do you want to copy this state to the new "s3" backend? Enter "yes" to copy and "no" to start with an empty state. Enter a value:
Related[edit]
See also[edit]
terraform init[-upgrade | -reconfigure | -backend-config | -get-plugins=false | -verify-plugins=false ],--help, Execution examples, Execution with errors,~/.terraformrc, required_providers- Terraform configuration files, Terraform state files:
.tf,.tfvars,main.tf, outputs.tf,variables.tf,.terraform.d/,terraform init,providers.tf,.terraform/,terraform.tfstate,.terraform.lock.hcl,terraform.tfstate.d, override.tf, versions.tf terraform[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]- Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint, Operators, Expressions:for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising:
