migration

func BuildClusterLinkConfig ¶ added in v0.8.1

func BuildClusterLinkConfig(config *types.MigrationConfig, apiKey, apiSecret string) clusterlink.Config

BuildClusterLinkConfig assembles a clusterlink.Config from a migration config plus runtime API credentials. Centralized here so the bookend callers in cmd/migration/execute don't duplicate the field layout.

func DisableOffsetSync ¶ added in v0.8.1

func DisableOffsetSync(
	ctx context.Context,
	cl clusterlink.Service,
	clCfg clusterlink.Config,
	config *types.MigrationConfig,
	persist func() error,
) error

DisableOffsetSync runs the pre-execute disable bookend for the --pause-consumer-offset-sync flow.

No-op cases (return nil without contacting the cluster link):

• intent flag not set
• migration is already at StateSwitched (re-run after success)
• PauseConsumerOffsetSyncFlipped is already true (resume after partial failure)

Active path: re-queries the cluster link for drift, calls AlterConfigs to set consumer.offset.sync.enable=false, sets PauseConsumerOffsetSyncFlipped, and persists the marker before returning.

A non-nil error stops execution before the FSM runs (R12).

func RestoreOffsetSync ¶ added in v0.8.1

func RestoreOffsetSync(
	_ context.Context,
	cl clusterlink.Service,
	clCfg clusterlink.Config,
	config *types.MigrationConfig,
	persist func() error,
)

RestoreOffsetSync runs the post-execute restore bookend. Soft-failure semantics: ListConfigs or AlterConfigs failure prints a remediation message to stderr but does NOT propagate an error, because the switchover itself succeeded (R13). The PauseConsumerOffsetSyncFlipped marker stays true on failure so the state file records that a restore is still owed.

Diff-based restore: when MigrationConfig.ClusterLinkConfigs holds an init snapshot, restore queries the cluster link for its current consumer.offset.* state and re-applies snapshot values for keys that the disable bookend cleared (current is missing, empty, or "false"). Keys whose current value looks like a deliberate post-disable operator change (non-empty, non-"false", differs from snapshot) are left alone. When the snapshot is empty (defensive fallback for unforeseen state-file lifecycles), restore performs a single SET consumer.offset.sync.enable=true.

The ctx argument is accepted for symmetry with DisableOffsetSync but the network calls use a fresh background ctx with a per-call timeout. The restore must run even when the parent ctx is already cancelled (e.g. a signal arrived between orchestrator.Execute returning and the bookend firing) — that is the case the soft-fail semantic exists for. Each PUT gets its own timeout budget so a slow endpoint on one key cannot starve the rest of the restore.

func WarnIfPausedOnExecuteFailure ¶ added in v0.8.1

func WarnIfPausedOnExecuteFailure(config *types.MigrationConfig, execErr error)

WarnIfPausedOnExecuteFailure prints a stderr remediation message when orchestrator.Execute returns an error while the cluster link is still in the disabled state (PauseConsumerOffsetSyncFlipped=true). The restore bookend only runs after a successful execute, so without this warning the operator has no signal that the cluster link is paused.

Soft-fail: never returns an error — this is best-effort messaging on top of the underlying execute error.