JASPER-223: Deploy JASPER application to Test

[ronaldo-macapobre]

Pull Request for JIRA Ticket: JASPER-223

Issue ticket number and link

https://jag.gov.bc.ca/jira/browse/JASPER-223

Description

Github Actions

• Updated build-infra pipeline to simplify logic for building, scanning and executing terraform plan command.
• Updated publish-infra pipeline to combine jobs to a single job that deploys the initial stack, deploys the dummy-image (for ECR and Lambda) and finally, the main stack to provision Jasper's cloud infrastructure
• Enable deploy2test job to deploy the frontend (web) and backend (api) applications

Openshift

• Updated sync-secrets and update-aws-creds scripts to be able to target environment to deploy.
• Separate each Openshift objects per environment

Terraform

• Combined the initial stack and main stack to a one file so that it would be easy to use one Terraform state file.
• Added missing db_subnet_group for the Postgres db which was originally created via Console
• Moved initial stack to modules.

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

• Deployed using working branch to the dev and test
• Verified that Jasper is accessing using the test environment URL.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings

[WadeBarnes]

Overall LGTM. I'll defer to @amlanc1 for final review and approval.

One question though. Would using Terraform workspaces simplify the management of the various environments? e.g. Reduce the number of files and any duplication.

[ronaldo-macapobre]

Overall LGTM. I'll defer to @amlanc1 for final review and approval.

One question though. Would using Terraform workspaces simplify the management of the various environments? e.g. Reduce the number of files and any duplication.

Thank you for the advanced review. I was meaning to mark this as ready for PR review once I resolved the build errors found by the pre-checks and cleanup.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[amlanc1]

Approved... looks good to be deployed. For now the environment folders are ok. We can look at Terragrunt for better environment management in Terraform. The Terraform workspace wont work for our use case as Workspace is mostly applicable when working with single state file. But here we have separate state files in each environment.