The Waypoint website is being redesigned to help you find what you are looking for more effectively.
»Waypoint Deployment deploy
waypoint deployment deploy
Deploy a pushed artifact
waypoint deployment deploy [options]
Deploy an application. This will deploy the most recent successful pushed artifact by default. You can view a list of recent artifacts using the "artifact list" command.
By default, "waypoint deploy" automatically performs a release. This behavior can be disabled by using the "-release=false" flag.
-plain- Plain output: no colors, no animation.
-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.
-p) - Project to target.
-w) - Workspace to operate in.
-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.
-release- Release this deployment immediately.