Edit this page on GitHub
»Waypoint Config sync
waypoint config sync
Synchronize declared variables and pipeline configs in a waypoint.hcl
waypoint config sync [options]
Synchronize declared application configuration in the waypoint.hcl file for existing and new deployments.
Conflicting configuration keys will be overwritten. Configuration keys that do not exist in the waypoint.hcl file but exist on the server will not be deleted.
-plain- Plain output: no colors, no animation. The default is false.
-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.