Releasing Code

insights+ is comprised of a core framework that includes both front and back-end components, as well as a variety of support services to deliver data. All UI components are released with the insights+ core.

The details below describe the release of the code components. Please ensure that the databases and data within are up-to-date prior to releasing code.

insights+ Core

NOTE: Prior to release a new version, ensure that the insights+ GCC Infrastructure is up-to-date.

In order to release the latest version of insights+ core, two steps need to be taken:

• The develop branch should be merged into main via a pull request.
• Once this is complete, a new release should be created. Include the release number in the description. Once the release is created, it should automatically deploy.

Supporting Services

Additional components within insights+ are supported via individual functions deployed independently. If no changes have been made, these do not need to be deployed.

Products Back End

Analyzer Back End

Use a pull request to merge the dev branch into the main branch. The code FROM THE MAIN branch will then need to be manually deployed to Analyzer function (typically via visual studio).

Reports and Certification Back End

This is typically deployed in tandem with the Certification backend. The reports functionality is primarily concerned with generating the content for NSWERS reports (currently the certification report). It is two components: the primary components which is deployed in Azure Commercial, as well as a helper component deployed to GCC to aid in aggregation non-deidentified data from the raw data files for the Certification process.

Although it operates on three separate Azure functions, the code is in a single solution.

To deploy, start by completing a pull request from the staging branch into the main branch.

Reports Component

Auto deploy on merge into main.

Reports – Secure (Azure GCC) Component

Auto deploy on merge into main.

Certification Component

Auto deploy on merge into main.

Utilities Back End

Secure Utilities Back End

R Runner

1. Use a pull request to merge the staging branch into the master branch.
2. In the staccrunner storage account queue called jobs (production) or jobs-staging (staging), create a new object to get update the code:
   • {“task”:”update”}

R Data Loader