type
RunnerOptions
Explicit operational admissions, bounded timeouts, and resumable boundaries.
Properties
| Property | Type | Description |
|---|---|---|
AllowInsecureDatabase | bool | AllowInsecureDatabase explicitly permits a PostgreSQL connection that can fall back to plaintext. It is intended only for local migration drills. |
AllowMaintenance | bool | AllowMaintenance admits traffic-sensitive semantic steps such as content rewrites, compiled data transforms, resource retirement, and reference-index rebuilds. Every old writer must be stopped while they run. It does not relax artifact validation. |
AllowUnbounded | bool | AllowUnbounded permits a zero operational timeout. Without this explicit admission, zero selects the runner's bounded production default. |
AdvisoryLockWait | time.Duration | AdvisoryLockWait bounds how long this runner waits for another migrator. |
LockTimeout | time.Duration | LockTimeout bounds PostgreSQL lock acquisition inside a phase. |
StatementTimeout | time.Duration | StatementTimeout bounds one transactional SQL statement. |
BatchTimeout | time.Duration | BatchTimeout bounds the complete execution of one checkpoint batch. |
ConcurrentIndexTimeout | time.Duration | ConcurrentIndexTimeout bounds one CREATE/DROP INDEX CONCURRENTLY command. |
IdleInTransactionTimeout | time.Duration | IdleInTransactionTimeout protects a paused transactional phase. |
StopAfterPhase | string | StopAfterPhase and StopAfterStep are explicit, successfully committed rollout boundaries. A transaction phase can stop only at its final step. |
StopAfterStep | string | The StopAfterStep value. |
How it works
AllowMaintenance admits traffic-sensitive steps only after every old writer and worker is stopped; it does not relax artifact validation. Zero timeouts use bounded defaults unless AllowUnbounded is explicit.
Full signature
type RunnerOptions struct {
// AllowInsecureDatabase explicitly permits a PostgreSQL connection that can
// fall back to plaintext. It is intended only for local migration drills.
AllowInsecureDatabase bool
// AllowMaintenance admits traffic-sensitive semantic steps such as content
// rewrites, compiled data transforms, conversion of stored documents to
// versioned documents, resource retirement, and reference-index rebuilds.
// Every old writer must be stopped while they run.
// It does not relax artifact validation.
AllowMaintenance bool
// AllowUnbounded permits a zero operational timeout. Without this explicit
// admission, zero selects the runner's bounded production default.
AllowUnbounded bool
// AdvisoryLockWait bounds how long this runner waits for another migrator.
AdvisoryLockWait time.Duration
// LockTimeout bounds PostgreSQL lock acquisition inside a phase.
LockTimeout time.Duration
// StatementTimeout bounds one transactional SQL statement.
StatementTimeout time.Duration
// BatchTimeout bounds the complete execution of one checkpoint batch.
BatchTimeout time.Duration
// ConcurrentIndexTimeout bounds one CREATE/DROP INDEX CONCURRENTLY command.
ConcurrentIndexTimeout time.Duration
// IdleInTransactionTimeout protects a paused transactional phase.
IdleInTransactionTimeout time.Duration
// StopAfterPhase and StopAfterStep are explicit, successfully committed
// rollout boundaries. A transaction phase can stop only at its final step.
StopAfterPhase string
StopAfterStep string
// contains filtered or unexported fields
}