Skip to content

Update separation behavior if keycloak account doesnt exist #124

@spelkey-ucd

Description

@spelkey-ucd

Currently when separating, if an employee's keycloak account no longer exists (probably manually deleted), the separation command fails and the user is not removed from the local database. the cli has an option to bypass the keycloak removal step, but not the gui.

Instead, I think it would be better if we just continued with the separation process if there is no keycloak account.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions