Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

Latest commit

 

History

History
51 lines (33 loc) · 2.11 KB

artifact-build.mdx

File metadata and controls

51 lines (33 loc) · 2.11 KB
layout page_title sidebar_title description
commands
Commands: Artifact build
artifact build
Build a new versioned artifact from source

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.

Waypoint Artifact build

Command: waypoint artifact build

Build a new versioned artifact from source

@include "commands/artifact-build_desc.mdx"

Usage

Usage: waypoint artifact build [options]

Alias: waypoint build [options]

Build a new versioned artifact from source.

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.

Command Options

  • -push - Push the artifact to the configured registry. The default is true.

@include "commands/artifact-build_more.mdx"