divekit plugin migrate

Synopsis

Convert flat v1 plugin state and its materialized layout to plugin suites.

The command prints the full plan and changes nothing until ‘–apply’ is passed. An applied migration copies every file it overwrites into ‘.divekit/backup/plugin-migrate-<timestamp>/’, which ‘–rollback’ restores.

Before writing, apply verifies the published suite, resolves enabled plugins to release tags and image digests, and composes the resulting pipeline. If the suite is incomplete, the origin stays unchanged on contract v1.

Usage

divekit plugin migrate [flags]

Examples

# Show what a migration would change
divekit plugin migrate

# Execute the plan
divekit plugin migrate --apply

# Restore the origin from the most recent migration backup
divekit plugin migrate --rollback

Flags

--apply      Execute the printed migration plan instead of only showing it
      --rollback   Restore the origin from the most recent migration backup

Inherited Flags

-d, --distribution string   Target distribution override (default: project-level eval overrides and .divekit state)
  -l, --loglevel string       log level (debug, info, warn, error, fatal) (default "info")
      --no-index              skip project index update
      --non-interactive       run in non-interactive mode (fails if interactive input is required)
  -y, --yes                   assume yes/default for all prompts (non-interactive with automatic defaults)

Parent Command

• divekit plugin