Resolve "User Sync Tool - Step 1 - read and write custom schema, and initiate scanning"
- Read customSchema
- Build list of uids that need to be scanned
- Limit and Cap changes
- Set 'scan' for these uids
- Also, clear customSchema for reactivated (unsuspended) uids
Added a --cache-dir
option (see README.md) so I could run multiple times and not have to wait for 70k+ users to be pulled from lookup and google every time. Bit of a cludge with decorator.
May be easier to review one commit at a time
Closes #40 (closed)
Merge request reports
Activity
added priority0 Highest teamIdentity workflowIn Progress labels
assigned to @rjg21
added 1 commit
- 5ad00119 - Bump version skipping 0.12 to avoid confusion
removed teamIdentity label
removed workflowIn Progress label
removed priority0 Highest label
requested review from @av603
- Resolved by Robin Goodall
- Resolved by Robin Goodall
- Resolved by Robin Goodall
- Resolved by Andrew Vella
- Resolved by Robin Goodall
- Resolved by Robin Goodall
added 1 commit
- 2d5a692e - Update README.md with testing against test tenancy
Added details to README.md on how to setup your local env to test against gdev.apps.cam.ac.uk tenancy.
Sync has already been run against this with
--really-do-this
when I was testing but with admin account users custom schema entries could be cleared/changes and then the tool rerun to see the changes reapplied.Tested locally and functions as expected. We may want to add all
.yaml
to.gitignore
and include anapi_gateway_credentials.json.example
. Also, why do we namegsuitesync.yaml
as opposed toconfiguration.yaml
whenconfiguration.yaml
is used in~/.gsuitesync/configuration.yaml
and/etc/gsuitesync/configuration.yaml
.