tacker/tacker/policies
Ghanshyam Mann ba24a89998 Add new default roles in vnf-package API policies
This adds new defaults roles in vnf-package API policies.

Backward compatibility:
- Old Rules and Defaults will keep working as it is because they
  are added as deprecated rules and not removed. They are enabled
  by default. This means existing deployement will continue working
  in same way till deprecated rules are there and enabled by default.
- Legacy/current admin stays same and no change in their access permission
- Deprecation warning is added for old defaults so that operators will
  know that new defaults are available to opt-in.

New defaults(project personas):
- Add new defaults but they are disabled by defaults and operators can adopt them
  by enabling the oslo.policy config option. Basically add below in tacker.conf

  [oslo_policy]
  enforce_new_defaults=True

- All GET (read only) APIs are default to PROJECT_READER_OR_ADMIN
- Rest other APIs (write operations) are default to PROJECT_MEMBER_OR_ADMIN

Adding tests also to check permissions of new defaults.

Partial implement blueprint implement-project-personas

Change-Id: Ic7f5a9cd5aa10d93dfa491e5e60befb1f4bf2fcd
2024-03-13 18:17:04 +00:00
..
__init__.py Add support cnf auto heal and scale 2022-09-15 18:59:28 +00:00
base.py Add new default base rules and mapping in policy base class 2024-03-13 18:16:46 +00:00
vnf_lcm.py Add new default roles in vnf-lcm API policies 2024-03-13 18:16:55 +00:00
vnf_package.py Add new default roles in vnf-package API policies 2024-03-13 18:17:04 +00:00