CloudSQLCTL – Production Hardening & Roadmap #9

Kinin-Code-Offical · 2025-12-21T22:05:45Z

Kinin-Code-Offical
Dec 21, 2025
Maintainer

Elevate CloudSQLCTL to a company-grade “production final” standard:

Deterministic GitHub Releases (installer + exe + zip + checksums)
Fully automated self-upgrade (cloudsqlctl upgrade default: check → download → verify → install)
NPM publish (node CLI distribution) integrated with release versioning
Secure machine-scope installation (no user-writable service binaries)
Supportability (support bundle, structured logs, docs automation)

Release pipeline builds SEA exe, builds Inno Setup installer, stages artifacts, uploads to GitHub Release.
Upgrade checks GitHub Releases and verifies SHA256SUMS before applying installer/portable update.
Setup supports gcloud login + ADC + instance selection.

Machine-scope security: ProgramData bin permissions must not allow Users write (service privilege escalation risk).
Release republish: Re-running the same tag should update assets reliably (delete/replace clashing asset names).
Workflow rerun: Manual workflow_dispatch is required for deterministic republish without tag gymnastics.
System-scope update guardrails: system-scope writes require admin/elevation and must be enforced.
Supportability gap: need one-command support bundle zip (logs/config/doctor/paths/status/gcloud info).
Upgrade rollout controls: channel (stable/beta), pinned version, target version install, rollback.
Supply chain: code signing + better release verification is needed for enterprise environments.
NPM publish: define what we publish (node CLI) and keep contents minimal + version-gated.