You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWX has historically made all resources a ForeignKey to organizations, and so all the work in #45 assumes this structure.
SIDE NOTE: development of the original AWX RBAC system is the reason that projects converted its many-to-many with organizations to ForeignKey, causing some duplication
We want to validate that permission inheritance can still work in an app that uses many-to-many between organizations and its resources.
The text was updated successfully, but these errors were encountered:
The core logic should "just work", that was the theory here, but I've realized that our real problem is the cache invalidation. We have signals connected to manage the case where an object's parent object changes... and this assumes ForeignKey. For a many-to-many between its object and its parent object(s), we would need to connect the m2m_changed signal and add somewhat substantial logic to cover the entire signature of that.
AWX has historically made all resources a ForeignKey to organizations, and so all the work in #45 assumes this structure.
SIDE NOTE: development of the original AWX RBAC system is the reason that projects converted its many-to-many with organizations to ForeignKey, causing some duplication
We want to validate that permission inheritance can still work in an app that uses many-to-many between organizations and its resources.
The text was updated successfully, but these errors were encountered: