tree: 0725efef0901791b6ce373944456f4e926cc9356 [path history] [tgz]
  1. policy_definitions/
  2. common_schemas.yaml
  3. legacy_device_policy_proto_map.yaml
  4. manual_device_policy_proto_map.yaml
  5. messages.yaml
  6. OWNERS
  7. policies.yaml
  8. README.md
  9. risk_tag_definitions.yaml
components/policy/resources/templates/README.md

Chromium policy definitions

This directory houses the data templates used Chromium browser and OS policies.

Policy definitions

Policies are defined under policy_definitions. Every subdirectory represents a policy group.

  • To create a new policy group, create a new directory named after the new group under policy_definitions.
  • To create a new policy, create a yaml file under the appropriate group. The name of the file will be the name of the policy. For more information on policy creation, visit add_new_policy.md.
  • To remove a policy, more information can be found at add_new_policy.md.
    • If the policy was released, mark it as deprecated, add an end milestone in the supported_on field of that policy. You may only remove support for a policy after the last milestone of support has passed.
    • If the policy was not released, delete the yaml file of that policy, and replace its name in policies.yaml by an empty string.
    • Removing policies also requires deleting all references to that policy in the code.

Policy templates.json

Policies used to be defined in policy_templates.json. This is a link to the last version of the file.

This file is still used in some other pipelines but it is now generated by policy_templates.py where needed. This is a link to the generated policy_templates.json.