Jafner.net/homelab/sellswords/README.md

# Sellswords
This directory contains Terraform code and documentation for external service providers. 

### Recovering from lost TF state

- Run [`cf-terraforming_import.sh`](./cloudflare/cf-terraforming_import.sh) to generate two important artifacts per Zone: 
  - List of `cf-terraforming import` commands, one for each record.
  - A `$ZONE.import.tf` configuration file with all imported records.
- When that's done, the state file should have all configured records, but with unreadable names like `terraform_managed_resource_werpwepigfnwgpowb`. 
- Delete the generated `$ZONE.import.tf` files.
- Run a `terraform init && terraform plan` and *read the diff.*
  - The destroyed and created resources should match 1:1, other than perhaps drift of A-records controlled by dynamic DNS. 
  - If any records differ (other than the above), reconcile those differences before proceeding. Add those records (with human-readable names) to the appropriate zone configuration.
- Run `terraform apply`.
Init k3s cluster with Terraform-provisioned AWS S3 bucket for Jafner.dev - Add Terraform statefiles to gitignore - Add *.secret.yml to gitignore for k8s secrets manifests - Init the "sellswords" directory for Terraform code interacting with public cloud providers. - Provision S3 bucket "Jafner-dev" to store static site files. - Describe CORS and access policies to apply to the bucket. - Throw in a budget to prevent nasty surprises. - Init "silver-hand" directory for Kubernetes manifests to be used with the local K3s cluster. - Datashim manifest to facilitate abstracted interaction with S3 bucket. - Kubernetes-dashboard to visualize cluster state. - Jafner-dev to serve contents of S3 bucket. 2024-08-07 16:23:20 -07:00			`# Sellswords`
			`This directory contains Terraform code and documentation for external service providers.`

Document recovering from lost TF state, or initializing Terraform for existing CF zones. 2024-08-28 13:13:43 -07:00			`### Recovering from lost TF state`

			- Run [`cf-terraforming_import.sh`](./cloudflare/cf-terraforming_import.sh) to generate two important artifacts per Zone:
			- List of `cf-terraforming import` commands, one for each record.
			- A `$ZONE.import.tf` configuration file with all imported records.
			- When that's done, the state file should have all configured records, but with unreadable names like `terraform_managed_resource_werpwepigfnwgpowb`.
			- Delete the generated `$ZONE.import.tf` files.
			- Run a `terraform init && terraform plan` and read the diff.
			`- The destroyed and created resources should match 1:1, other than perhaps drift of A-records controlled by dynamic DNS.`
			`- If any records differ (other than the above), reconcile those differences before proceeding. Add those records (with human-readable names) to the appropriate zone configuration.`
			- Run `terraform apply`.