@@ -31,7 +31,9 @@ Schemas are loaded into the Azure OSDU instance at deployment time through the d
...
@@ -31,7 +31,9 @@ Schemas are loaded into the Azure OSDU instance at deployment time through the d
The Microsoft version of OSDU enables support for multiple data partition separated by physical boundaries. While the MVP instance provided in Gitlab enables one data partition by default, [this section](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/infra/templates/osdu-r3-mvp/data_partition) walks you through the process of adding a new partition to your terraform deployment.
The Microsoft version of OSDU enables support for multiple data partition separated by physical boundaries. While the MVP instance provided in Gitlab enables one data partition by default, [this section](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/tree/master/infra/templates/osdu-r3-mvp/data_partition) walks you through the process of adding a new partition to your terraform deployment.
### Managing multiple environments
### Managing multiple environments
Multiple OSDU environments can be supported in Azure as multiple OSDU deployments using the same TF scripts. There are two ways to deploy into multiple environments:
1- Automatically, by using Gitlab mirroring into your person ADO environment, and using ADO deployment pipelines
2- Manually, by using a modified version of the following [helm charts](https://community.opengroup.org/osdu/platform/deployment-and-operations/helm-charts-azure)