Add launch-ec2-runner-with-fallback action

This action is used to launch an EC2 instance (either as a spot instance or a dedicated instance) in a desired availability zone. If no availability, then backup availability zones will be tried until one is successful.

Signed-off-by: Courtney Pacheco <[email protected]>

Author: courtneypacheco

.github/workflows/lint.yml

@@ -52,17 +52,15 @@ jobs:
           - name: "ruff"
             commands: |
               tox -e ruff
-          ## TODO: Uncomment `pylint` once the first in-house, Python-based action is merged
-          # - name: "pylint"
-          #   commands: |
-          #     echo "::add-matcher::.github/workflows/matchers/pylint.json"
-          #     tox -e fastlint
-          #     tox -e lint
-          ## TODO: Uncomment `mypy` once the first in-house, Python-based action is merged
-          # - name: "mypy"
-          #   commands: |
-          #     echo "::add-matcher::.github/workflows/matchers/mypy.json"
-          #     tox -e mypy
+          - name: "pylint"
+            commands: |
+              echo "::add-matcher::.github/workflows/matchers/pylint.json"
+              tox -e fastlint
+              tox -e lint
+          - name: "mypy"
+            commands: |
+              echo "::add-matcher::.github/workflows/matchers/mypy.json"
+              tox -e mypy
           - name: "yamllint"
             commands: |
               tox -e yamllint

.isort.cfg

@@ -7,4 +7,9 @@ import_heading_thirdparty=Third Party
 import_heading_firstparty=First Party
 import_heading_localfolder=Local
 known_firstparty=
-known_localfolder=tuning
+known_localfolder=tuning
+
+# isort falsely flags some GitHub action Python files as problematic, and tries to add
+# comments to existing import statements for the wrong reasons. Therefore, we skip these
+# files
+skip_glob=actions/launch-ec2-runner-with-fallback/launch_ec2_runner/*.py

.yamllint.yaml

@@ -8,4 +8,7 @@ rules:
   line-length:
     max: 120
     allow-non-breakable-words: true
-    allow-non-breakable-inline-mappings: false
+    allow-non-breakable-inline-mappings: false
+    ignore:
+      # REASON: This file needs lines that are longer than 120 in order to load variables to the env
+      - /actions/launch-ec2-runner-with-fallback/action.yml

README.md

@@ -16,6 +16,7 @@ Below is a list of the in-house GitHub actions stored in this repository:
 | Name | Description | Example Use Cases |
 | --- | --- | --- |
 | [free-disk-space](./actions/free-disk-space/free-disk-space.md) | Used to reclaim disk space on either a GitHub or EC2 runner. | <ul><li>If a CI job tends to fail due to "insufficient disk space"</li><li>If you want to reduce cloud costs by reclaiming disk space instead of increasing your writeable cloud storage to compensate for a bloated EC2 image</li></ul> |
+| [launch-ec2-runner-with-fallback](./actions/launch-ec2-runner-with-fallback/launch-ec2-runner-with-fallback.md) | Used launch an EC2 instance in AWS, either as a spot instance or a dedicated instance. If your preferred availability zone lacks availability for your instance type, "backup" availability zones will be tried. | <ul><li>Insufficient capacity in AWS (i.e., AWS lacks availablility for your desired EC2 instance type in your preferred availability zone)</li><li>Cost savings (i.e., You want to try launching your EC2 runner as a spot instance first)</li></ul> |
 
 ## How to Use One or More In-House GitHub Actions
 

actions/free-disk-space/action.yml

@@ -1,5 +1,8 @@
+# SPDX-License-Identifier: Apache-2.0
+
 name: 'Free Disk Space'
 description: 'Frees disk space on the runner'
+author: 'InstructLab'
 runs:
   using: "composite"
   steps: