Skip to content

Commit

Permalink
Add watch path
Browse files Browse the repository at this point in the history
  • Loading branch information
farski committed Apr 19, 2024
1 parent e04a06c commit 7de3334
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 1 deletion.
3 changes: 2 additions & 1 deletion .github/workflows/deploy.yml
Original file line number Diff line number Diff line change
@@ -1,11 +1,12 @@
name: Deploy application
name: Deploy hosted zone and checks

on:
workflow_dispatch:
push:
branches:
- main
paths:
- .github/workflows/deploy.yml
- template.yml
- package.json
- yarn.lock
Expand Down
4 changes: 4 additions & 0 deletions components/ftp-connection-check/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

0 comments on commit 7de3334

Please sign in to comment.