Following a similar pattern to what is done by allen-cell-animated/nucmorp-colorizer I adapted the workflow per @meganrm Slack request wherein it is clarified to publish the main branch to staging on merge, then publish to production when a tag is pushed.
Type of change
Please delete options that are not relevant.
New feature (non-breaking change which adds functionality)
Change summary:
Create AWS Deployment Github Actions workflow
Steps to Verify:
After this PR is merged, and since the workflow is only triggered by pushes to the main branch, then we'll need to push a change to the main branch.
Verify that the AWS Deployment Github Actions workflow runs successfully; if not, proceed with troubleshooting.
Problem
Estimated review size: medium
#60596707 - GitHub Actions can publish releases to the staging-ipub-simularium and production-ipub-simularium S3 buckets and invalidate the CloudFront cache and the contents of the S3 buckets will be served from https://staging.simularium.allencell.org/learn/binding-affinity/ and https://simularium.allencell.org/learn/binding-affinity/
Solution
Following a similar pattern to what is done by
allen-cell-animated/nucmorp-colorizer
I adapted the workflow per @meganrm Slack request wherein it is clarified to publish the main branch to staging on merge, then publish to production when a tag is pushed.Type of change
Please delete options that are not relevant.
Change summary:
Steps to Verify: