Supports this update to cas-metabase
The initial configuration of the Terraform chart worked was set up to only handle 1 GitHub repo/Helm job per namespace. This became an issue with cas-metabase, which runs within cas-ggircs's namespaces. As they were set up, each of these would want to destroy the other's objects within state each time they were run. To alleviate this, the chart now supports an optional terraform.workspace value parameter, which will create/use a workspace within the same state, preventing overwrites. This allows both projects to utilize the same configuration (ie. gcs.tfbackend), credentials (from GCP), secrets and similar shared pieces.
Changes 🚧
added terraform.workspace to chart's Values, with a default of default.
added command to switch-or-create active workspace on terraform-job execution.
Supports this update to cas-metabase The initial configuration of the Terraform chart worked was set up to only handle 1 GitHub repo/Helm job per namespace. This became an issue with
cas-metabase, which runs withincas-ggircs's namespaces. As they were set up, each of these would want to destroy the other's objects within state each time they were run. To alleviate this, the chart now supports an optionalterraform.workspacevalue parameter, which will create/use a workspace within the same state, preventing overwrites. This allows both projects to utilize the same configuration (ie.gcs.tfbackend), credentials (from GCP), secrets and similar shared pieces.Changes 🚧
terraform.workspaceto chart's Values, with a default ofdefault.terraform-jobexecution.