Review this curated collection of dispatch workflows.
Take this path when you want to get up-and-running as quickly as possible with the least amount of fuss.
Action | Link |
---|---|
Create workflows | Choose create before clicking on the Run workflow button |
KMS Key | ✅ |
Remote Backend Support | ✅ |
Toolset image | ✅ |
DNS Zone for base domain | ✅ |
DNS Zone for sub domain | ✅ |
Create workshop environment | ✅ |
Cleanup workflows | Choose destroy before clicking on the Run workflow button |
Destroy workshop environment | ✅ |
DNS Zone for sub domain | ✅ |
DNS Zone for base domain | ✅ |
Remote Backend Support | ✅ |
KMS Key | ✅ |
Clean Workflow Logs | ✅ |
Administer resources one at a time.
There are two types of actions defined, those that can be manually triggered (i.e., dispatched), and those that can only be called by another action. All actions are located here and can be run by providing the required parameters. Go here to inspect the source for each action.
Note that for most dispatch actions, you have the option to either create or destroy the resources.
Module | Github Action | Terraform |
---|---|---|
KMS | ✅ | ✅ |
Remote backend | ✅ | ✅ |
VPC | ✅ | ✅ |
DNS Zone for base domain | ✅ | ✅ |
DNS Zone for sub domain | ✅ | ✅ |
GKE Cluster | ✅ | ✅ |
GKE Autopilot Cluster | ✅ | ✅ |
Container registry | ✅ | ✅ |
Harbor | ✅ | ✅ |
Bastion | ✅ | ✅ |
Secrets Manager | ✅ | ✅ |
Secrets | ✅ | ✅ |
All Credentials are stored in Google Cloud Secrets Manager.
First, configure Google Cloud using the service account credentials you created earlier
Go visit the Secret Manager Secrets Terraform module's README for how to retrieve secrets.