Customizing the Settings
All customer-specific customizations and configurations are handled by Terraform before deployment.
To see the repository:
In Azure, click the Repos icon.

In the header, click OpComm, and then use the search field to select the
OpComm_Terraformrepository.
On the left, you see different type of Terraform files.

Expand the tvars directory.

The
<client>.auto.tfvarsfile is where all configuration is done. Each client has one, with their specific customizations. For example,hideClinicalPortalLinkis currently set toTruefor the dummy environment. Client ABC might set it toFalse.Note: The first segment of the file named after the client. For example, the dummy environment uses
dummy.auto.tfvarsbut for client, ABC, the file might beabc.auto.tfvars.
Note: Any updates for the Terraform-related changes should be handled by the DevOps team before the release.
Future plan: This file is currently hard coded but the plan is to make it be fully dynamic. For example, wherever “client” appears, this part is dynamic and will change. If you run the pipeline and choose dummy, then the client name will be updated with “dummy.” This is planned for all other app settings that can be updated so those parts will also be updated dynamically.
Last updated
