Virtual assistant
TypeScript
When running the deployment of the needed resources using the ARM template an error message pops up with the message 'The template deployment 'deployment_dry_run' is not valid according to the validation procedure'.
Following this guide.
Having the resource group completed according to the template.
Error message:
{'additional_properties': {}, 'code': 'InvalidTemplateDeployment', 'message': "The template deployment 'deployment_dry_run' is not valid according to the validation procedure. The tracking id is '5c12b860-c6dc-450e-b461-98ea5de98816'. See inner errors for details.", 'target': None, 'details': [<azure.mgmt.resource.resources.v2019_07_01.models._models.ErrorResponse object at 0x0529AA10>], 'additional_info': None}
deploy_log.txt
ERROR: Deployment '03102020103532' could not be found.
Assigning to support.
Hi @19George97
Can you please ensure that you have the most recent version of AZ CLI?
Also, you are creating the VA from the yeoman package, correct? Or are you using the sample from the repo?
If using yeoman, can you please confirm the version of the package:
npm -v generator-botbuilder-assistant
Hi @19George97
Can you please ensure that you have the most recent version of AZ CLI?
Also, you are creating the VA from the yeoman package, correct? Or are you using the sample from the repo?
If using yeoman, can you please confirm the version of the package:
npm -v generator-botbuilder-assistant
@dmvtech
I am using the lastest version of the AZ CLI indeed: 2.2.0
I am creating the virtual assistant following the typescript tutorial steps here.
using version 6.13.4 of the generator (using yeoman indeed)
Also relevant to mention: When using the C# tutorial, the provisioning of the resources through the deploy script (ARM templates) works fine.
Thanks. Seeing if i can reproduce.
Just touching base. I _am_ able to reproduce this. Investigating.
Hi @19George97
So, this is an issue with using the newer version of the CLI (2.2.0). There were commands that were deprecated and we are working to get changes to the script in a release coming soon.
For now, the options you can use are:
1) use an older cli version (2.0.n). You might have to use the C# version of the deployment scripts/templates. See here.
2) provision the resources 'by hand' (either with cli or UI). See here.
Thank you for bringing this to our attention.
Most helpful comment
Just touching base. I _am_ able to reproduce this. Investigating.