Difference between revisions of "Examples: terraform init"
Jump to navigation
Jump to search
| Line 115: | Line 115: | ||
</pre> | </pre> | ||
| − | == | + | == Terraform init with errors == |
terraform init | terraform init | ||
Revision as of 15:30, 6 September 2021
Contents
Terraform init: AWS 3.56.0
terraform init
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
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
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
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 with errors
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.
Terraform init with errors
terraform init
Initializing the backend...
Initializing provider plugins...
- Finding latest version of hashicorp/vsphere...
- Installing hashicorp/vsphere v1.24.3...
- Installed hashicorp/vsphere v1.24.3 (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.
Warning: Interpolation-only expressions are deprecated
on kk.tf line 7, in data "vsphere_datastore" "datastore":
7: datacenter_id = "${data.vsphere_datacenter.dc.id}"
Terraform 0.11 and earlier required all non-constant expressions to be
provided via interpolation syntax, but this pattern is now deprecated. To
silence this warning, remove the "${ sequence from the start and the }"
sequence from the end of this expression, leaving just the inner expression.
Template interpolation syntax is still used to construct strings from
expressions when the template includes multiple interpolation sequences or a
mixture of literal strings and interpolations. This deprecation applies only
to templates that consist entirely of a single interpolation sequence.
(and 5 more similar warnings elsewhere)
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.
See also
- 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:
