mirrors/khuedoan-homelab
1
0
Fork 0
mirror of https://github.com/khuedoan/homelab.git synced 2024-12-23 01:04:32 +07:00
Code Issues Packages Projects Releases Wiki Activity

docs(external): add Terraform Cloud workspace instruction (#44)

Browse Source 
* Add note regarding terraform cloud execution mode

When configuring a workspace in Terraform Cloud, the execution mode defaults to "Remote". This is problematic for two reasons:
1. We use local files that are not in the terraform plan directory. This creates errors about being unable to local files where it is not immediately obvious why.
2. The remote (cloud) runner won't be able to access the kube cluster running on the internal network anyway, so any plan application will fail.

* Detail terraform cloud workspace setup
This commit is contained in:
Elliot Blackburn 2022-02-15 01:32:29 +00:00 committed by GitHub
parent d10892a326
commit cf94f761c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
external/README.md
View File

@ -25,7 +25,13 @@ This layer will:
### Create Terraform workspace ### Create Terraform workspace
TODO Terraform is stateful, which means it needs somewhere to store it's state. The Terraform Cloud is one option for a state backend with a generous free tier perfect for a homelab.
1. Sign up for a [Terraform Cloud](https://cloud.hashicorp.com/products/terraform)
2. Create a workspace named `homelab-external`, this is the workspace where your homelab state will be stored.
3. Change the "Execution Mode" from "Remote" to "Local". This will ensure your local machine, which can access your lab, is the one executing the terraform plan rather than the cloud runners.
If you decide to use a different terraform backend, you'll need to edit the [external/versions.tf](./versions.tf) file as required.
### Create Cloudflare API token ### Create Cloudflare API token