Validating software design
Initial data is what drives the main usability of a formset.
I have an ARM Template that I need to validate and to do that, have created a build definition on Visual Studio Team Services, I’ll take you through the steps involved in validating the ARM template. JSONLint is a npm package we can use to validate the json syntax.In this article, I’ll talk about an approach that we can use to validate our Azure Resource Manager templates. And these JSON files should be validated for syntactic correctness and validated against the schema used in the ARM templates and validated against the Resource Group on top of which the ARM template is deployed on.We can use the Visual Studio Team Services build pipeline to do this validation.They should be versioned, source controlled and also tested and validated.By doing this, you can be confident that your Infrastructure code is up to the highest quality and also will not give you problems at deployment time.The following output was given when validating the ARM template JSON syntax with JSONLInt As you can clearly see, the extra information on the JSON lint task makes it easy to pin-point the syntax issue with the json file.
The screenshot below shows the exact line where the error is.
Then change the command to custom and add to the Script section of the task.
In the advanced section you can select the Working Directory where the Template JSON file resides.
And for me the amount of details I see in the output helps me a lot to pin-point the issue and fix it.
Look at the example below, The following output was given when validating the ARM template JSON syntax with the Azure Resource Group Deployment task.
If you use an is a list whose entries correspond to the forms in the formset.