Schemas used to author and validate Resource Manager Templates. These schemas power the intellisense and syntax completion in our ARM Tools VSCode extension, as well as the Export Template API

Перейти к файлу

Tian Ouyang 212fea4464 Merge pull request #341 from QuasarSE/patch-10 Fix template expression definition for if/and/or/not		2017-08-03 10:52:21 -07:00
schemas	Merge pull request #341 from QuasarSE/patch-10	2017-08-03 10:52:21 -07:00
tests	Write schema for disaster recovery configurations	2017-07-31 18:29:45 -07:00
tools	Corrected order of actual vs expected test errors	2017-07-25 20:52:30 -07:00
.gitignore	Add runSchemaTest.js fixes and tests	2016-06-21 13:38:10 -07:00
LICENSE	Add LICENSE file.	2015-05-06 17:15:10 -07:00
README.md	Updated deploymentTemplate.json files to reference new Microsoft.Sql/administrators	2017-03-28 15:54:03 -04:00

README.md

azure-resource-manager-schemas

This is the repo for template deployment schemas hosted at: https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json

Welcome to contribute to template deployment schemas, please send pull request to improve the schemas. We will review the pull request and publish the latest schemas to http://schema.management.azure.com/schemas

Hints:

When you add a new resource type in schema, please add it into schemas\2014-04-01-preview\deploymentTemplate.json and schemas\2015-01-01\deploymentTemplate.json
Please add or update tests for your change.
Please test your change with following two node.js scripts:
1. tools\validateJSON.js and ResourceMetaSchema.json:
  The script uses the ResourceMetaSchema.json to do some basic checks against the new/updated schema file.
  Usage:
  Node validateJSON.js <schema file path> ResourceMetaSchema.json <schema folder path> Sample:
  Node validateJSON.js ..\schemas\2015-08-01\Microsoft.Compute.json ResourceMetaSchema.json ..\schemas\
2. tools\runSchemaTests.js
  The script uses all test JSON files under tests folder to test against the schema files.
  Usage:
  Node runSchemaTests.js

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.