Auto-install AWS CLI in runner if missing
Some checks failed
Deploy Hello Lambda CFT / deploy (push) Failing after 11s

This commit is contained in:
Vijaya Krishna Manne 2026-05-29 14:14:19 -04:00
parent 17ab6b480e
commit 7102aa3232

View file

@ -28,13 +28,37 @@ jobs:
echo "SRC_DIR=${SRC_DIR}" >> "$GITHUB_ENV" echo "SRC_DIR=${SRC_DIR}" >> "$GITHUB_ENV"
echo "Using source directory: ${SRC_DIR}" echo "Using source directory: ${SRC_DIR}"
- name: Ensure Docker is available - name: Ensure AWS CLI
run: | run: |
if ! command -v docker >/dev/null 2>&1; then set -e
echo "docker is not available on this runner." if command -v aws >/dev/null 2>&1; then
exit 1 aws --version
exit 0
fi fi
docker --version
# Try local AWS CLI v2 install (no root required).
if command -v curl >/dev/null 2>&1 && command -v unzip >/dev/null 2>&1; then
TMP_DIR="$(mktemp -d)"
curl -fsSL "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "${TMP_DIR}/awscliv2.zip"
unzip -q "${TMP_DIR}/awscliv2.zip" -d "${TMP_DIR}"
"${TMP_DIR}/aws/install" -i "$HOME/.aws-cli" -b "$HOME/.local/bin" || true
if [ -x "$HOME/.local/bin/aws" ]; then
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
"$HOME/.local/bin/aws" --version
exit 0
fi
fi
# Fallback to pip user install.
if command -v python3 >/dev/null 2>&1; then
python3 -m pip install --user --upgrade awscli
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
"$HOME/.local/bin/aws" --version
exit 0
fi
echo "Unable to install aws CLI on this runner."
exit 1
- name: Check required AWS secrets - name: Check required AWS secrets
run: | run: |
@ -50,36 +74,19 @@ jobs:
- name: Verify AWS identity - name: Verify AWS identity
run: | run: |
set -e set -e
if ! docker run --rm \ if ! aws sts get-caller-identity; then
-e AWS_ACCESS_KEY_ID \
-e AWS_SECRET_ACCESS_KEY \
-e AWS_SESSION_TOKEN \
-e AWS_DEFAULT_REGION \
amazon/aws-cli:2 sts get-caller-identity; then
echo "AWS authentication failed. If using STS creds, regenerate and update all 3 secrets: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN." echo "AWS authentication failed. If using STS creds, regenerate and update all 3 secrets: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN."
exit 1 exit 1
fi fi
- name: Validate CFT - name: Validate CFT
run: | run: |
docker run --rm \ aws cloudformation validate-template \
-e AWS_ACCESS_KEY_ID \ --template-body "file://${SRC_DIR}/infra/hello-lambda.yml"
-e AWS_SECRET_ACCESS_KEY \
-e AWS_SESSION_TOKEN \
-e AWS_DEFAULT_REGION \
-v "$PWD/${SRC_DIR}/infra:/infra" \
amazon/aws-cli:2 cloudformation validate-template \
--template-body file:///infra/hello-lambda.yml
- name: Deploy CFT - name: Deploy CFT
run: | run: |
docker run --rm \ aws cloudformation deploy \
-e AWS_ACCESS_KEY_ID \
-e AWS_SECRET_ACCESS_KEY \
-e AWS_SESSION_TOKEN \
-e AWS_DEFAULT_REGION \
-v "$PWD/${SRC_DIR}/infra:/infra" \
amazon/aws-cli:2 cloudformation deploy \
--stack-name hello-lambda-stack \ --stack-name hello-lambda-stack \
--template-file /infra/hello-lambda.yml \ --template-file "${SRC_DIR}/infra/hello-lambda.yml" \
--capabilities CAPABILITY_NAMED_IAM --capabilities CAPABILITY_NAMED_IAM