build: allow experimental features

README.md

@@ -52,3 +52,29 @@ All dagster secrets are automatically picked up by the terraform deployment and
 
 This means that, after manually triggering the 'Add secrets' GitHub actions pipeline, you should also trigger the Terraform deployment
 to ensure that your secrets are available in the cluster / dagster deployment.
+
+## Migrating dagster minor version
+
+See [this guide](https://docs.dagster.io/deployment/guides/kubernetes/how-to-migrate-your-instance)
+
+Uncomment lines 112-115 to get values.yaml and do tfapply
+
+Get migration values
+```shell
+helm template dagster-prd dagster/dagster \  
+    --set "migrate.enabled=true" \
+    --show-only templates/job-instance-migrate.yaml \
+    --values values.yaml \
+    -n dagster-prd > migration.yml
+```
+
+In migration.yml, change value of the postgres secret
+
+Deploy job
+`kubectl apply -f migration.yml -n dagster-prd`
+
+Describe pod
+`kubectl describe pod dagster-prd-dagster-webserver-instance-migrate -n dagster-prd`
+
+View logs
+`kubectl logs dagster-prd-dagster-webserver-instance-migrate-4lpcs -n dagster-prd`

infra/app.tf

@@ -108,3 +108,8 @@ resource "helm_release" "dagster" {
     value = data.google_secret_manager_secret_version.postgres_password.secret_data
   }
 }
+
+# resource "local_file" "helm_manifest" {
+#   content = yamlencode(jsondecode(helm_release.dagster.manifest))
+#   filename = "${path.module}/values.yml"
+# }

infra/providers.tf

@@ -40,4 +40,8 @@ provider "helm" {
     token                  = data.google_client_config.default.access_token
     cluster_ca_certificate = base64decode(module.gke.ca_certificate)
   }
+
+  experiments {
+      manifest = true
+  }
 }