Expose additional Overmind CLI options (#15)

* Added more args to the plugin

* Normalise case

Author: dylanratcliffe

README.md

@@ -22,6 +22,12 @@ The Overmind plugin installs the Overmind CLI (and GitHub CLI) and executes one
 | `comment_provider` | Where `wait-for-simulation` should post comments when `post_comment=true`. Must be one of: `github`, `gitlab`.                                                                                              | No       |
 | `on_failure`       | Behavior when the plugin step errors. `fail` (default) fails the step and blocks the deployment; `pass` allows the deployment to continue even if this step errors. Must be one of: `fail`, `pass`.         | No       |
 | `skip_after_approval` | When `true` (default), `submit-plan` exits early once a deployment has been approved (`ENV0_REVIEWER_NAME` is set), avoiding duplicate analysis from the post-approval re-plan. Set to `false` to submit on every plan. | No       |
+| `timeout` | Wall-clock time limit for the entire Overmind CLI invocation after login, including any polling for analysis or snapshot completion (e.g. `45m`). Accepts any Go duration string. Defaults to the CLI default of `31m`. Must be longer than the expected analysis time; the 30-minute service hard cap on analysis is separate from this value. Applies to all actions. | No       |
+| `change_analysis_target_duration` | Soft server-side target duration for change analysis planning used with `submit-plan` (e.g. `5m`, `20m`). The blast-radius phase uses 67% of this value; the remaining 33% covers hypothesis formation. Valid range: `1m`–`30m`. Defaults to account-level settings. | No       |
+| `blast_radius_link_depth` | How many relationship levels deep to traverse when calculating the blast radius (used with `submit-plan`). Larger values give a more complete picture but take longer. Defaults to account-level settings. | No       |
+| `blast_radius_max_items` | Maximum number of resources to include in the blast radius calculation (used with `submit-plan`). Larger values give a more complete picture but take longer. Defaults to account-level settings. | No       |
+| `risk_levels` | Comma-separated list of risk severities to include in the `wait-for-simulation` output (e.g. `high,medium`). Allowed values: `high`, `medium`, `low`. Defaults to all three. | No       |
+| `wait_for_snapshot` | When `true`, `start-change` blocks until the pre-change snapshot is fully captured before returning. Defaults to `false` (snapshot runs in background). | No       |
 
 ## Usage
 
@@ -192,6 +198,53 @@ By default, if the plugin step fails (e.g. Overmind API error, missing env var,
 
 Use `on_failure: pass` when the Overmind integration is optional and you do not want plugin failures to block deployments.
 
+### Tuning Analysis
+
+For large or complex infrastructure, you can tune how deep and how long the blast-radius analysis runs using three optional `submit-plan` inputs. These map directly to the corresponding Overmind CLI flags; see the [Overmind CLI configuration docs](https://docs.overmind.tech/cli/configuration) for full details.
+
+```yaml
+version: 2
+deploy:
+  steps:
+    terraformPlan:
+      after:
+        - name: Submit Plan to Overmind
+          use: https://github.com/overmindtech/env0-plugin
+          inputs:
+            action: submit-plan
+            api_key: ${OVERMIND_API_KEY}
+            timeout: 45m                         # wall-clock limit for the CLI invocation
+            change_analysis_target_duration: 15m # server-side analysis budget (1m–30m)
+            blast_radius_link_depth: 4           # relationship levels to traverse
+            blast_radius_max_items: 500          # max resources in blast radius
+```
+
+To limit which risk severities appear in the PR/MR comment, use `risk_levels` on `wait-for-simulation`:
+
+```yaml
+        - name: Post Overmind Simulation
+          use: https://github.com/overmindtech/env0-plugin
+          inputs:
+            action: wait-for-simulation
+            api_key: ${OVERMIND_API_KEY}
+            post_comment: true
+            comment_provider: github
+            risk_levels: high,medium # omit low-severity risks from the comment
+```
+
+To block `start-change` until the pre-change snapshot is fully captured before the apply proceeds:
+
+```yaml
+    terraformApply:
+      before:
+        - name: Mark Change Started
+          use: https://github.com/overmindtech/env0-plugin
+          inputs:
+            action: start-change
+            api_key: ${OVERMIND_API_KEY}
+            wait_for_snapshot: true
+```
+
 ### Complete Example
 
 Here's a complete example that uses the plan/change lifecycle actions:

env0.plugin.yaml

@@ -25,6 +25,24 @@ inputs:
   skip_after_approval:
     description: "When true (default), submit-plan exits early once a deployment has been approved (ENV0_REVIEWER_NAME is set), avoiding wasted resubmission of the post-approval re-plan. Set to false to submit on every plan, including the apply pipeline's re-plan."
     required: false
+  timeout:
+    description: "Wall-clock time limit for the entire Overmind CLI invocation after login, including any polling for analysis or snapshot completion (e.g. '45m'). Accepts any Go duration string. Defaults to the CLI default of 31m. Must be longer than the expected analysis time; the 30-minute service hard cap on analysis is separate from this value."
+    required: false
+  change_analysis_target_duration:
+    description: "Soft server-side target duration for change analysis planning used with submit-plan (e.g. '5m', '20m'). The blast-radius phase uses 67% of this value; the remaining 33% covers hypothesis formation. Valid range: 1m–30m. Defaults to account-level settings."
+    required: false
+  blast_radius_link_depth:
+    description: "How many relationship levels deep to traverse when calculating the blast radius (used with submit-plan). Larger values give a more complete picture but take longer. Defaults to account-level settings."
+    required: false
+  blast_radius_max_items:
+    description: "Maximum number of resources to include in the blast radius calculation (used with submit-plan). Larger values give a more complete picture but take longer. Defaults to account-level settings."
+    required: false
+  risk_levels:
+    description: "Comma-separated list of risk severities to include in the wait-for-simulation output (e.g. 'high,medium'). Allowed values: high, medium, low. Defaults to all three."
+    required: false
+  wait_for_snapshot:
+    description: "When true, start-change blocks until the pre-change snapshot is fully captured before returning. Defaults to false (snapshot runs in background)."
+    required: false
 run:
   exec: |
     #!/bin/sh
@@ -530,6 +548,18 @@ run:
             if [ -n "${DIFF_FILE}" ]; then
                 set -- "$@" --code-changes-diff "${DIFF_FILE}"
             fi
+            if [ -n "${inputs.change_analysis_target_duration}" ]; then
+                set -- "$@" --change-analysis-target-duration "${inputs.change_analysis_target_duration}"
+            fi
+            if [ -n "${inputs.blast_radius_link_depth}" ]; then
+                set -- "$@" --blast-radius-link-depth "${inputs.blast_radius_link_depth}"
+            fi
+            if [ -n "${inputs.blast_radius_max_items}" ]; then
+                set -- "$@" --blast-radius-max-items "${inputs.blast_radius_max_items}"
+            fi
+            if [ -n "${inputs.timeout}" ]; then
+                set -- "$@" --timeout "${inputs.timeout}"
+            fi
             "$@"
 
             # Clean up diff file if created
@@ -539,13 +569,30 @@ run:
             ;;
         start-change)
             echo "Starting change in Overmind..."
-            "${INSTALL_DIR}/overmind" changes start-change \
+            set -- "${INSTALL_DIR}/overmind" changes start-change \
                 --ticket-link "${ticket_link}"
+            if [ -n "${inputs.app}" ]; then
+                set -- "$@" --app "${inputs.app}"
+            fi
+            if [ "$(echo "${inputs.wait_for_snapshot}" | tr '[:upper:]' '[:lower:]')" = "true" ]; then
+                set -- "$@" --wait-for-snapshot
+            fi
+            if [ -n "${inputs.timeout}" ]; then
+                set -- "$@" --timeout "${inputs.timeout}"
+            fi
+            "$@"
             ;;
         end-change)
             echo "Ending change in Overmind..."
-            "${INSTALL_DIR}/overmind" changes end-change \
+            set -- "${INSTALL_DIR}/overmind" changes end-change \
                 --ticket-link "${ticket_link}"
+            if [ -n "${inputs.app}" ]; then
+                set -- "$@" --app "${inputs.app}"
+            fi
+            if [ -n "${inputs.timeout}" ]; then
+                set -- "$@" --timeout "${inputs.timeout}"
+            fi
+            "$@"
             ;;
         wait-for-simulation)
             echo "Waiting for Overmind simulation and commenting on PR/MR..."
@@ -574,6 +621,12 @@ run:
             if [ -n "${inputs.app}" ]; then
                 set -- "$@" --app "${inputs.app}"
             fi
+            if [ -n "${inputs.risk_levels}" ]; then
+                set -- "$@" --risk-levels "${inputs.risk_levels}"
+            fi
+            if [ -n "${inputs.timeout}" ]; then
+                set -- "$@" --timeout "${inputs.timeout}"
+            fi
             if ! "$@" > "${MARKDOWN_FILE}"; then
                 echo "Error: Failed to retrieve change markdown from Overmind"
                 exit 1