pscale maintenance
Inspect read-only maintenance schedule and window data for Vitess databases on Enterprise plans.
Prerequisites
- Authenticate with
pscale auth check --format json. - Identify the exact organization and Vitess database.
- Pass
--orgexplicitly rather than relying on the configured default organization. - Prefer
--format jsonfor automation and preserve schedule IDs as opaque values.
Inspect schedules
# Discover schedules and stable IDs
pscale maintenance list <database> \
--org <org> \
--format json
# Inspect one schedule in full
pscale maintenance show <database> <schedule-id> \
--org <org> \
--format json
Schedule output can include whether the schedule is enabled or required, frequency, day/week/hour, duration, next and last window times, pending Vitess/MySQL versions, expiry, and deadline metadata. Treat all timestamps in JSON as authoritative API values; do not infer a local timezone from human table output.
Monthly schedules include a week-of-month value. Non-monthly table rows show a dash for week because the field does not apply.
Inspect maintenance windows
pscale maintenance windows <database> <schedule-id> \
--org <org> \
--format json
Windows are historical or active instances associated with the selected schedule. Use their start and finish timestamps to distinguish completed work from a future schedule. An empty result means no windows currently exist for that schedule; it does not prove maintenance is disabled.
Safe review workflow
- Run
pscale database show <database> --org <org> --format jsonand confirm the database engine and identity. - List schedules and select the exact schedule ID from live output.
- Show the schedule before interpreting pending versions, expiry, or deadline fields.
- List its windows and report schedule metadata separately from observed window history.
- Do not claim these read-only commands reschedule, approve, or cancel maintenance; the current CLI surface only lists and shows records.
Troubleshooting
- Command unavailable: update
pscaleand verify livepscale maintenance --help. - Not found: re-run the list against the exact organization/database and copy the schedule ID without modification.
- No schedules: confirm the database is Vitess and that the organization has the applicable Enterprise maintenance feature.
- Unexpected day/week: inspect JSON fields and frequency together; week-of-month applies only to monthly schedules.
See references/commands.md for checksum-verified command help.