ST-2026-158 · SDKs, clients & toolchains
Google Cloud CLI 578 makes DMS conversion operations auto-commit by default
Google Cloud CLI 578.0.0 makes --auto-commit the default for Database Migration conversion-workspace seed, convert and import-rules operations; --no-auto-commit opts out.
Google Cloud CLIDatabase Migrationconversion workspaceauto-commitbreaking default
Previous state
The named conversion-workspace operations did not auto-commit by default.
Current state
seed, convert and import-rules auto-commit unless callers pass --no-auto-commit.
Affected users
Who needs to care
Database Migration Service automation invoking the three named conversion-workspace operations.
Required response
What to do
Add --no-auto-commit where review-before-commit semantics are required and test on CLI 578 or later.
Evidence boundary
What the source does not prove
The default change is limited to seed, convert and import-rules under conversion-workspaces.
Lifecycle history
Dated event sequence
- Auto-commit became default
CLI 578.0.0 shipped the opt-out default.
Evidence ledger
First-party sources
- 01Google Cloud — Google Cloud CLI release notes — 578.0.0
Official CLI release notes · 2026-07-28
Open official source ↗