Miscellaneous

This section discusses some potential troubleshooting and future plans.

Planned Upgrades to Editing

Future upgrades will:

• make the pipeline more efficient

• make it easier to select the various services or the customizations

The goal is to be able update everything from the Library (OpComm > Pipelines > Library) instead of being hardcoded in the tfvar file as it is currently. For example, the #{location} value.

In the future, you can update it in the Library instead of the tfvar file. When the Terraform pipeline runs, it will dynamically update the tfvars file from the library variable group.

Order of Operations

1. The DevOps team will prepare everything for the production deployments, such as the tfvar files, the Terraform configuration, etc.

2. Two or three days before production, DevOps will run the Terraform pipeline.

3. When the pipeline hits the Approval Gate, DevOps will verify that everything looks good and create a change request.

4. On the day of production, the Deployment team will approve that change onto the pipeline, and then this part will be deployed.

Disaster Recovery/Crashes

• If a crash occurs on the infrastructure level, then we will do the Terraform deployment again and then for code deployment again.

• If a crash occurs because of a code issue (bugs), the developers will fix the code side and we will create one more release branch and do the deployment. The build and deployment only.

• If a database crashes, we can use the backup and deploy the code again. Currently, database backup is enabled but disaster recovery is not. That will require some additional development time.

Creating a New Client

The DevOps team can do this in both the OpComm Terraform pipeline and the Web Deployment pipeline. This example covers the OpComm Terraform pipeline.

1. Go to Pipelines > OpComm Terraform > terraform.yml.

   
2. Go to parameters > Client > values.

3. Add a new line and type the name of the new client. For example, abc.

   
4. Click Validate and save.

5. Click Save.

6. Click Run.

   On the Run pipeline window, the new abc client is now available under Hospital.

   

Templates

For the OpComm Terraform pipeline, Asish created some templates that pass the values for the Terraform Plan and Terraform Apply stages. The templates are easy to call and to use. Currently, Asish is the only one who can approve the Approval Gate, but he will create a group and add Support, DevOps, and Development. He has created templates for the Web Deployment pipeline, as well, and will create a similar approval group there.

In the Web Deployment pipeline, due to the number of app services, Asish created a template to call for all app services, such as OpCommAdminPortal and OpCommPortal.

In the future, if the Development team adds a new app service, copy all the lines related to the app service, paste it, and update the configuration, such as the csproj path and the artifact name.