Description

Product issue: https://github.com/3drepo/3D-Repo-Product-Team/issues/791

Since 5.16.0, we have deprecated the concept of a teamspace owner, thus, it no longer makes sense to allow the user to delete a user when they delete a teamspace. A teamspace is also associated with an FE account ID, which at the point of teamspace removal, we may not want to remove all the Frontegg accounts.

There are 3 things to do here:

1. Rename removeTeamspaceAndOwner script to removeTeamspaces:

• The script should no longer take the flag removeOwners.
• The script should take in an optional new flag, removeAssociatedAccount (defaults to true);
  • If true, it should delete the frontegg account (current behaviour)
  • If false, it should keep the frontegg account and ensure the frontegg users/roles are intact (this relates to Get teamspace member through IDP endpoint #5480 and v5 endpoint to Jobs and multiple jobs support #5339)
• At the end, the script should tell you how many users are removed and which ones were not found

1. Add a new script removeUsers, which will remove one or more specified users.

• The users can be in the form of an email or a username.
• At the end, the script should tell you how many users are removed and which ones were not found

Goals

• As a 3DR admin, I want to be able to remove the teamspace and specify whether I also want to remove the associated FE account
• As a 3DR admin, I want to be able to remove a batch of users by their usernames or emails
• As a 3DR admin, I want to know the results of my runs, which should tell me the list of teamspaces or users that we failed to remove because they did not exist.

Tasks

• update the removeTeamspaceAndOwner
  • update the test
• create a removeUsers script
  • create a test for removeUsers script