Difference between revisions of "Migration to s3 backend"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
== See also == | == See also == | ||
* {{terraform init}} | * {{terraform init}} | ||
| − | * {{terraform | + | * {{terraform backends}} |
| + | |||
| + | |||
| + | [[Category:Terraform]] | ||
Revision as of 22:40, 21 October 2021
terraform init
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: yes Successfully configured the backend "s3"! Terraform will automatically use this backend unless the backend configuration changes.
Initializing provider plugins... - Reusing previous version of hashicorp/aws from the dependency lock file - Using previously-installed hashicorp/aws v3.57.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.
See also
Advertising:
