Pull request #8: Feature/multi thread bulk operationsMerge in BBCS/migrate_groups_to_cloud from feature/multi-thread_bulk_operations to master
* commit 'f9fee8bda15a8b9418ac72bb228cb1b7e44ae051':
adding project and repo permission settings to multi-threading
adding project based scanning and group creation to multi-threading
moving group membership scanning and repo scanning to multi-thread
set groups to backfil members rather than filling them preemptively as this could cause a serious performance/timing issue if there are a large number of unused groups within Bitbucket server
Addressed edge case where user's don't necessarily have email addresses.Only the users with an email are valid in cloud so simply skip any user without one to prevent errors
removing mention of personal access tokens as they no longer actually can be privileged high enough to allow instance admin, causing the script to fail with a 401 at times
Pull request #7: adding debug logging for early eventsMerge in BBCS/migrate_groups_to_cloud from feature/expanding-early-debug-logging to master
* commit '87345eac179e0d324c9d84f1290649bece629ea8':
adding debug logging for early events
Pull request #6: added same check but for global permissions level.Merge in BBCS/migrate_groups_to_cloud from bugfix/handling-non-active-groups to master
* commit '52e34ffed04b3be41aa70467815f587803b9dca3':
added same check but for global permissions level. Also cleaned up unused imports while I was at it
Pull request #5: adding try/except to to skip the scenario where a group found at the project or repo level (in server) may contain a permission but isn't a group in use.Merge in BBCS/migrate_groups_to_cloud from bugfix/handling-non-active-groups to master
* commit 'e60ea29e9603ede303da8b6b48601b7b0c0e9701':
adding try/except to to skip the scenario where a group found at the project or repo level (in server) may contain a permission but isn't a group in use. This is sometimes seen with remote directories
adding try/except to to skip the scenario where a group found at the project or repo level (in server) may contain a permission but isn't a group in use.This is sometimes seen with remote directories
Pull request #4: Feature/add project permissionsMerge in BBCS/migrate_groups_to_cloud from feature/add-project-permissions to master
* commit 'a6f799b81f20907c8cf3865b84e3541d7576d8ff':
adding timer
updating readme
revamped to use project permissions. Heavy overhaul of the permission flattening, added functions for new API endpoints, and broke the dataclass objects to it's own file and expanded on the objects available
moved logic f...
revamped to use project permissions.Heavy overhaul of the permission flattening, added functions for new API endpoints, and broke the dataclass objects to it's own file and expanded on the objects available
Pull request #3: Feature/users and groupsMerge in BBCS/migrate_groups_to_cloud from feature/users-and-groups to master
* commit '5d04fd724491671bd13ca1d5ff5b4c89f24fb85a': (21 commits)
Enabling user level permission migration if 'export-users.csv' file is present and readable
fixing type hinting
moved the .get_aid() out of the post_init as we don't need it to run when the user obj is first created, but rather when we're ready t...
Pull request #2: fixing type hintingMerge in BBCS/migrate_groups_to_cloud from bugfix/type-fixing to feature/users-and-groups
* commit '67816e42e3b0691f0c8c3e5d4c0d96e3f9313bf4':
fixing type hinting
moved the .get_aid() out of the post_init as we don't need it to run when the user obj is first created, but rather when we're ready to use the aid, if at all | also updated the logic to update self.aid rather than return anything
modified max_user_permission to leverage Permission enum | updated mirror_repo_user_permission to now utilize the 'name' of the enum rather than the enum obj itself
broke mirror function into logical group and user sub functions and added permission flattening for user level | Incomplete until a mechanism for comparing user permission, to find greatest permission level, is added
Michael Walker