Atlas project maintenance

GSuiteAPI

Shell-based Google Workspace automation repository containing legacy classroom, guardian, group, and reporting scripts built around shared GAM and SQL helper libraries.

Internal-only entry. Do not publish externally without review.

Type: Component
Lifecycle: Deprecated
Last touched: 2026-03-26
Visibility: Internal

Purpose

Document and retain the legacy Google automation script set while clarifying migration and overlap with newer repositories.

Current state

Implementation evidence is substantial, but Atlas now treats this as maintenance/deprecated in favor of clearer successor tooling (for example `aether` and focused Rust utilities). Cross-repo evidence strengthens that boundary: `aether/docs/cron-example.txt` schedules `Push-AeriesToGoogleClassroom.sh` and other similarly named script families while this repo contains matching legacy script names, suggesting successor runtime has shifted to Linux-hosted `aether` paths (primary host role `sal-01.bousd.us`) for at least part of the workload. Current `saw-01` Task Scheduler artifact evidence does not show tasks invoking `GSuiteAPI` paths, so active production execution from this repo is not currently evidenced.

Next step

Build a script-level migration map (`GSuiteAPI` -> `aether` or Rust successor) and mark each workflow as active, fallback-only, or retired, including explicit host/scheduler assignment (`sal-01` cron, `saw-01` Task Scheduler, or manual).

Interfaces

Inputs

Google Admin domain data
SQL-backed exports
Config under config/

Outputs

Google Workspace updates
CSV/report files
Script logs

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Artifacts

Root Push/Get shell scripts
lib/*.sh helpers
sql/*.sql queries

Operational notes

Constraints and scars

Large script surface with mixed maturity.
Workflow ownership can be unclear across overlapping repos.

Reliability posture

Behavior varies per script. Shared libraries provide some consistency, but safeguards and run controls are not centralized.

Observability

Script stdout/stderr
Local log artifacts

Security and privacy

Repository contains privileged automation paths. Keep credentials outside source control and treat outputs as restricted where they include directory or student/staff data.

Dependencies

Upstream

Google Workspace APIs
SQL data sources
GAM runtime

Downstream

Classroom/group/guardian operational workflows

Ownership

Owners

Josh Barton

Users

Technology Services

GSuiteAPI

Ecosystem Position

This repo is best treated as legacy or overlapping Google Workspace automation. Repo implementation remains available for reference, but current scheduler evidence does not prove direct production invocation from GSuiteAPI paths.

Atlas links active behavior to more focused repositories where evidence is stronger:

aether
google-classroom-guardians
google-groups-guard
Lifecycle Decision Queue
Scheduler-path evidence currently sits in aether/docs/cron-example.txt, not in this repo, which supports the deprecated/legacy-support classification.

Validation Needed

Script-by-script production status (for example Push-AeriesToGoogleClassroom.sh, Push-AeriesToGoogleGuardianInvites.sh, Push-GoogleGroupsModify.sh) and whether active runtime is aether on sal-01, saw-01 Task Scheduler, or manual execution.
Final legacy-versus-successor boundary including ownership/escalation for any scripts retained here as fallback/manual paths (tracked in the Lifecycle Decision Queue).