Artifacts

Build, publish, and query deployment artifacts

sfp artifacts fetch

Fetch artifacts from a registry based on a release definition. When sfp server is configured, artifacts are fetched from sfp server. Use --npm to enable fallback to external npm registries.

USAGE
  $ sfp artifacts fetch -d <value> [--json] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url
    <value>] [-a <value> | -p <value>] [--scope <value>] [--npmrcpath <value> [--npm | -f <value>]]
    [--continue-on-error] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

FLAGS
  -a, --artifacts=<value>          Comma-separated list of artifacts to fetch (format: name:version). Use LATEST_TAG for
                                   latest version
  -d, --artifactdir=<value>        (required) [default: artifacts] Directory to download artifacts into
  -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>         (Optional: no-NPM) Path to script that authenticates and downloads artifacts from the
                                   registry
  -p, --releasedefinition=<value>  Path to release definition file
  -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).
      --continue-on-error          Continue processing other artifacts even if some fail to 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                        Enable fallback to external npm registry if artifact is not found in sfp server
      --npmrcpath=<value>          Path to .npmrc file used for authentication to registry. If --sfp-server-url is
                                   provided, npmrc will be fetched from the server instead. If left blank, defaults to
                                   home directory
      --repository=<value>         The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
                                   for Azure DevOps
      --scope=<value>              (required for NPM) User or Organisation scope of the NPM package
      --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

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Fetch artifacts from a registry based on a release definition. When sfp server is configured, artifacts are fetched
  from sfp server. Use --npm to enable fallback to external npm registries.

EXAMPLES
  $ sfp artifacts:fetch -p myreleasedefinition.yaml -f myscript.sh

  $ sfp artifacts:fetch -p myreleasedefinition.yaml --npm --scope myscope --npmrcpath path/to/.npmrc

  $ sfp artifacts:fetch -p myreleasedefinition.yaml --npm --scope myscope --sfp-server-url http://localhost:3029

  $ sfp artifacts:fetch --artifacts package1:1.0.0,package2:LATEST_TAG --npm --scope myscope

See code: src/commands/artifacts/fetch.tsarrow-up-right

sfp artifacts list

List available versions of artifacts in the registry. When sfp server is configured, lists versions from sfp server.

See code: src/commands/artifacts/list.tsarrow-up-right

sfp artifacts promote

Promotes artifacts predominantly for unlocked packages with code coverage greater than 75%

See code: src/commands/artifacts/promote.tsarrow-up-right

Last updated

Was this helpful?