Deployment script is not able to create multiple environments with the same name

Describe the bug

If you’d like to deploy two resource groups with the script using the same name, but different environments, the second deployment would fail with and error.

This happens because both runs of the script would try to create a Microsoft.BotService/botServices resource with the same name, which of course would fail for the second try.

To Reproduce

Example

1st deployment

node .\provisionComposer.js `
   --subscriptionId ***** `
   --appId ***** `
   --appPassword ***** `
   --location westeurope `
   --name my-composer `
   --environment dev

2nd deployment

node .\provisionComposer.js `
   --subscriptionId ***** `
   --appId ***** `
   --appPassword ***** `
   --location westeurope `
   --name my-composer `
   --environment test

(Note the only difference is the --environment parameter: dev first, test second.)

The error you would get is:

×
{
  "error": {
    "code": "InvalidBotData",
    "message": "Bot is not valid. Errors: The bot name is already registered to another bot application..  See https://aka.ms/bot-requirements for detailed requirements."
  }
}
** Provision failed **

Expected behavior

The second run should succeed. The resource names in the two environments shouldn’t clash.

[peterbozso]

@EricDahlvang Yes, feedback is totally right, I only lack the free time to actually implement the changes.

[tdurnford]

@pavolum @GeoffCoxMSFT Any updates on this?