openstack/tacker
Code Issues Proposed changes
46da7f8f59
tacker/doc/source/configuration/index.rst
Ghanshyam Mann 40a48bde6b [goal] Deprecate the JSON formatted policy file 
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:

1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.

2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.

Also replace policy.json to policy.yaml ref from doc and tests.

[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html

Change-Id: I6fc6f7d95e4efde6ea3bd0f1e4134aa54ce3889a
2021-01-22 04:18:31 +00:00

1.9 KiB
Raw Blame History

Tacker Configuration Guide

The static configuration for tacker lives in three main files: api-paste.ini, tacker.conf and policy.yaml. These are described below. For a bigger picture view on configuring tacker to solve specific problems.

Configuration

  • API Paste ini <api-paste.ini>: A complete reference of api-paste.ini available in the api-paste.ini file.
  • Config Reference <config>: A complete reference of all configuration options available in the tacker.conf file.
  • Sample Config File <sample_config>: A sample config file with inline documentation.

Policy

Tacker, like most OpenStack projects, uses a policy language to restrict permissions on REST API actions.

  • Policy Reference <policy>: A complete reference of all policy points in tacker and what they impact.
  • Sample Policy File <sample_policy>: A sample tacker policy file with inline documentation.

api-paste.ini policy sample_policy config sample_config