From 7de333412db4e45806601dc67882a5679c3648f1 Mon Sep 17 00:00:00 2001 From: Chris Kalafarski Date: Fri, 19 Apr 2024 14:31:59 -0400 Subject: [PATCH] Add watch path --- .github/workflows/deploy.yml | 3 ++- components/ftp-connection-check/README.md | 4 ++++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 0d824b6..4dff1cc 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -1,4 +1,4 @@ -name: Deploy application +name: Deploy hosted zone and checks on: workflow_dispatch: @@ -6,6 +6,7 @@ on: branches: - main paths: + - .github/workflows/deploy.yml - template.yml - package.json - yarn.lock diff --git a/components/ftp-connection-check/README.md b/components/ftp-connection-check/README.md index 7edbf3b..49d2c30 100644 --- a/components/ftp-connection-check/README.md +++ b/components/ftp-connection-check/README.md @@ -7,3 +7,7 @@ It's expected that, for any given production FTP server, several of these stacks The status of the Route 53 health check matches the state of a CloudWatch alarm that is also created in the stack. The the Lambda function that is actually running the connection tests fails, the CloudWatch alarm will move into an ALARM state, which will cause the health check to move into an UNHEALTHY state. On their own, these health checks don't have any impact on other Route 5 resources, like DNS records. Other Route 53 health checks should be created that list these health checks as _child health checks_. + +### Deployment + +Deployment is expected to be handled by a continuous deployment GitHub Action (see deploy.yml), which uses a matrix strategy to deploy the correct combination of check- and target-regions.