FAQ | This is a LIVE service | Changelog

Skip to content
Snippets Groups Projects

Resolve "User Sync Tool - Step 1 - read and write custom schema, and initiate scanning"

Merged Robin Goodall requested to merge 40-custom-schema into master
  • 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

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Andrew Vella
  • Andrew Vella
  • Andrew Vella
  • Andrew Vella
  • Andrew Vella
  • Robin Goodall added 1 commit

    added 1 commit

    Compare with previous version

  • Robin Goodall added 1 commit

    added 1 commit

    Compare with previous version

  • Andrew Vella resolved all threads

    resolved all threads

  • Changes look ok, but I can't test the changes myself.

  • Robin Goodall added 1 commit

    added 1 commit

    • 2d5a692e - Update README.md with testing against test tenancy

    Compare with previous version

  • 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 an api_gateway_credentials.json.example. Also, why do we name gsuitesync.yaml as opposed to configuration.yaml when configuration.yaml is used in ~/.gsuitesync/configuration.yaml and /etc/gsuitesync/configuration.yaml.

    • gsuitesync.yaml is probably historic.

      Pushed commit that ignores all config files except examples (don't like having the wrong extensions on files so leaving them as ..-example.*). Also allows configuration.yaml as a local default.

    • I find it helpful to name examples configuration.yaml.example as they bypass the .gitignore *.yaml rule and terminal (tab) will auto-fill to configuration.yaml instead of configuration.

    • Renamed

    • Please register or sign in to reply
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading