enum values in policy_templates.json have a
- 'schema': {'enum': [ 0, 1, 2, .. ], .. }
- 'items': [
    {
     'name': '<NAME>',
     'value': 0,
     'caption': '''<CAPTION>''',
    },
    ...
   ]

Introduce a presubmit to check that these match


 

policy_templates.json contains 'schema' fields describing the JSON schema of the policy value. Introduce a presubmit to validate these (currently we don't do that at all, or do it manually with online JSON validation tools).
TBD: Which JSON Schema draft version is to be used.

Additionally, enum values in policy_templates.json have a
- 'schema': {'enum': [ 0, 1, 2, .. ], .. }
- 'items': [
    {
     'name': '<NAME>',
     'value': 0,
     'caption': '''<CAPTION>''',
    },
    ...
   ]
Introduce a second PRESUBMIT to check that these match.

 

Enum values in policy_templates.json have a
- 'schema': {'enum': [ 0, 1, 2, .. ], .. }
- 'items': [
    {
     'name': '<NAME>',
     'value': 0,
     'caption': '''<CAPTION>''',
    },
    ...
   ]
Introduce a second PRESUBMIT to check that these match.