...
Review bicep deployment files (azuredeploy. *) under project repository folder AzureDeployment
Review
skuvalues for resources and update as necessary. The sku values are inside of bicep templates in repository: Infrastructure/AzureDeployment/azuredeploy.*.bicepIn the same bicep files optionally set
deploymentflag to false if the associated resource did not need to be deployed. It is set to true by default.
Configure the variables for each azure resource deployment DevOps pipelines
Edit DevOps pipelines under Pipelines → All → Azure Deployment folder
Configure variables listed for each deployment pipeline in Appendix section 1. For secured variables, need to re-create the value and check “Keep this value secret” checkbox after adding the value
Run the first deployment pipeline Azure Resources Deployment 1 (Initial). This will create container registry, keyvault and app service plan resources
Create a folder by environment name in DevOps pipeline and clone/create DevOps CI/CD pipelines for Vessel Registry and Shared (Dsd Marine) app services.
Configure new cloned/created DevOps CI/CD pipelines for specified resource groups, container image name and container image tag. Then build the pipelines. Please refer to the Appendix section 2 for the container name, image name and image tag.
Update the deployment pipeline variables and run the remaining two: Azure Resources Deployment 2 (Safsecsur) and Azure Resources Deployment 3 (Eregistry). Verify the resources has been deployed successfully in Azure Portal → Resource Group → Deployments
Add keyvault secrets used for applications from created resources. Please refer to the Appendix section 3 for the required application secrets (Optional: Configure Access Policies in the KeyVault)
Create a Variable group in DevOps → Pipelines → Library. Toggle “Link Secrets” option, select appropriate Azure subscription → KeyVault name, add all the necessary keys and save the variable group
Add workmanagementservice appservice outbound IP addresses to Postgresql server connection security (Have to do this for documentmanagement service too)
Add/Create a “Diagnostics Settings” to all the appservices on Azure portal
Link and save the new variable group in all the DevOps CI/CD pipelines
Make sure to use the correct branch(Develop/Master) on all the DevOps CI/CD pipelines
Migrate LOV Azure Cosmos DB data using Microsoft tool or Console App
Create Application Registration for Vessel Registration internal and external websites. Please refer to below Application Registration section.
Run DevOps CI/CD pipelines again and verify the applications runs as expected.
...
Key Name | Value or Derived from | Required for | ResourceGroup to be updated |
|---|---|---|---|
| Deployment Environment Resource Group → Application Insights → {Application Insight Name} → Overview → Instrumentation Key |
|
|
| Deployment Environment Resource Group → Application Insights → {Application Insight Name} → Overview → Instrumentation Key |
|
|
| Deployment Environment Resource Group → Application Insights → {Application Insight Name} → Overview → Instrumentation Key |
|
|
| Deployment Environment Resource Group → Application Insights → {Application Insight Name} → Overview → Instrumentation Key |
|
|
| Deployment Environment Resource Group → Service Bus → {Service Bus Name} → Settings → Shared access policies → Policy → Primary Connection String |
|
|
| Deployment Environment Resource Group → Azure Cosmos DB → { Cosmos DB Name } → Settings → Connection String → Primary Connection String |
|
|
| Deployment Environment Resource Group → Azure Cache For Redis → { Azure Cache Redis Name } → Settings → Access Keys → Primary Connection String (StackExchange.Redis) |
|
|
| Deployment Environment Resource Group → Azure Database for PostgreSQL servers → { PostreSQL Server Name } → Settings → Connection Strings → ADO.NET After obtaining the ADO.NET connectionstring, replace {your_database} and {your_password} values with database name and database/server password respectively |
|
|
| Deployment Environment Resource Group → Storage accounts → Access keys → Click on “Show keys” → Connection string |
|
|
| Deployment Environment Resource Group → App Services → { List Of Value Service Name } → Overview → URL After obtaining the URL append “/ListOfValue“ to it, excluding the quotation marks. {URL}/ListOfValue |
|
|
| Deployment Environment Resource Group → App Services → { List Of Value Service Name } → Overview → URL After obtaining the URL append “/ListOfValueType“ to it, excluding the quotation marks. {URL}/ListOfValueType |
|
|
| Deployment Environment Resource Group → App Services → { Document Service Name } → Overview → URL Service is developed by Team Ninja Turtles, and will be located in their resource group. |
|
|
| Deployment Environment Resource Group → API Management services → { APIM Name } → Overview → Gateway URL After obtaining the Gateway URL append “/wms/api/v1“ to it, excluding the quotation marks. {URL}/wms/api/v1 |
|
|
| The API key can be obtained by checking with Walter Hoban, or Team Kraken. |
|
|
App Registration Flowchart
...