0
votes

I am attempting to follow the instructions in Franky's Notes, see the video at the bottom.

There is a step to use Azure Resource Group Deployment task.

I am getting a name collision. Also the error message may have a bug. Here is the error:

2019-08-11T23:52:02.0279313Z ##[error]The resource 'mydemoprojectname' already exists in location 'westus' in resource group 'mydemoprojectname'. A resource with the same name cannot be created in location 'centralus'. Please select a new resource name.
2019-08-11T23:52:02.0284558Z ##[error]Task failed while creating or updating the template deployment.

Issue 1: The error says to "Please select a new resource name." There is no field asking for a "resource name".

Issue 2: The logs don't represent the request. It is true that mydemoprojectname exists in location 'westus' in a resource group mydemoprojectname. I am not trying to create a resource in location centralus. I am trying to 'create or update' a resource in 'westus'.

Where do I set the "resource name" in the Azure Deployment:Create Or Update Resource Group action?

1
in the ARM template parameter file ?Thomas
@HughLin-MSFT, I ended up tearing down that pipeline and building it a different way. So I wasn't able to verify your answer. I'll upvote because it was useful information.Phillip Scott Givens

1 Answers

1
votes

Issue 1: The error says to "Please select a new resource name." There is no field asking for a "resource name".

For this issue, I think it is currently not support to rename resources.There is already a user voice about renaming resources . You can vote for this feature here : https://feedback.azure.com/forums/281804-azure-resource-manager/suggestions/19048513-rename-resources-in-azure-resource-manager-or-powe

 ##[error]The resource 'mydemoprojectname' already exists in location 'westus' in resource group 'mydemoprojectname'. A resource with the same name cannot be created in location 'centralus'. Please select a new resource name.

For this error, a similar issue has been resolved in this blog, please refer to it . You can also refer to this case with the similar error. Hope these help.