Rick Bartra a8fd8731d2 Add policy granularity to the Flavors API ... The same policy rule (os_compute_api:os-flavor-manage) is being used for the create and delete actions of the flavors REST API. It is thus impossible to provide different RBAC for the create and delete actions based on roles. To address this, changes are made to have separate policy rules for each action. Most other places in nova (and OpenStack in general) have separate policy rules for each action. This affords the ultimate flexibility to deployers, who can obviously use the same rule if that is what they want. To address backwards compatibility, the new rules added to the flavor_manage.py policy file, default to the existing rule (os_compute_api:os-flavor-manage). That way across upgrades this should ensure if an existing admin has customised the rule, it keeps working, but folks that know about the new setting can override the default rule. In addtion, a verify_deprecated_policy method is added to see if the old policy action is being configured instead of the new actions. Closes-Bug: #1675147 Co-Authored-By: Felipe Monteiro <felipe.monteiro@att.com> Change-Id: Ic67b52ebac3a47e9fb7e3c0d6c3ce8a6bc539e11		2017-07-19 15:56:47 -04:00
..
openstack	Add policy granularity to the Flavors API	2017-07-19 15:56:47 -04:00
__init__.py	move all tests to nova/tests/unit	2014-11-12 15:31:08 -05:00
test_auth.py	conf: Move api options to a group	2016-11-25 16:32:31 -06:00
test_compute_req_id.py	Migrate to oslo request_id middleware - mv 2.46	2017-05-27 10:11:44 +00:00
test_wsgi.py	Capture stdout in for test_wsgi:test_debug	2016-09-26 06:45:08 -04:00