Buddy

Guide Buddy Terraform Apply runs against different state unless tf_workspace matches the Plan action: Always set tf_workspace to the same value in both the Terraform Plan and Terraform Apply actions, e.g. production in both. Use this when y

Guide Buddy Terraform Apply reads the plan from $BUDDY_ACTION_TF_PLAN_OUTPUT_FILE, so keep Plan directly ahead of it: If you insert actions between Plan and Apply, disable the Plan action, or chain Apply after a different Plan, the default

Guide With manage_variables_by_yaml on, Buddy YAML owns the variables and UI edits get overwritten: Pick one owner and stick with it. If manage_variables_by_yaml is true on a pipeline, treat the YAML file as the single source of truth for v

Guide Buddy's TERRAFORM tool only goes up to 1.5.7; use OPENTOFU or CUSTOM for newer versions: If you need Terraform newer than 1.5.7 in a Buddy pipeline, pick tool OPENTOFU with the version you want, or use CUSTOM and point custom_binary_p

Fix for Buddy Trigger Pipeline with revision SPECIFIC needs specific_revision set, or it pins nothing: When triggering a pipeline on a specific revision, set both revision to SPECIFIC and specific_revision to the ref you mean (e.g. #$BUDDY_