Update ExecutionEnvironment model so object-level roles work with DAB RBAC system#15289
Conversation
|
|
ee4b68c to
c6f629a
Compare
Test got me the intended failuremoving onto fixing it... |
|
Migration tests are now giving: Which is what I wanted. So removing the view permission for the EE model is now done. |
c851341 to
744ddc8
Compare
|
Newer test failures such as this: Are reflecting that the dependent DAB change needs to be merged first. |
744ddc8 to
a99d5f0
Compare
a99d5f0 to
507ce90
Compare
507ce90 to
c1e9349
Compare
|
Schema change is intended. That's the entire point. |
… RBAC system (ansible#15289) * Add initial test for deletion of stale permission * Delete existing EE view permission * Hypothetically complete update of EE model permissions setup * Tests passing locally * Issue with user_capabilities was a test bug, fixed
… RBAC system (ansible#15289) * Add initial test for deletion of stale permission * Delete existing EE view permission * Hypothetically complete update of EE model permissions setup * Tests passing locally * Issue with user_capabilities was a test bug, fixed
|
@AlanCoding @chrismeyersfsu does this PR disable the option to give the role "Execution Environment Admin" to an Organization? |
|
No, it shouldn't. This was trying really hard to not un-do the existing permission setup. There are special rules for EEs that are not assigned to an org. When assigned to an org, members of the org can see it, and the messy implication of that (with this change) is that membership to the org is required to get the organization EE role. |
SUMMARY
Depends on ansible/django-ansible-base#490
RECAP:
user_capabilitieswas giving the wrong answer... it wasn't. My fixture was wrong, and the API was right. ✔️AAP-25268
ISSUE TYPE
COMPONENT NAME