You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEPLOYMENT.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,10 +159,16 @@ Run `terraform apply` to create the AWS resources.
159
159
terraform apply -var-file="mysettings.tfvars"
160
160
```
161
161
162
+
Alternative method:
163
+
```
164
+
terraform plan -var-file=mysettings.tfvars -out=my.plan
165
+
terraform apply my.plan
166
+
```
167
+
162
168
Enter 'yes' to create the resources.
163
169
164
170
---
165
-
**NOTE:**
171
+
**NOTES:**
166
172
167
173
You may run into something similar to the following error if applying Terraform on an AWS account where more than one Cloud Sandbox have been deployed:
168
174
```
@@ -204,7 +210,7 @@ The installation script will continue to run on the instance after terraform com
204
210
You can log into the newly created EC2 instance and watch the installation progress.
*If terraform says the instance needs to be destroyed first, type "no" when prompted to keep the existing instance. There are other ways to change the instance type.*
228
234
229
-
### Cleanup
235
+
### Cleanup - delete the sandbox
230
236
When done using the Cloud Sandbox deployment, all of the AWS resources (including disks!) can be destroyed with the following command:
In case you've already deployed cloud resources but your local copy of Cloud Sandbox is destroyed or you work on multiple copies, you can restore the Terraform state from the remote S3 bucket by simply running `terraform init -backend-config=config.s3.tfbackend` again. If you were using a custom workspace, switch to that workspace with `terraform workspace select`. Once you run `terraform plan` you should see that no new resources need to be created.
245
+
In case you've already deployed cloud resources but your local Cloud Sandbox terraform directory/files are destroyed or or lost, or if you work on multiple copies, you can restore the Terraform state from the remote S3 bucket by simply running `terraform init -backend-config=config.s3.tfbackend` again. If you were using a custom workspace, switch to that workspace with `terraform workspace select`. Once you run `terraform plan` you should see that no new resources need to be created.
0 commit comments