From e680d1bbf04e41fbb7cb24307013301dc8c8293e Mon Sep 17 00:00:00 2001 From: SeanTarrant <139977599+SeanTarrant@users.noreply.github.com> Date: Fri, 10 Jan 2025 10:25:14 +0000 Subject: [PATCH 1/2] Update azure-devops.md Had an issue with referencing, umbracoCloudApiKey reference in the yaml files needed to be amended to UMBRACOCLOUDAPIKEY to reference the newly created variable. This was in Azure DevOps pipeline --- .../umbraco-cicd/samplecicdpipeline/azure-devops.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md index deb107d6e04..bbc9301e5b6 100644 --- a/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md +++ b/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md @@ -165,7 +165,11 @@ It is recommended to handle the `API Key` as a secret. This can be done by ticki {% hint style="info" %} 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`. -{% endhint %} +{% endhint %} + +{% hint style="info" %} +Check the references to the variables in the yaml files match the variable syntaxes in the created variable. e.g. umbracoCloudApiKey = UMBRACOCLOUDAPIKEY +{% endhint %} 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. From c2e6ecf1f8e5a8a2c5ecc99361dcf0b80b4653c2 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Fri, 7 Mar 2025 12:43:12 +0100 Subject: [PATCH 2/2] Update azure-devops.md --- .../umbraco-cicd/samplecicdpipeline/azure-devops.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md index bbc9301e5b6..3e9ab961687 100644 --- a/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md +++ b/umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/azure-devops.md @@ -164,11 +164,9 @@ It is recommended to handle the `API Key` as a secret. This can be done by ticki {% endhint %} {% hint style="info" %} -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`. -{% endhint %} +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`. -{% hint style="info" %} -Check the references to the variables in the yaml files match the variable syntaxes in the created variable. e.g. umbracoCloudApiKey = UMBRACOCLOUDAPIKEY +Check the references to the variables in the yaml files match the variable syntaxes in the created variable. Example: `umbracoCloudApiKey` = `UMBRACOCLOUDAPIKEY`. {% endhint %} 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.