-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add organization and team models #2094
Add organization and team models #2094
Conversation
0bad411
to
5e857ff
Compare
5e857ff
to
72bbf86
Compare
72bbf86
to
2791177
Compare
8767151
to
691f7aa
Compare
* Add new `Oranization` and `Team` models, that implement respective abstract models from DAB. * Add related database migrations and data migration, that creates a new default model. * Implement custom manager for the `Organization` model that retrieves the default organization. * Team model has a one-to-one relationship with the standard Group model. * When new Team record is created, a related Group model is automatically created as well. No-Issue
And drop group prefix for the default organization. No-Issue
691f7aa
to
cd5d588
Compare
Organization & team admins & members are implemented as a role in both DAB RBAC and current AWX. Yes, they are implemented as relationships in Gateway. It will make our lives much easier if they never need to co-exist. I added a sub-feature of DAB RBAC to cope with that co-existence, but I had plans to remove it - ansible/django-ansible-base#159 Looking at this, it seems that ansible/django-ansible-base#159 may need to be closed, as with the way this is going, org admins may co-exist as both a relationship and a role at some point. |
Oranization
andTeam
models, that implement respective abstract models from DAB.Organization
model that retrieves the default organization.No-Issue