heat/heat/policies
Takashi Kajinami 185f28a3b4 Isolate project scope and system scope
This change updates the default policies implemented in Heat, to follow
the updated guideline[1] to implement SRBAC.

The main change is that system users are no longer allowed to perform
any operations about project-level resources like stacks, while project
admin(*1) is still allowed to perform operations about project-level
resources BEYOND project (like getting stacks for all projects by list
stacks API).

[1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#direction-change

This also adds the test cases to validate reader role which was almost
implemented in heat.

(*1)
If Keystone has an admin project defined, Heat checks an additional
requirement that request context is scoped by that admin project.

Change-Id: I943b3c1ce021cc05445b73fbc342b8386cf5bf6a
2023-06-28 18:38:59 +09:00
..
__init__.py Remove CloudWatch API 2018-01-28 09:11:17 +05:30
actions.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
base.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
build_info.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
cloudformation.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
events.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
resource.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
resource_types.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
service.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
software_configs.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
software_deployments.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00
stacks.py Isolate project scope and system scope 2023-06-28 18:38:59 +09:00