... | ... | @@ -57,9 +57,9 @@ The Azure deployment provides configuration templates to enable customers to dep |
|
|
|
|
|
|
|
|
### Continuous delivery pipelines
|
|
|
- link to [infrastructure automation](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/infra-automation.md)
|
|
|
- [service automation](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-automation.md)
|
|
|
- OSDU code, including Azure code, can be deployed directly from Gitlab. the following pipelines include service-level deployment scripts
|
|
|
- The [infrastructure automation](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/infra-automation.md) configuration section needs to be edited to connect to your own Azure subscription and credentials.
|
|
|
- The [service automation](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-automation.md) templates hold the environment variables and configuration for service deployments into OSDU on Azure.
|
|
|
- OSDU code, including Azure code, can be deployed directly from Gitlab. Each cloud provider publishes their custom pipeline to the [CI/CD repository](https://community.opengroup.org/osdu/platform/ci-cd-pipelines). For Azure, we currently deploy into the staging environment to validate code merges and run tests in alignment with the agreed CI/CD standards for OSDU, however, for private deployments, we recommend deploying from a private [ADO environment](https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/docs/service-onboarding.md#development-and-demo-azure-devops-pipelines).
|
|
|
|
|
|
|
|
|
### Release Strategy
|
... | ... | |