8ab5ec6b4f
RBAC enforcement in manila happens in stages: 1) Does user have access to the API 2) Does user have access to the resource 3) Is user permitted to perform the API action on the resource If (1) fails, user gets a HTTP 403, if (2) fails, they get a HTTP 404; if (3) fails, they get a HTTP 403. More often than not, (2) prevents "existence" detection of resources that don't belong to the user; except in case of "public" resources (e.g.: shares can be "public"). In some share API methods, policy checks for (1) are happening after a bunch of processing. This leads to some inconsistency. Fix these occurrences to ensure a consistent user experience. Change-Id: I5b1f1ce517efed000f17b1e0901e183a1913ba9f Related-Bug: #2004230 Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com> (cherry picked from commit190876809f) (cherry picked from commit318140e250) (cherry picked from commit8edaa3254c) (cherry picked from commitf878e15bca)
Team and repository tags
MANILA
You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.
- Wiki: https://wiki.openstack.org/wiki/Manila
- Developer docs: https://docs.openstack.org/manila/latest/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://opendev.org/openstack/manila
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/manila
Python client
https://opendev.org/openstack/python-manilaclient
- Documentation for the project can be found at:
https://docs.openstack.org/manila/latest/
- Release notes for the project can be found at:
https://docs.openstack.org/releasenotes/manila/
- Source for the project:
https://opendev.org/openstack/manila
- Bugs:
https://bugs.launchpad.net/manila
- Blueprints:
https://blueprints.launchpad.net/manila
- Design specifications are tracked at: