@@ -159,8 +159,10 @@ In the [HackyStack v1.11 (November 2021) release](https://gitlab.com/gitlab-com/
1. Click the **Create Terraform Environment** button and fill out the form:
1. Choose your Cloud Account from the **Cloud Account** dropdown.
1. Choose the template you wish to use from the **Environment Template** dropdown. If this is your first time, use the `gcp-sandbox-environment-template-v2-########` template.
- If you are looking for a more detailed template (where you can set the version and enable a runner) use `support-resources-template-v2`.
1. Input a name for your environment in the **Environment Name (Alphadash Slug)** text field.
1. After the Environment is created, click the **View Terraform Configuration** button. This is hosted on a new GitLab instance at [https://gitops.gitlabsandbox.cloud](https://gitops.gitlabsandbox.cloud). Your GitLab instance credentials can be found in the View GitOps Credentials button modal.
- You can create multiple Terraform Environments, subject to GCP resource quotas and cost considerations. Every Friday, your GCP compute instances will automatically be powered down for cost savings and security best practices.
### How to Use Terraform Environments
@@ -193,6 +195,14 @@ In the [HackyStack v1.11 (November 2021) release](https://gitlab.com/gitlab-com/
1. You can update the `terraform/main.tf` file in the Git repository to add more Terraform resources or modules.
1. Simply run the `Deploy` CI pipeline job to deploy your resources.
### Navigate Terraform Environments in a GCP environment
1. Once on your GCP account page you will see the test environments you've created on the bottom of the page.
1. To view CI Pipelines, locate your environment in the list and click on the rocket icon (🚀) in the actions column on the far right side of the row.
1. Log on to your GitLab Sandbox Cloud GitOps Environments.
- To find your GitOps URL credentials, go to your GCP sandbox account homepage and click **View Credentials**.
1. You are now able to view your environment.
## Delete an AWS account or GCP project
Currently, deleting an AWS account or GCP project must be performed manually by IT Ops. This is done during offboarding for operational consistency. However, outside of offboarding, you must make a best effort to delete all resources within the account yourself. There may be a nominal monthly cost of a few dollars a month to keep the account in existence. At this time, this cost is deemed acceptable.
