Difference between revisions of "Examples: terraform init"
Jump to navigation
Jump to search
(Created page with "== Terraform init: AWS 3.56.0 == <pre> Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/aws... - Installing hashicorp/aws v3...") |
|||
Line 23: | Line 23: | ||
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> | ||
+ | |||
+ | == 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. |
Revision as of 14:08, 6 September 2021
Terraform init: AWS 3.56.0
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.
Advertising: