# navvy-cli **What it is.** An operator/developer command-line tool (spf13/cobra) that talks straight to [[postgres]] with the same env config as the API (`PG_CONNECTION` or `PG_*`, optional `.env`). Log level is forced to `error` (`initConfigWithErrorLevel`) and std log output is discarded. No Navvy permission checks apply — whoever has DB credentials can run anything. Build/run with `make build-navvy-cli` / `make navvy-cli`. Global flag `--json`. ## Commands | command | effect | writes | |---|---|---| | `user search ` / `details ` / `permissions ` | lookup; `permissions` lists resolved permission keys | — | | `user anonymize --confirm` | `runUserAnonymize`: every user whose role's `role_type != RoleSuperAdmin`: `email = ''`, given/family names replaced by uuid segments | [[user]] | | `client list` / `details ` | lookup | — | | `client anonymize --confirm` | `runClientAnonymize`: every client `name = id::text` | [[client]] | | `org list` / `details ` | lookup | — | | `org anonymize --confirm` | `runOrgAnonymize`: every org `name = id::text` | [[org]] | | `class search ` / `details ` | lookup | — | | `class anonymize --confirm` | `runClassAnonymize`: every class `title = id::text` | [[class]] | | `assessment`, `course`, `item` `search`/`details`; `subject`, `role`, `academic-session` `list`/`details`; `enrollment`, `testing-session`, `testing-assignment`, `testing-window` `details` | read-only lookups | — | | `lti platform list` / `register --name --issuer --client-id --auth-login-url [--auth-token-url] --jwks-url` / `activate` / `deactivate ` | `cmd/navvy-cli/lti.go`: LTI 1.3 platform registrations; register upserts on issuer+client_id and never changes `is_active` | [[lti-platform]] | | `lti deployment register --platform-id --deployment-id [--name] [--navvy-client-id]` / `activate` / `deactivate ` | upsert on platform+deployment_id; replaces `navvy_client_id` (pass it every time) | [[lti-deployment]] | | `lti tool-config` / `lti jwks` | print the login/redirect/JWKS URLs from `LTIBaseURL()` and the public JWKS for `LTI_TOOL_PRIVATE_KEY` ([[lti-config]]); no DB | — | | `anonymous-clone --source-client-id --district-rename-from "a,b" --confirm` | copy a client subset into a NEW anonymized client (below) | many (see rels) | The `lti` commands write immediately (no `--confirm`). Without `--confirm` every other writing command prints what it would do and exits 0. ## anonymous-clone (`runAnonymousClone`) Built for NAVVY-5887 (demo-account preparation). Single transaction on the write pool with a driver timeout of `--db-timeout` (default 30m). Steps, in order: 1. Verify the source [[client]] exists and each `--district-rename-from` name matches exactly one district (`cloneVerifySourceDistricts`); refuse if `--client-name` (default "Navvy+ State") already exists (client names are unique). 2. `cloneCopyClient` — `CREATE TEMP TABLE clone_tmp_client ... ON COMMIT DROP AS SELECT *`, rewrite id/name, clear `email`, `tenant_id`, `oneroster_client_id`, `oneroster_base_url`, `auto_sync_enabled = FALSE`, then `INSERT INTO clients SELECT *`. Every later step uses the same temp-table → remap → insert pattern with `clone_*_map` old→new id tables. 3. `cloneCreateStateOrg` (one new state [[org]], `--state-org-name`), `cloneCopyOrgs` (named districts and subtrees), `cloneCopyAcademicSessions`, `cloneCopyUsers` (+ `user_orgs`, `user_clients`, `user_demographics`; passwords and reset tokens blanked at copy; excludes roles Super Admin, Navvy Support, Navvy Team), `cloneCopyCourses`, `cloneCopyClasses`, `cloneCopyEnrollments`, `cloneCopyTestingData` (testing windows, assignments, sessions, responses, writing responses/scores; new random `adam_session_uuid` / `learnosity_session_uuid`), `cloneCopyMeasuresAndGoals` (measure scores, progress-monitoring goals), `cloneCopyConfiguration` (client/org configurations, client/org grade-subjects, org priority standards, org report categories, smart-set configs, fixed-form settings, bundle org display labels). 4. `cloneAnonymizeUsers` — chunks of 500 (`cloneUserUpdateChunkSize`) `UPDATE users ... FROM (VALUES ...)` setting fictional names from fixed name lists and blanking middle name, email, username, identifier, sourced_id, phone, sms. `cloneRenameCopiedOrgs` — districts get `--district-rename-to` names (default four fictional district names), other orgs generated names keeping Elementary/Middle/High/Academy. 5. Commit; prints the new client id. Shared reference data (roles, grades, subjects, assessments, measures, administration windows) is referenced, not copied. Demographic birth dates are truncated to year and birth locations cleared. The source client is never modified. ## Gotchas - `user anonymize` only blanks email and names; the anonymized DB still has usernames, identifiers, sourced ids and password hashes. Use on a copy only — these commands are destructive across the **whole** database. - `anonymous-clone` relies on `INSERT INTO SELECT * FROM clone_tmp_` — column order comes from the same table so schema changes are fine, but any new FK column pointing at a copied table must be added to the remap steps or it will point at the source client's rows. - Unit tests (`anonymous_clone_test.go`) only pin the name generators and `parseCloneDistrictRenames`; the SQL is untested. ## Related [[ops-tools]], [[orgs-service]], [[users-service]].