Add note when blocking user accounts during PS user migration
Overview
Currently, when PS migrates user accounts we make sure to match their state
between source and destination instance (GitLab, BitBucket or GitHub).
When migrating customer user accounts to SaaS we often bring the blocked ones over as well to preserve their user contribution mappings.
To do this we either create the user account and immediately block
it afterwards or block
an existing one.
There are sometimes cases where already existing user accounts on both instances are blocked
on source, but active
on destination. In these cases we want to align their state
and go through the process of manually blocking them on destination.
To make it clear for destination instance admins and/or GitLab Support, we should add a note indicating the user account blocking was done by GitLab PS.
This note should be added as part of the user metadata when editing (blocking) the account, either automated via Congregate or manually.
Via API:
Attribute | Required | Description |
---|---|---|
note | No | Administration notes for this user |
Manually (Admin -> Users -> User page -> Edit -> Admin notes (Note)):
Tasks
-
Update docs if needed (workflow, runbooks, README, migration metrics, etc.)
Acceptance Criteria
-
Existing UTs pass locally -
100% code coverage on new code
@gitlab-org/professional-services-automation/tools/migration