migrating custom groups

[ArtificialOwl]

migrate owncloud's Custom Groups to Teams

for each Custom Group (CG):

• creating Team using CG oldest Admin as Owner
• adding CG members to generated Team
• leveling other Admins from CG as Admin in generated Team,
• converting shares to CG to generated Team,
• fixing children shares

original data

+--------------+---------------------+------+-----+---------+----------------+
| Field        | Type                | Null | Key | Default | Extra          |
+--------------+---------------------+------+-----+---------+----------------+
| group_id     | bigint(20) unsigned | NO   | PRI | NULL    | auto_increment |
| uri          | varchar(255)        | NO   | UNI | NULL    |                |
| display_name | varchar(64)         | NO   |     | NULL    |                |
+--------------+---------------------+------+-----+---------+----------------+

+----------+---------------------+------+-----+---------+-------+
| Field    | Type                | Null | Key | Default | Extra |
+----------+---------------------+------+-----+---------+-------+
| group_id | bigint(20) unsigned | NO   | PRI | NULL    |       |
| user_id  | varchar(64)         | NO   | PRI | NULL    |       |
| role     | int(11)             | NO   |     | 0       |       |
+----------+---------------------+------+-----+---------+-------+

[mejo-]

I have no idea about owncloud and their custom groups functionality, but apart from one comment i didn't spot anything obvious ☺️

[mejo-]

Code changes look sensible now. Thanks for adding additional context to the PR description. I didn't test this, bug I guess you did 😉

[ArtificialOwl]

/backport to stable30

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/1685/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1bbc440e ee7d2d67 49e748da

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/1685/stable30

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.