define process for re-deploying the service

[elrayle]

Need to define the process for re-deploying/update/re-start the service through GitHub actions...

for -int:

• Trigger: when the -int private authority_lookup image changes
• Trigger: when the dev branch changes
  • adding/updating authority configs
  • updating the customized footer

for -stg:

• Trigger: when the -stg private authority_lookup image changes
• Trigger: when the main branch changes
  • adding/updating authority configs
  • updating the customized footer

for -prod:

• Trigger: manual deploy
  • when the -prod private authority_lookup image changes
  • when this repo is released

[elrayle]

I believe this is handled by the deploy github actions for -int, -stg, and -prod. These need to be tested to confirm they work as expected.

PR #9 added the deploy action for integration. This is tested and completes without error, but additional testing is required to confirm that it is fully functional and redeploys the service.

PR #12 adds the deploy actions for staging and production. This is tested and completes without error, but additional testing is required to confirm that it is fully functional and redeploys the service. There is additional remaining work for stg and prod. See the PR for more info on the remaining work.

[elrayle]

Also, the actions triggered by changes to the images is TBD. Quite a bit of exploration was done, but a clear solution was not identified.

[elrayle]

Moved remaining work specific to changes in AWS ECR images to Issue #20.