Open sunnybhambhani opened 1 year ago
If a full copy of ARM is required, the sample can be found on below URL, since that too is failing and there as well we have vmSize as a parameter:
https://learn.microsoft.com/en-us/azure/aks/learn/quick-kubernetes-deploy-rm-template?tabs=azure-cli Section: Review the template
Thanks, Sunny
It appears we are not allowing the VMSize parameter to be anything other than VMSize:
I believe we should adjust this. But how? Should we require it to be named anything particular? If not, what heuristic do we use to determine if the top-level parameter is a VMSize?
It should have no naming constraints - the parameter can be named anything. We just need to verify that any resource property named vmSize
has a property value that is a parameter (or a variable that references a parameter)... Keeping in mind that the param/var could be an object.
@sunnybhambhani
This should be fixed by recent changes to the VMSize tests. Please confirm when you get the chance.
Hi Team, Hope you are doing good.
Since the upgrade of ARM-TTK our template validation is failing. If I remember it correctly with v0.15 I never encountered this issue.
Also, I believe the reason is wrong or misleading since we already are using the practices which are shared over the documentation.
Ref: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-test-cases Section: VM size uses parameter
Error:
We are already using vmSize as a parameter, please find below snippets from our respective arm templates:
createUiDefinition.json [Ref: https://learn.microsoft.com/en-us/azure/azure-resource-manager/managed-applications/microsoft-compute-sizeselector]
mainTemplate's parameters:
mainTemplate's resources (this is a part of AKS agent pool):
Could you please suggest OR correct me if I am doing something wrong?
Thank you, Sunny