This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 95%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
Running the arm-ttk against a CreateUIDefinition.json and getting the following:-
Test-AzTemplate -TemplatePath /d/home/dug/timjam/azure/arm/testingpassed -Test Outputs-Must-Be-Present-In-Template-Parameters
Validating testingpassed\createUiDefinition.json
CreateUIDefinition
[-] Outputs Must Be Present In Template Parameters (22 ms)
A parameter cannot be found that matches parameter name 'ErrorId'.
A parameter cannot be found that matches parameter name 'ErrorId'.
A parameter cannot be found that matches parameter name 'ErrorId'.
I don't have a parameter ErrorId in either my CreateUiDefinition or MainTemplate and I don't believe it is mandatory, so I am unsure why this is reported as an error.
Hi @Tim James ,
If you don't have a parameter ErrorId in either CreateUiDefinition or MainTemplate then it's a weird error.
I have tried to reproduce the issue in various ways (i.e., by giving wrong syntaxes like adding extra comma, removing double quotes, trying with linked templates related mainTemplate, etc.) but was not successful to reproduce the issue.
I hope you are trying with the latest 0.3 version arm-ttk. If not, please use the latest version.
Are you getting same or similar error if you run some other tests in the same template path as well?
Can you provide your MainTemplate and CreateUiDefinition for me to try to reproduce the issue in my environment?
Thanks for checking into this for me. I am using 0.3.
I will attach the two json files here to see if you get the same. (Removed now to protect IP)
Hi @Tim James ,
The 3 errors are because of adding below 3 highlighted lines under the outputs property. If I remove those 3 lines then it doesn't throw the errors.
"startIP": "[steps('clusterDetails1').startIP]",
"nodeCount": "[steps('clusterDetails2').nodeSection.nodeCount]",
"storagePoolSize": "[steps('clusterDetails2').storageSection.storagePoolSize]",
The 3 parameters startIP, nodeCount and storagePoolSize are int type so that might be the reason but I am still trying to figure out why outputs property doesn't allow to map these int parameters related elements from steps property. Will provide a comment as soon as I have an update.
Good detective work, thank you.
Yes, I see they are the only parameters with int type. They obviously do exist in the mainTemplate as parameters, so presumably the testing toolkit is not handling this situation correctly and at some point the parameter name(s) are being translated to ErrorId in the toolkit when it correlates outputs from the createUiDefinition with the parameters of the mainTemplate. The combination of UiDef and main template is fully functional with respect to these parameters.
Hi @Tim James ,
I have worked with internal team, the error is fixed and is more meaningful now. Please check below screenshot for illustration. Also, please refer this related github issue for more information. So overall in your case, the CUID is not returning the correct JSON type for the parameter value. In CUID those properties return a "string" type and mainTemplate.json expects an "int". The types must match but thats not happening and hence the error.
Thanks for following up. The error in the ttk makes more sense now.
I don't see how we can ensure the outputs of the CUID are of type int, though. How can that be specified in the CUID? The alternative is to change them to being strings and convert in the mainTemplate but I would prefer not to do that.
Looking at the pull request, the test case for failing a mismatch from int to boolean uses this output value
"outputs": {
"testBoolean": "[int('1')]"
}
so I will experiment with applying the int() function to the outputs.
OK, wrapping each of the outputs with int() works fine, and now the template test toolkit is all green as well - thanks for your help!
Hi @Tim James ,
I was about to tell the same! Glad to hear that from you! :)
Hi @Tim James ,
<<Adding the summary as answer for the benefit of broader community members who might be looking for similar information>>
Summary:
Firstly, it was a bug to have the error description as "A parameter cannot be found that matches parameter name 'ErrorId'." which was fixed here to give more meaningful error description as "output <PARAMETER> does not return the expected type <TYPE>"
Secondly, to ensure the outputs of the CUID are of type int in this case, wrapping each of the outputs with int() worked fine, and now the template test toolkit is all green as well. :)