Add github actions for deploying AWS ECS envs #853
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create github actions for building and deploying LAMP-dashboard
Manual Actions:
stg
andprod
. Note that the input for this job is the DOCKER tag, not the git tag. Likely, the docker tags will be in the form ofmaster
,sha-somelongformatgitsha
, orgittag
(eg.2024.5.9
as is the preferred format in this repository)Automatic Actions:
master
, and deploy that image to the staging environment (stg
) using the image's checksum digest.edited
webhook type (among others), it will be triggered each time the base branch is updated. If there are lots of open pull requests, this could mean an unhelpful amount of rebuilds when master is updated.2024.5.9
will create a docker tag of2024.5.9
)Tasks or Callable Workflows:
These two workflows should not be called directly, but instead called by an "On "-style workflow. No need to do anything here, just wanted to explain all the new files. The "Build" task builds the docker image. The "Deploy" task deploys the docker task to the Digital Psych AWS ECS environment(s).
@MattMatt27 -- should be all set 🥳