bfc0692063
We don't know yet how useful the job failue tables will be, and maintaining multiple failure tables--one for every entity involved in CSP provisioning--is burdensome. This collapses them all into a single table that track the entity type (environment, portfolio, etc.) and the entity ID. That way we can construct queries when needed to find task results.
22 lines
913 B
Python
22 lines
913 B
Python
from .base import Base
|
|
from .application import Application
|
|
from .application_invitation import ApplicationInvitation
|
|
from .application_role import ApplicationRole, Status as ApplicationRoleStatus
|
|
from .attachment import Attachment
|
|
from .audit_event import AuditEvent
|
|
from .clin import CLIN, JEDICLINType
|
|
from .environment import Environment
|
|
from .environment_role import EnvironmentRole, CSPRole
|
|
from .job_failure import JobFailure
|
|
from .notification_recipient import NotificationRecipient
|
|
from .permissions import Permissions
|
|
from .permission_set import PermissionSet
|
|
from .portfolio import Portfolio
|
|
from .portfolio_state_machine import PortfolioStateMachine, FSMStates
|
|
from .portfolio_invitation import PortfolioInvitation
|
|
from .portfolio_role import PortfolioRole, Status as PortfolioRoleStatus
|
|
from .task_order import TaskOrder
|
|
from .user import User
|
|
|
|
from .mixins.invites import Status as InvitationStatus
|