spatial cloud launch
Launch a deployment.
Orchestrate a new deployment to run the given code with and tag the deployment. Launching while uploading to the same assembly name in parallel can result in undefined behavior.
spatial cloud launch <assembly name> <launch configuration> <deployment name> [flags]
--cluster string Cluster to create the deployment in. For example, 'gce-us-central1-c'. Leave blank to automatically pick. --deployment_description string Description for the deployment. --experimental_runtime string Specify an experimental runtime version to launch with. Defaults to using the stable released version. --hide_overview_page Set flag to not open the deployment overview page. --no_history Do not create a new history. You should normally never need to specify this. --snapshot string Path to the snapshot to start the deployment from. (default "no snapshot") --tags strings Comma-delimited list of tags to attach to the new deployment. --upload_timeout duration Snapshot upload timeout ('2s', '1m', etc). (default 2m0s)
Options inherited from parent commands
--json_output Print output in JSON format. Useful when you need to parse the Spatial CLI output. --log_directory string Sets the directory log files will be created in. If not specified, this is set to <project_root>/logs when inside a project directory and logging is disabled when outside a project directory. --log_level string Sets the log level. Available log levels: debug, info, warning, error, fatal, or panic. --main_config string The path to your project's main configuration file (usually called spatialos.json) --no_animation Disable dynamic output elements such as the spinner, progress bars, etc. --project_name string This flag overrides the project name given in the spatialos.json file of the current SpatialOS project (if there is one).