Friday, November 20, 2026
HomeGolangThe place do you place migration approval in a Go deployment? -...

The place do you place migration approval in a Go deployment? – Releases


I began go-migrate in 2023 because the migration layer of a personal Go framework. I’ve been releasing its layers independently, together with its structured logger, HaloLog. I’m involved in how different Gophers deal with the handoff between a instrument exhibiting the SQL it intends to run and an operator granting permission to execute it.

Our instance catalog has a SQL desk creation at model 1, a Go backfill at model 2 and a SQL constraint at model 3. A customized Go binary can register the center step with WithGoMigrations and go its embedded SQL by means of WithFS. The backfill makes use of the runner’s Executor. Goose additionally helps blended Go and SQL migrations. One element price reviewing in go-migrate is that an utilized Up SQL file has a checksum, whereas Go perform our bodies don’t have any saved checksum. I maintain the deployed binary identifiable and ship a modified backfill as a brand new model. Go migration sorts · Goose v3

The v1.1.0 change considerations the inventory CLI’s MCP server. Strive sending apply with verify: true and the right plan_id to its default course of. It returns operator_approval_required. An operator can overview the identical goal, SQL and callbacks in a trusted shell, then launch gomigrate mcp --approve-apply "$REVIEWED_PLAN_ID". The agent can spend that grant on one matching try. A second name on the identical course of is refused. Rollback makes use of a individually reviewed down plan. Your personal direct name to m.Up(ctx) nonetheless runs with the authority your software offers it.

One course of can serve a number of MCP classes. They share the identical single-attempt grant. The deployment system controls who could begin that course of with approval flags.

We checked the refusal and the licensed path on the revealed Linux and Home windows amd64 binaries with SQLite. The separate conformance run lined PostgreSQL, MySQL, SQLite, SQL Server, Oracle Database and Db2 LUW. MCP regression · Six-database CI · Launch downloads

When your Go deployment job loses its connection throughout COMMIT, who inspects the author? What proof does your pipeline require earlier than it would grant a retry?

I keep go-migrate and used AI to assist draft this put up.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments