Amended custom/variables test

app/spec/lib/bk/compat/bitbucket/__snapshots__/spec/lib/bk/compat/bitbucket/examples/custom/variables.yml.snap

@@ -1,6 +1,11 @@
 ---
 steps:
-- group: default
+- key: execute-34fda39a698739f93a76af1583cf0b9e937f3561
+  prompt: Execute step 34fda39a698739f93a76af1583cf0b9e937f3561?
+  input: execute-34fda39a698739f93a76af1583cf0b9e937f3561
+- group: deployer
+  depends_on:
+  - execute-34fda39a698739f93a76af1583cf0b9e937f3561
   steps:
   - key: custom-vars
     fields:

app/spec/lib/bk/compat/bitbucket/examples/custom/variables.yml

@@ -1,18 +1,19 @@
 # from https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/#Example-%E2%80%94-using-the-variables-property-to-define-custom-pipeline-variables
 
 pipelines:
-  default:
-    - variables:
-        - name: Username
-        - name: Role
-          default: "admin"          # optionally provide a default variable value
-          description: "Add user role"
-        - name: Region
-          default: "us-east-1"
-          allowed-values:           # optionally restrict variable values
-            - "ap-southeast-2"
-            - "us-east-1"
-            - "us-west-2"
-    - step:
-        script:
-          - echo "$Username manually triggered for a build for $Region as $Role!"
+  custom:
+    deployer: # The name that is displayed in the list in the Bitbucket Cloud GUI
+      - variables:
+          - name: Username
+          - name: Role
+            default: "admin"          # optionally provide a default variable value
+            description: "Add user role"
+          - name: Region
+            default: "us-east-1"
+            allowed-values:           # optionally restrict variable values
+              - "ap-southeast-2"
+              - "us-east-1"
+              - "us-west-2"
+      - step:
+          script:
+            - echo "$Username manually triggered for a build for $Region as $Role!"