Retry allocation in multiple zones/regions if there is no capacity (#231)

* add ability to specify multiple availability zones

* add multi-region support to the availability zone spec

* do best effort to remove ec2 instance if there is no runner label

* add default startup timeout

* fix parsing of gh timeout config

Author: yonch

action.yml

@@ -15,10 +15,20 @@ inputs:
     description: >-
       GitHub Personal Access Token with the 'repo' scope assigned.
     required: true
+  availability-zones-config:
+    description: >-
+      JSON string array of objects with configurations for multiple availability zones.
+      Each object should contain 'imageId', 'subnetId', and 'securityGroupId'.
+      Optionally, you can specify 'region' to launch the instance in a specific AWS region.
+      If 'region' is not specified, the default AWS_REGION environment variable will be used.
+      Example: '[{"imageId":"ami-123","subnetId":"subnet-123","securityGroupId":"sg-123"},{"imageId":"ami-456","subnetId":"subnet-456","securityGroupId":"sg-456","region":"us-west-2"}]'
+      When provided, the action will try each configuration in sequence until a successful instance is launched.
+      This takes precedence over individual ec2-image-id, subnet-id, and security-group-id parameters.
+    required: false
   ec2-image-id:
     description: >-
       EC2 Image Id (AMI). The new runner will be launched from this image.
-      This input is required if you use the 'start' mode.
+      This input is required if you use the 'start' mode and don't provide availability-zones-config.
     required: false
   ec2-instance-type:
     description: >-
@@ -28,14 +38,14 @@ inputs:
   subnet-id:
     description: >-
       VPC Subnet Id. The subnet should belong to the same VPC as the specified security group.
-      This input is required if you use the 'start' mode.
+      This input is required if you use the 'start' mode and don't provide availability-zones-config.
     required: false
   security-group-id:
     description: >-
       EC2 Security Group Id.
       The security group should belong to the same VPC as the specified subnet.
       The runner doesn't require any inbound traffic. However, outbound traffic should be allowed.
-      This input is required if you use the 'start' mode.
+      This input is required if you use the 'start' mode and don't provide availability-zones-config.
     required: false
   label:
     description: >-
@@ -88,17 +98,20 @@ inputs:
     description: >-
       Specifies the retry interval in seconds to register the runner after the quiet period.
     required: false
-  startup-timeout-seconds:
+  startup-timeout-minutes:
     description: >-
-      Specifies the timeout in seconds to register the runner after the quiet period.
+      Specifies the timeout in minutes to register the runner after the quiet period.
+    required: false
+    default: '5'
   run-runner-as-service:
-    type: boolean
     description: >-
       Start the runner as a service rather than using ./run.sh as root.
     required: false
+    default: 'false'
   run-runner-as-user:
     description: >-
       Specify user under whom the runner service should run
+    required: false
   ec2-volume-size:
     description: >-
       EC2 volume size in GB.
@@ -124,6 +137,10 @@ outputs:
     description: >-
       EC2 Instance Id of the created runner.
       The id is used to terminate the EC2 instance when the runner is not needed anymore.
+  region:
+    description: >-
+      AWS region where the EC2 instance was created.
+      This is useful for subsequent AWS operations on the instance.
 runs:
   using: node20
   main: ./dist/index.js