openstack
/
openstack
Code Issues Proposed changes

Update git submodules 

* Update tacker from branch 'master'
  to b4d82e774cd51d0e05a0191506251951ea549901
  - Merge "Introduce project scope_types in VNF LCM policy"
  - Introduce project scope_types in VNF LCM policy
    
    oslo.policy introduced the scope_type feature which can
    control the access level at system-level and project-level.
     - https://docs.openstack.org/oslo.policy/latest/user/usage.html#setting-scope
    
    As per the SRBAC design, OpenStack does not support system scope so
    we need to make scope type of each policy rule to project.
    
    - https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#phase-1
    
    The policy with 'project' scope means user with 'project-scoped'
    token have permission to access which is nothing but the current
    case so no change in permission level. By adding the scope_type
    to project explicitly gives benefit of better error message. For
    example, if any user with system scope token try to access tacker
    APIs then oslo policy will fail early (instead of failing in lower
    layer at DB or VIM level) and give clear error message of invalid
    scope.
    
    This commit adds project scope in VNF LCM policies and its tests
    also.
    
    Partial implement blueprint implement-project-personas
    
    Change-Id: Iead7f82b8c22c0c67981f5a7ae3a86016ee64734
This commit is contained in:
Zuul 2024-03-15 09:39:25 +00:00 committed by Gerrit Code Review
parent e4062bb6bd
commit e23efe0589
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tacker

@ -1 +1 @@
Subproject commit 9c797d08e4b323291f36fd58b210a150216715b2
Subproject commit b4d82e774cd51d0e05a0191506251951ea549901