You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/automation/configure-devops.md
+33-27Lines changed: 33 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,11 +156,11 @@ Record the URL of the project.
156
156
157
157
### Import the repository
158
158
159
-
Start by importing the SAP Deployment Automation Framework GitHub repository into Azure Repos.
159
+
Start by importing the SAP Deployment Automation Framework Bootstrap GitHub repository into Azure Repos.
160
160
161
161
Go to the **Repositories** section and select **Import a repository**. Import the `https://github.com/Azure/sap-automation-bootstrap.git` repository into Azure DevOps. For more information, see [Import a repository](/azure/devops/repos/git/import-git-repository?view=azure-devops&preserve-view=true).
162
162
163
-
If you're unable to import a repository, you can create the repository manually. Then you can import the content from the SAP Deployment Automation Framework GitHub repository to it.
163
+
If you're unable to import a repository, you can create the repository manually. Then you can import the content from the SAP Deployment Automation Framework GitHub Bootstrap repository to it.
164
164
165
165
### Create the repository for manual import
166
166
@@ -188,7 +188,7 @@ Copy the content from the .zip file to the root folder of your local clone.
188
188
189
189
Open the local folder in Visual Studio Code. You should see that changes need to be synchronized by the indicator by the source control icon shown here.
190
190
191
-
:::image type="content" source="./media/devops/automation-vscode-changes.png" alt-text="Screenshot that shows that source code has changed.":::
191
+
:::image type="content" source="./media/devops/automation-vscode-changes.png" alt-text="Screenshot that shows that source code is changed.":::
192
192
193
193
Select the source control icon and provide a message about the change. For example, enter **Import from GitHub** and select Ctrl+Enter to commit the changes. Next, select **Sync Changes** to synchronize the changes back to the repository.
194
194
@@ -200,6 +200,7 @@ You can either run the SAP Deployment Automation Framework code directly from Gi
200
200
201
201
If you want to run the SAP Deployment Automation Framework code from the local Azure DevOps project, you need to create a separate code repository and a configuration repository in the Azure DevOps project:
202
202
203
+
-**Name of configuration repository**: `Same as the DevOps Project name`. Source is `https://github.com/Azure/sap-automation-bootstrap.git`.
203
204
-**Name of code repository**: `sap-automation`. Source is `https://github.com/Azure/sap-automation.git`.
204
205
-**Name of sample and template repository**: `sap-samples`. Source is `https://github.com/Azure/sap-automation-samples.git`.
205
206
@@ -260,18 +261,19 @@ del manifest.json
260
261
261
262
Save the app registration ID and password values for later use.
262
263
263
-
## Create Azure pipelines
264
+
## Create Azure Pipelines
264
265
265
-
Azure pipelines are implemented as YAML files. They're stored in the *deploy/pipelines* folder in the repository.
266
+
Azure Pipelines are implemented as YAML files. They're stored in the *deploy/pipelines* folder in the repository.
266
267
267
268
## Control plane deployment pipeline
268
269
269
270
Create the control plane deployment pipeline. Under the **Pipelines** section, select **New Pipeline**. Select **Azure Repos Git** as the source for your code. Configure your pipeline to use an existing Azure Pipelines YAML file. Specify the pipeline with the following settings:
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **Control plane deployment**.
@@ -282,8 +284,9 @@ Create the SAP workload zone pipeline. Under the **Pipelines** section, select *
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **SAP workload zone deployment**.
@@ -294,8 +297,9 @@ Create the SAP system deployment pipeline. Under the **Pipelines** section, sele
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **SAP system deployment (infrastructure)**.
@@ -306,6 +310,7 @@ Create the SAP software acquisition pipeline. Under the **Pipelines** section, s
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **SAP configuration and software installation**.
@@ -330,8 +336,9 @@ Create the deployment removal pipeline. Under the **Pipelines** section, select
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **Deployment removal**.
@@ -342,8 +349,9 @@ Create the control plane deployment removal pipeline. Under the **Pipelines** se
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **Control plane removal**.
@@ -354,9 +362,10 @@ Create the deployment removal Azure Resource Manager pipeline. Under the **Pipel
| Name | Deployment removal using Azure Resource Manager|
360
369
361
370
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **Deployment removal using ARM processor**.
362
371
@@ -369,18 +378,15 @@ Create the repository updater pipeline. Under the **Pipelines** section, select
Save the pipeline. To see **Save**, select the chevron next to **Run**. Go to the **Pipelines** section and select the pipeline. Choose **Rename/Move** from the ellipsis menu on the right and rename the pipeline as **Repository updater**.
377
387
378
388
This pipeline should be used when there's an update in the sap-automation repository that you want to use.
379
389
380
-
## Import the Ansible task from Visual Studio Marketplace
381
-
382
-
The pipelines use a custom task to run Ansible. You can install the custom task from [Ansible](https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.vss-services-ansible). Install it to your Azure DevOps organization before you run the **Configuration and SAP installation** or **SAP software acquisition** pipelines.
383
-
384
390
## Import the cleanup task from Visual Studio Marketplace
385
391
386
392
The pipelines use a custom task to perform cleanup activities post deployment. You can install the custom task from [Post Build Cleanup](https://marketplace.visualstudio.com/items?itemName=mspremier.PostBuildCleanup). Install it to your Azure DevOps organization before you run the pipelines.
@@ -422,7 +428,7 @@ Create a new variable group named `SDAF-General` by using the **Library** page i
422
428
| Branch | main ||
423
429
| S-Username |`<SAP Support user account name>`||
424
430
| S-Password |`<SAP Support user password>`| Change the variable type to secret by selecting the lock icon. |
425
-
|`tf_version`| 1.3.0 | The Terraform version to use. See [Terraform download](https://www.terraform.io/downloads). |
431
+
|`tf_version`| 1.6.0 | The Terraform version to use. See [Terraform download](https://www.terraform.io/downloads). |
426
432
427
433
Save the variables.
428
434
@@ -449,11 +455,11 @@ Create a new variable group named `SDAF-MGMT` for the control plane environment
| CP_ARM_TENANT_ID |`Tenant ID` for the service principal ||
457
463
| AZURE_CONNECTION_NAME | Previously created connection name ||
458
464
| sap_fqdn | SAP fully qualified domain name, for example, `sap.contoso.net`| Only needed if Private DNS isn't used. |
459
465
| FENCING_SPN_ID |`Service principal application ID` for the fencing agent | Required for highly available deployments that use a service principal for the fencing agent. |
@@ -491,7 +497,7 @@ Enter a **Service connection name**, for instance, use `Connection to MGMT subsc
491
497
492
498
## Permissions
493
499
494
-
Most of the pipelines add files to the Azure repos and therefore require pull permissions. On **Project Settings**, under the **Repositories** section, select the **Security** tab of the source code repository and assign Contribute permissions to the `Build Service`.
500
+
Most of the pipelines add files to the Azure Repos and therefore require pull permissions. On **Project Settings**, under the **Repositories** section, select the **Security** tab of the source code repository and assign Contribute permissions to the `Build Service`.
495
501
496
502
:::image type="content" source="./media/devops/automation-repo-permissions.png" alt-text="Screenshot that shows repository permissions.":::
497
503
@@ -557,7 +563,7 @@ Selecting the `deploy the web app infrastructure` parameter when you run the con
557
563
558
564
Wait for the deployment to finish. Select the **Extensions** tab and follow the instructions to finalize the configuration. Update the `reply-url` values for the app registration.
559
565
560
-
As a result of running the control plane pipeline, part of the web app URL that's needed is stored in a variable named `WEBAPP_URL_BASE` in your environment-specific variable group. At any time, you can update the URLs of the registered application web app by using the following command.
566
+
As a result of running the control plane pipeline, part of the web app URL that is needed is stored in a variable named `WEBAPP_URL_BASE` in your environment-specific variable group. At any time, you can update the URLs of the registered application web app by using the following command.
az ad app update --id $TF_VAR_app_registration_app_id --web-home-page-url https://${webapp_url_base}.azurewebsites.net --web-redirect-uris https://${webapp_url_base}.azurewebsites.net/ https://${webapp_url_base}.azurewebsites.net/.auth/login/aad/callback
574
580
```
575
581
---
576
-
You also need to grant reader permissions to the app service system-assigned managed identity. Go to the app service resource. On the left side, select **Identity**. On the **System assigned** tab, select **Azure role assignments** > **Add role assignment**. Select **Subscription** as the scope and **Reader** as the role. Then select **Save**. Without this step, the web app dropdown functionality won't work.
582
+
You also need to grant reader permissions to the app service system-assigned managed identity. Go to the app service resource. On the left side, select **Identity**. On the **System assigned** tab, select **Azure role assignments** > **Add role assignment**. Select **Subscription** as the scope and **Reader** as the role. Then select **Save**. Without this step, the web app dropdown functionality will not work.
577
583
578
584
You should now be able to visit the web app and use it to deploy SAP workload zones and SAP system infrastructure.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments