Skip to content

Commit c2e6ecf

Browse files
authored
Update azure-devops.md
1 parent e680d1b commit c2e6ecf

File tree

1 file changed

+2
-4
lines changed
  • umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline

1 file changed

+2
-4
lines changed

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -164,11 +164,9 @@ It is recommended to handle the `API Key` as a secret. This can be done by ticki
164164
{% endhint %}
165165

166166
{% hint style="info" %}
167-
You can customize the names for the variables as you like, however you then need to rename the affected variables in `azure-release-pipeline.yaml`.
168-
{% endhint %}
167+
You can customize the names for the variables as you like, however, you then need to rename the affected variables in `azure-release-pipeline.yaml`.
169168

170-
{% hint style="info" %}
171-
Check the references to the variables in the yaml files match the variable syntaxes in the created variable. e.g. umbracoCloudApiKey = UMBRACOCLOUDAPIKEY
169+
Check the references to the variables in the yaml files match the variable syntaxes in the created variable. Example: `umbracoCloudApiKey` = `UMBRACOCLOUDAPIKEY`.
172170
{% endhint %}
173171

174172
When you click on "Save and Run" your first deployment will be triggered. Which means that Azure DevOps is set up with all the needed information to be able to deploy your Cloud project back to Umbraco Cloud.

0 commit comments

Comments
 (0)