Skip to content

Commit

Permalink
Fix Inline Documentation
Browse files Browse the repository at this point in the history
Why these changes are being introduced:
There was a discrepancy between the documentation in the production GHA
workflow for deploying the app and what the workflow actually did.

How this addresses that need:
* Fix the comment header for the prod deploy workflow for the Lambda
function

Side effects of this change:
None.
  • Loading branch information
cabutlermit committed Jan 24, 2024
1 parent d4e87d1 commit d5acd48
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions .github/workflows/prod-cf-deploy-lambda.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
### This is the Terraform-generated GitHub Actions workflow for cf-lambda ###
### applications for dev/stage/prod. It will publish the Lambda zip to S3 ###
### and automatically re-apply Terraform in the Terraform Cloud ###
### workloads-libraries-website-prod workspace. ###
### and automatically run Terraform in the Terraform Cloud ###
### workloads-libraries-website-prod workspace. It will NOT auto-apply in ###
### Terraform Cloud; rather, TfC will wait for human input to either cancel ###
### or apply the result. ###
name: Prod CF Lambda@Edge Full Deploy

on:
Expand Down

0 comments on commit d5acd48

Please sign in to comment.