Rollback

Analyze and manage rollbacks of deployed releases

sfp rollback analyze

Analyze whether a deployed release can be safely rolled back to an earlier release. Produces a mechanical delta and (optionally) an AI feasibility verdict.

USAGE
  $ sfp rollback analyze [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>]
    [--current <value>] [--target <value>] [--current-artifacts <value>] [--target-artifacts <value>] [--branch <value>]
    [--ai] [--provider <value>] [--scope <value>] [--npmrcpath <value> [--npm | -f <value>]] [-g <value>...] [--loglevel
    trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -e, --email=<value>               Email address for authenticated user. Ignored if --application-token is provided.
                                    Can be set via SFP_SERVER_USER env var.
  -f, --scriptpath=<value>          Path to a script that fetches artifacts (alternative to npm).
  -g, --logsgroupsymbol=<value>...  Symbol used by CICD platform to group/collapse logs in the console. Provide an
                                    opening group, and an optional closing group symbol.
  -t, --application-token=<value>   Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
                                    (CLI flags take precedence over env vars).
      --[no-]ai                     Run the AI feasibility analysis. Use --no-ai for the mechanical delta only.
      --branch=<value>              Server mode: branch to clone as the basis for reconstructing current source
                                    (defaults to repo default branch).
      --current=<value>             Current (deployed) release ref in domain/releaseName form (server mode), or a
                                    display label in local mode.
      --current-artifacts=<value>   Local mode: directory of pre-built CURRENT release artifacts (skips server + fetch).
      --loglevel=<option>           [default: info] logging level for this command invocation
                                    <options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
      --npm                         Server mode: fetch artifacts from an external NPM registry instead of the internal
                                    registry.
      --npmrcpath=<value>           Path to a .npmrc to use when fetching artifacts via --npm.
      --provider=<value>            AI provider id (e.g. anthropic). Defaults to the server default integration, or env
                                    credentials in local mode.
      --repository=<value>          The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                    for Azure DevOps
      --scope=<value>               NPM scope (without @) when using --npm.
      --sfp-server-url=<value>      URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
                                    config:set server-url
      --target=<value>              Target (earlier) release ref in domain/releaseName form (server mode), or a display
                                    label in local mode.
      --target-artifacts=<value>    Local mode: directory of pre-built TARGET release artifacts (skips server + fetch).

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Analyze whether a deployed release can be safely rolled back to an earlier release. Produces a mechanical delta and
  (optionally) an AI feasibility verdict.

EXAMPLES
  $ sfp rollback analyze --current-artifacts ./artifacts/current --target-artifacts ./artifacts/target --no-ai

  $ sfp rollback analyze --current core/Sprint_27.02 --target core/Sprint_27.01 --repository owner/repo --sfp-server-url http://localhost:3029

On this page