New invitation backend for portfolio invitations.
Portfolio invitations do not associate a user entity until the invitation has been accepted. User info, including DOD ID, is held on the invitation itself. When a user accepts and invitation, their user entry is associated with the corresponding `portfolio_role` entry. The same change will be applied to `application_role` and application invitations. For now, small changes have been made to application-related methods so that that flow works as-is.
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
"""add user data fields to invitations
|
||||
|
||||
Revision ID: 8467440c4ae6
|
||||
Revises: d2390c547dca
|
||||
Revises: 24700d113ea9
|
||||
Create Date: 2019-05-31 12:40:10.457529
|
||||
|
||||
"""
|
||||
@@ -11,7 +11,7 @@ from sqlalchemy.dialects import postgresql
|
||||
|
||||
# revision identifiers, used by Alembic.
|
||||
revision = '8467440c4ae6'
|
||||
down_revision = 'd2390c547dca'
|
||||
down_revision = '24700d113ea9'
|
||||
branch_labels = None
|
||||
depends_on = None
|
||||
|
||||
|
Reference in New Issue
Block a user