[AIRAVATA-2787] GatewayGroups model for storing adminsGroupId, readOnlyAdminsGroupId and defaultGatewayUsersGroupId

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Epic Link: Group based Authorization
• Assignee: Marcus Christie
• Reporter: Marcus Christie
• Created: 10/May/18 13:49
• Updated: 23/May/18 20:49
• Resolved: 23/May/18 20:49

Description

Create a GatewayGroups thrift model and backend to store the ids of the "Admins", "Read Only Admins" and the default "Gateway Users" group. The "Admins" and "Read Only Admins" group will be used in the API server to automatically grant access to WRITE and READ to those groups, respectively, for newly created entities. The default "Gateway Users" group will be used by migrations (to keep track of previously migrated "Gateway Users" group and to share resources that are being migrated to group-based auth) and also to pre-populate the list of groups to share a new Group Resource Profile or Application Deployment with in UIs (but can be changed by the user).

The AiravataDataMigrator should use the presence of this model to determine if the gateway groups should be created or not.

TODO

• [x] add GatewayGroups model and entity to Registry
• [x] Create the GatewayGroups in the migration script by calling the Registry
• [x] create GatewayGroups initializer code to be run in a just-in-time fashion

Deferred

• add feature to sharing registry to mark certain groups as being undelete-able
• add feature to sharing registry to specify a certain group as one that should be added as admin of all groups created (so gateway admins can edit all groups created in a gateway)