Terraform templates for WWT cloud infrastructure.
Перейти к файлу
Peter Williams cc27fd91de dev: add new backend settings needed for session tracking 2023-06-01 15:32:03 -04:00
dev dev: add new backend settings needed for session tracking 2023-06-01 15:32:03 -04:00
keyvault-acmebot keyvault-acmebot: start writing some stuff down here 2023-03-20 14:51:15 -04:00
prod prod: rename from "website" 2023-03-10 16:08:07 -05:00
.gitignore Adding gitignore to make sure the terraform non script assets are not committed 2020-08-11 09:29:39 -07:00
LICENSE Initial commit 2020-08-11 12:18:36 -04:00
README.md keyvault-acmebot: start writing some stuff down here 2023-03-20 14:51:15 -04:00

README.md

Terraform Infrastructure for WWT Web Services

This repository contains Terraform files that define the infrastructure for a large portion of the AAS WorldWide Telescope web services. In principle, you could use these templates to create your own clone of the WWT web app, although the WWT team does not test the templates for this kind of portability, and various secrets and data holdings are not expressed in these files.

Basic commands:

terraform plan -var-file=prod.tfvars                        # plan a change
terraform apply -var-file=prod.tfvars                       # apply a change
terraform import -var-file=prod.tfvars [tfname] [azurename] # tell Terraform about a resource

Directory structure:

  • prod expresses much, but not all, of the production WWT environment
  • dev expresses a more limited development environment
  • keyvault-acmebot describes our, well, Keyvault/Acmebot system

The eventual goal is to merge dev and prod, and have the distinctions entirely subsumed into the .tfvars files, but that is unlikely to happen anytime soon.

To update the Terraform provider version:

  • Remove .terraform.lock.hcl
  • Update minimum version in the main.tf file
  • Run terraform init
  • Run terraform (plan|apply) -var-file=prod.tfvars -refresh-only