update

.github/workflows/terraform-deploy.yaml → .github/workflows/terraform-apply.yaml

@@ -1,15 +1,11 @@
 # Based on https://github.com/canonical/sunbeam-terraform/blob/9973905d24892903fab19ce691bbc5c28c53df0a/.github/workflows/deploy.yml
 # For usage, refer to templates/terraform-deploy-usage-template.yaml
-name: Deploy Terraform module
+# Applies terraform module and wait for the application to go active or blocked.
+name: Apply Terraform module
 
 on:
   workflow_call:
     inputs:
-      module-directory:
-        description: The directory that stores the Terraform module. Defaults to `./terraform`.
-        required: false
-        type: string
-        default: ./terraform
       model:
         description: The model that the charm is deployed on. Defaults to `testing`.
         required: false
@@ -20,10 +16,15 @@ on:
         required: false
         type: string
         default: latest/stable
+      module-directory:
+        description: The directory that stores the Terraform module. Defaults to `./terraform`.
+        required: false
+        type: string
+        default: ./terraform
 
 jobs:
-  deploy:
-    name: Deploy Terraform
+  apply:
+    name: Apply Terraform
     runs-on: ubuntu-20.04
     steps:
       - name: Checkout

templates/terraform-deploy-usage-template.yaml → templates/terraform-apply-usage-template.yaml

@@ -1,6 +1,7 @@
+# trigger workflow
 jobs:
-  terraform-deploy:
-    name: Deploy Terraform
+  terraform-apply:
+    name: Apply
     uses: canonical/charmed-kubeflow-workflows/.github/workflows/terraform-deploy.yaml@main
     with:
       # Defaults to "testing"
@@ -9,8 +10,4 @@ jobs:
       channel: latest/edge
       # Add the line below for multi-charm repos. For single-repo repositories, it can be 
       # omitted since the workflow was designed according to CC006 spec file structure conventions.
-      working-directory: charms/<charm-name>/terraform
-      # The following line is useful when there are no dependencies for a charm to go `active`. Otherwise,
-      # setting it to true will cause the workflow to timeout if the unit never goes to `active`.
-      workload-check: true
-
+      module-directory: charms/<charm-name>/terraform