| Info |
|---|
Refer to the page about location of deployed artifacts for environment information. |
1. Branch Management
Guidance on branching strategy presents a typical pattern that we can apply to our work. In a nutshell, the feature branches are for work in progress, the non-versioned branches map to a specific deployment environment and the numbered branches for release and hotfix relate to work in progress on shippable and shipped code respectively. Once code is released, the master branch is tagged with the same release number of the corresponding branch.
2. Release Steps
Use the infrastructure pipeline to create and publish all Azure services to the correct resource group
Create/update application settings in the app service
Create/update all dashboard key vault values
Create/update all application settings (ie appsettings.<environment>.json) in the solution
Ask cloud group to grant all API permissions needed by the application in the Azure AD app registration
Ensure an application role is created so that we can later assign Azure AD user groups to that role
Navigate to the enterprise application settings and assign Azure AD user groups to a role in the application
