Waypoint Artifact push

Warning

This content is part of the legacy version of Waypoint that is no longer actively maintained. For additional information on the new vision of Waypoint, check out this blog post and the HCP Waypoint documentation.

Command: waypoint artifact push

Push a build's artifact to a registry

Usage

Usage: waypoint artifact push [options]

Alias: waypoint push [options]

Push a local build to a registry. This will push the most recent successful local build by default. You can view a list of the recent local builds using "artifact list-builds" command.

Global Options

-plain - Plain output: no colors, no animation. The default is false.
-app=<string> (-a) - App to target. Certain commands require a single app target for Waypoint configurations with multiple apps. If you have a single app, then this can be ignored.
-project=<string> (-p) - Project to target.
-workspace=<string> (-w) - Workspace to operate in.

Operation Options

-label=<key=value> - Labels to set for this operation. Can be specified multiple times.
-local - True to use a local runner to execute the operation, false to use a remote runner. If unset, Waypoint will automatically determine where the operation will occur, defaulting to remote if possible.
-remote-source=<key=value> - Override configurations for how remote runners source data. This is specified to the data source type being used in your configuration. This is used for example to set a specific Git ref to run against.
-var=<key=value> - Variable value to set for this operation. Can be specified multiple times.
-var-file=<string> - HCL or JSON file containing variable values to set for this operation. If any ".auto.wpvars" or ".auto.wpvars.json" files are present, they will be automatically loaded.