14_Troubleshooting Infrastructure

This section provides basic approaches towards fixing AWS infrastructure problems within GitHub Actions.

• The Manual: Set up AWS GitHub Action fails!

-> If you chose either 'live' or 'test' as the deployment mode, you must choose and confirm forcing deployment, since these are possibly customer-facing systems. If you chose 'dev' and you already have a dev instance deployed, you must also force deployment.

• The Manual: Destroy AWS GitHub Action fails!

-> Ensure the corresponding environment is online. If you are trying to destroy a 'live' or 'test' system, you must force & confirm destruction. If you are trying to destroy a 'stage' system, you must enter the corresponding branch name, e.g. 'stage-180814'.

• The automatic dev update action fails!

-> Ensure you have set up a dev system. If the frontend is not reachable at its designated URL, the update action will fail with a corresponding message; this is to ensure we don't get undefined Terraform behavior.

• Creating a release draft fails!

-> Ensure the 'test' system is online, since this is where the release draft will be deployed. If you haven't set up the 'test' system yet, use the Manual: Set up AWS action with mode 'test'. Also, ensure your project can be properly built without any errors locally, since the built .zip files will be attached to the release (not including node_modules).

• Marking a release as live fails!

-> Ensure the 'live' system is online, since this is where the release draft will be deployed. If you haven't set up the 'live' system yet, use the Manual: Set up AWS action with mode 'live'.

• There is an empty temp workspace on terraform!

-> This workspace is used in the automated destruction steps for staging infrastructure. You may delete it, but it will be recreated anytime a staging environment is destroyed.