Note that in version 1.4.0 the syntax for certain commands has changed. Check out the release notes and the description of the updated commands on this page.
The following commands refer to bacalhau cli version v1.4.0. For installing or upgrading a client, follow the instructions in the installation page. Run bacalhau version in a terminal to check what version you have.
Let’s run the bacalhau help command in the terminal to find out information about available commands and flags:
Compute over data
Usage:
bacalhau [command]
Available Commands:
agent Commands to query agent information.
completion Generate the autocompletion script for the specified shell
config Interact with the bacalhau configuration system.
devstack Start a cluster of bacalhau nodes for testing and development
docker Run a docker job on the network (see run subcommand)
exec Execute a specific job type
help Help about any command
job Commands to submit, query and update jobs.
node Commands to query and update nodes information.
serve Start the bacalhau compute node
version Get the client and server version.
wasm Run and prepare WASM jobs on the network
Flags:
--api-host string The host for the client and server to communicate on (via REST).
Ignored if BACALHAU_API_HOST environment variable is set. (default "bootstrap.production.bacalhau.org")
--api-port int The port for the client and server to communicate on (via REST).
Ignored if BACALHAU_API_PORT environment variable is set. (default 1234)
--cacert string The location of a CA certificate file when self-signed certificates
are used by the server
-h, --help help for bacalhau
--insecure Enables TLS but does not verify certificates
--log-mode logging-mode Log format: 'default','station','json','combined','event' (default default)
--repo string path to bacalhau repo (default "/home/u/.bacalhau")
--tls Instructs the client to use TLS
Use "bacalhau [command] --help" for more information about a command.
Global flags
--api-host string
Determines the host for RESTful communication between the client and server. This flag is ignored if the BACALHAU_API_HOST environment variable is set.
Default: bootstrap.production.bacalhau.org
--api-port int
Determines the port for RESTful communication between the client and server. This flag is ignored if the BACALHAU_API_PORT environment variable is active.
Default: 1234
--log-mode logging-mode
Determines the preferred log format. Available log formats are: default, station, json, combined, event.
Default: default
--repo string
Specifies the path to the bacalhau repository.
Default: $HOME/.bacalhau
The bacalhau agent command is a parent command that offers sub-commands to query information about the Bacalhau agent. This can be useful for debugging, monitoring, or managing the agent's behavior and health.
The bacalhau agent alive command retrieves the agent's liveness and health information. This can be helpful to determine if the agent is running and healthy.
Flags:-h,--helphelpforalive--outputformatTheoutputformatforthecommand (one of ["json""yaml"]) (defaultyaml)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
--output format
Determines the format in which the output is displayed. Available formats include JSON and YAML. Default: yaml
--pretty
Formats the output for enhanced readability. This flag is relevant only when using JSON or YAML output formats.
The bacalhau agent node command gathers the agent's node-related information. This might include details about the machine or environment where the agent is running, available resources, supported engines, etc.
Flags:-h,--helphelpfornode--outputformatTheoutputformatforthecommand (one of ["json""yaml"]) (defaultyaml)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
The bacalhau agent version command is used to obtain the version of the bacalhau agent.
Flags:-h,--helphelpforversion--outputformatTheoutputformatforthecommand (one of ["json""yaml"])--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
To load completions in your current shell session:
bacalhau completion fish | source
To load completions for every new session, execute once:
bacalhau completion fish > ~/.config/fish/completions/bacalhau.fish
You will need to start a new shell for this setup to take effect.
To load completions in your current shell session:
bacalhau completion powershell | Out-String | Invoke-Expression
To load completions for every new session, add the output of the above command to your powershell profile.
If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once:
echo "autoload -U compinit; compinit" >> ~/.zshrc
The bacalhau config command is a parent command that offers sub-commands to modify and query information about the Bacalhau config. This can be useful for debugging, monitoring, or managing the nodes configuration.
The bacalhau config auto-resources command automatically configures compute resource values in the bacalhau node's configuration file based on the hardware resources of the user's machine. This command streamlines the process of resource allocation for jobs, dynamically adjusting settings to align with the capabilities of the machine. It is designed to simplify the task of resource management, ensuring that the node operates efficiently and effectively within the hardware's limits.
The bacalhau config auto-resources command intelligently adjusts resource allocation settings based on the specific hardware configuration of your machine, promoting optimal utilization for bacalhau jobs. Due to the dynamic nature of this command, the specific values set in the configuration will vary depending on the available hardware resources of the machine in use. This functionality is particularly beneficial for users who seek to optimize their node's performance without the need for manual calculations of resource limits. It is important for users to understand that these settings will directly impact the number and types of jobs their node can manage at any given time, based on the machine's resource capacity.
Flags: --default-job-percentage int Percentage expressed as a number from 1 to 100 representing default per job amount of resources jobs will get when they don't specify any resource limits themselves (values over 100 will be rejected (default 75)
--job-percentage int Percentage expressed as a number from 1 to 100 representing per job amount of resource the system can be using at one time for a single job (values over 100 will be rejected) (default 75)
--total-percentage int Percentage expressed as a number from 1 to 100 representing total amount of resource the system can be using at one time in aggregate for all jobs (values over 100 will be rejected) (default 75)
The bacalhau config list command lists the configuration keys and values of the bacalhau node. This command is useful for understanding how configuration keys map to their respective values, aiding in the use of the bacalhau config set command.
Configuration values displayed by this command represent the settings that will be applied when the bacalhau node is next restarted. It is important to note that these values may not reflect the current operational configuration of an active bacalhau node. The displayed configuration is relevant and accurate for a node that is either not currently running or that has been restarted after the execution of this command.
The bacalhau config set command sets a value in the bacalhau node's configuration file. This command is used to modify the configuration file that the bacalhau node will reference for its settings. Key names in the configuration are case-insensitive. Additionally, the command validates the value being set based on the type of the configuration key, ensuring that only appropriate and valid configurations are applied.
Changes made using this command will be applied to the configuration file, but they do not immediately affect the running configuration of an active bacalhau node. The modifications will take effect only after the node is restarted.
The bacalhau devstack command is used to start a cluster of nodes and run a job on them.
Usage:
bacalhaudevstack [flags]
Flags:
--Noop Use the noop executor for all jobs
--allow-listed-local-paths strings Local paths that are allowed to be mounted into jobs. Multiple paths can be specified by using this flag multiple times.
--autocert string Specifies a host name for which ACME is used to obtain a TLS Certificate.
Using this option results in the API serving over HTTPS
--bad-compute-actors int How many compute nodes should be bad actors
--bad-requester-actors int How many requester nodes should be bad actors
--compute-nodes int How many compute only nodes should be started in the cluster (default 3)
--cpu-profiling-file string File to save CPU profiling to
--default-job-execution-timeout duration default value for the execution timeout this compute node will assign to jobs with no timeout requirement defined. (default 10m0s)
--default-publisher string A default publisher to apply to all jobs without a publisher
--disable-engine strings Engine types to disable
--disable-storage strings Storage types to disable
--disabled-publisher strings Publisher types to disable
--docker-manifest-cache-duration duration The default time-to-live for each record in the manifest cache (default 1h0m0s)
--docker-manifest-cache-frequency duration The frequency that the checks for stale records is performed (default 1h0m0s)
--docker-manifest-cache-size uint Specifies the number of items that can be held in the manifest cache (default 1000)
--hybrid-nodes int How many hybrid (requester and compute) nodes should be started in the cluster
--ignore-physical-resource-limits When set the compute node will ignore is physical resource limits
--job-execution-timeout-bypass-client-id strings List of IDs of clients that are allowed to bypass the job execution timeout check
--job-negotiation-timeout duration Timeout value to hold a bid for a job. (default 3m0s)
--job-selection-accept-networked Accept jobs that require network access.
--job-selection-data-locality local|anywhere Only accept jobs that reference data we have locally ("local") or anywhere ("anywhere"). (default Anywhere)
--job-selection-probe-exec string Use the result of a exec an external program to decide if we should take on the job.
--job-selection-probe-http string Use the result of a HTTP POST to decide if we should take on the job.
--job-selection-reject-stateless Reject jobs that don't specify any data.
--limit-job-cpu string Job CPU core limit to run all jobs (e.g. 500m, 2, 8).
--limit-job-gpu string Job GPU limit to run all jobs (e.g. 1, 2, or 8).
--limit-job-memory string Job Memory limit to run all jobs (e.g. 500Mb, 2Gb, 8Gb).
--limit-total-cpu string Total CPU core limit to run all jobs (e.g. 500m, 2, 8).
--limit-total-gpu string Total GPU limit to run all jobs (e.g. 1, 2, or 8).
--limit-total-memory string Total Memory limit to run all jobs (e.g. 500Mb, 2Gb, 8Gb).
--max-job-execution-timeout duration The maximum execution timeout this compute node supports. Jobs with higher timeout requirements will not be bid on. (default 2562047h47m16s)
--memory-profiling-file string File to save memory profiling to
--min-job-execution-timeout duration The minimum execution timeout this compute node supports. Jobs with lower timeout requirements will not be bid on. (default 500ms)
--peer string Connect node 0 to another network node
--pluggable-executors Will use pluggable executors when set to true
--requester-job-translation-enabled Whether jobs should be translated at the requester node or not. Default: false
--requester-nodes int How many requester only nodes should be started in the cluster (default 1)
--self-signed Specifies whether to auto-generate a self-signed certificate for the requester node
--stack-repo string Folder to act as the devstack configuration repo
--tlscert string Specifies a TLS certificate file to be used by the requester node
--tlskey string Specifies a TLS key file matching the certificate to be used by the requester node
Flags:-c,--constraintsstringSelector (label query) to filter nodes on which this job can be executed.Supports'=','==',and'!='.(e.g.-skey1=value1,key2=value2).Matchingobjectsmustsatisfyallofthespecifiedlabelconstraints.--countintHowmanynodesshouldrunthejob. (default 1)--cpustringJobCPUcores (e.g. 500m,2,8).--diskstringJobDiskrequirement (e.g. 500Gb,2Tb,8Tb).--domainstringArrayDomain(s) thatthejobneedstoaccess (for HTTPnetworking)--dry-runDonotsubmitthejob,butinsteadprintoutwhatwillbesubmitted--entrypointstringsOverridethedefaultENTRYPOINToftheimage-e,--envstringsTheenvironmentvariablestosupplytothejob (e.g. --envFOO=bar--envBAR=baz)-f,--followWhenspecifiedwillfollowtheoutputfromthejobasitruns--gpustringJobGPUrequirement (e.g. 1,2,8).--id-onlyPrintoutonlytheJobIDonsuccessfulsubmission. -i, --input storage Mount URIs as inputs to the job. Can be specified multiple times. Format: src=URI,dst=PATH[,opt=key=value]
Examples:# Mount IPFS CID to /inputs directory-iipfs://QmeZRGhe4PmjctYVSVHuEiA9oSXnqmYa4kQubSHgWbjv72# Mount S3 object to a specific path-is3://bucket/key,dst=/my/input/path# Mount S3 object with specific endpoint and region -i src=s3://bucket/key,dst=/my/input/path,opt=endpoint=https://s3.example.com,opt=region=us-east-1
--ipfs-connect string The ipfs host multiaddress to connect to, otherwise an in-process IPFS node will be created if not set.
-l, --labels strings List of labels for the job. Enter multiple in the format '-labels env=prod -label region=earth'.
Valid label keys must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character.
Valid label values must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end
withanalphanumericcharacter.--memorystringJobMemoryrequirement (e.g. 500Mb,2Gb,8Gb).--namestringThenametorefertothisjobby.--namespacestringThenamespacetoassociatewiththisjob. (default "default")--networknetwork-typeNetworkingcapabilityrequiredbythejob.None,HTTP,orFull (default None)--node-detailsPrintoutdetailsofallnodes (overridden by--id-only). -o, --output ResultPath name=path of the output data volumes. 'outputs:/outputs' is always added unless '/outputs' is mapped to a different name.
--priorityintThepriorityofthejob.-p,--publisherpublisherWheretopublishtheresultofthejob--queue-timeoutintJobqueuetimeoutinseconds (e.g. 300for5minutes). zero timeout means no queueing is enabled and jobs will fail if they cannot be scheduled immediately
--target all|any Whether to target the minimum number of matching nodes ("any") (default) or all matching nodes ("all"). (default any)
--task-namestringThenametorefertothistaskby (default "main")--timeoutintJobexecutiontimeoutinseconds (e.g. 300for5minutes) --wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int When using --wait, how many seconds to wait for the job to complete before giving up. (default 600)
-w, --workdir string Working directory inside the container. Overrides the working directory shipped with the image (e.g. via WORKDIR in Dockerfile).
Let's run a Docker job, using the image dpokidov/imagemagick, with a CID mounted at /input_images and an output volume mounted at /outputs in the container. All flags after the -- are passed directly into the container for execution:
This command allows you to start a job in a Docker container using the specified image, mount an external CID resource from IPFS inside the container to handle images, and execute a command inside the container to process files.
To check the job specification before submitting it to the bacalhau network, run:
bacalhaudockerrun--dry-runubuntuechohello
The command does not run the job itself, but only displays information about how it would be run so you can make sure that all job parameters and commands are correctly specified before sending it to the Bacalhau network for execution
To save the job specification to a YAML file, run:
The command starts an Ubuntu image container using a specific version of the image identified by its SHA256 hash. This ensures the accuracy of the image source, independent of its tag and possible future changes, since the image digest remains constant for a particular version.
The bacalhau exec command is used to execute a specific job type.
Usage:
bacalhauexec [jobtype] [flags]
Flags:--codestringSpecifiesthefile,ordirectoryofcodetosendwiththerequest--dry-runDonotsubmitthejob,butinsteadprintoutwhatwillbesubmitted-e,--envstringsTheenvironmentvariablestosupplytothejob (e.g. --envFOO=bar--envBAR=baz)-f,--followWhenspecifiedwillfollowtheoutputfromthejobasitruns-h,--helphelpforexec--id-onlyPrintoutonlytheJobIDonsuccessfulsubmission. -i, --input storage Mount URIs as inputs to the job. Can be specified multiple times. Format: src=URI,dst=PATH[,opt=key=value]
Examples:# Mount IPFS CID to /inputs directory-iipfs://QmeZRGhe4PmjctYVSVHuEiA9oSXnqmYa4kQubSHgWbjv72# Mount S3 object to a specific path-is3://bucket/key,dst=/my/input/path# Mount S3 object with specific endpoint and region -i src=s3://bucket/key,dst=/my/input/path,opt=endpoint=https://s3.example.com,opt=region=us-east-1
-l, --labels strings List of labels for the job. Enter multiple in the format '-l a -l 2'. All characters not matching /a-zA-Z0-9_:|-/ and all emojis will be stripped.
--node-detailsPrintoutdetailsofallnodes (overridden by--id-only). -o, --output strings name:path of the output data volumes. 'outputs:/outputs' is always added unless '/outputs' is mapped to a different name. (default [outputs:/outputs])
-p,--publisherpublisherWheretopublishtheresultofthejob (default ipfs) -s, --selector string Selector (label query) to filter nodes on which this job can be executed, supports '=', '==', and '!='.(e.g. -s key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints.
--timeoutintJobexecutiontimeoutinseconds (e.g. 300for5minutes) --wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int When using --wait, how many seconds to wait for the job to complete before giving up. (default 600)
The bacalhau agent node command shows bacalhau node id info.
Usage:
bacalhauagentnode [flags]
Flags:-h,--helphelpforid--hide-headerdonotprintthecolumnheaders.--no-styleremoveallstylingfromtableoutput.--outputformatTheoutputformatforthecommand (one of ["table""csv""json""yaml"]) (defaultjson) --peer string A comma-separated list of libp2p multiaddress to connect to. Use "none" to avoid connecting to any peer, "env" to connect to the default peer list of your active environment (see BACALHAU_ENVIRONMENT env var). (default "none")
--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.--swarm-portintTheporttolistenonforswarmconnections. (default 1235)--widePrintfullvaluesinthetableresults
The bacalhau job command provides a suite of sub-commands to submit, query, and manage jobs within Bacalhau. Users can deploy jobs, obtain job details, track execution logs, and more.
The bacalhau job describe command provides a detailed description of a specific job in YAML format. This description can be particularly useful when wanting to understand the attributes and current status of a specific job. To list all available jobs, the bacalhau job list command can be used.
Flags:-h,--helphelpfordescribe--outputformatTheoutputformatforthecommand (one of ["json""yaml"]) (defaultyaml)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.
The bacalhau job get command is used to get the results of the job, including stdout and stderr.
Usage:
bacalhaujobget [id] [flags]
Flags:--download-timeout-secsdurationTimeoutdurationforIPFSdownloads. (default 5m0s)-h,--helphelpforget --ipfs-connect string The ipfs host multiaddress to connect to, otherwise an in-process IPFS node will be created if not set.
--ipfs-serve-pathstringpathlocalIpfsnodewillpersistdatato --ipfs-swarm-addrs strings IPFS multiaddress to connect the in-process IPFS node to - cannot be used with --ipfs-connect. (default [/ip4/35.245.161.250/tcp/4001/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/35.245.161.250/udp/4001/quic/p2p/12D3KooWAQpZzf3qiNxpwizXeArGjft98ZBoMNgVNNpoWtKAvtYH,/ip4/34.86.254.26/tcp/4001/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/34.86.254.26/udp/4001/quic/p2p/12D3KooWLfFBjDo8dFe1Q4kSm8inKjPeHzmLBkQ1QAjTHocAUazK,/ip4/35.245.215.155/tcp/4001/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/35.245.215.155/udp/4001/quic/p2p/12D3KooWH3rxmhLUrpzg81KAwUuXXuqeGt4qyWRniunb5ipjemFF,/ip4/34.145.201.224/tcp/4001/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/34.145.201.224/udp/4001/quic/p2p/12D3KooWBCBZnXnNbjxqqxu2oygPdLGseEbfMbFhrkDTRjUNnZYf,/ip4/35.245.41.51/tcp/4001/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa,/ip4/35.245.41.51/udp/4001/quic/p2p/12D3KooWJM8j97yoDTb7B9xV1WpBXakT4Zof3aMgFuSQQH56rCXa])
--ipfs-swarm-keystringOptionalIPFSswarmkeyrequiredtoconnecttoaprivateIPFSswarm--output-dirstringDirectorytowritetheoutputto. --private-internal-ipfs Whether the in-process IPFS node should auto-discover other nodes, including the public IPFS network - cannot be used with --ipfs-connect. Use "--private-internal-ipfs=false" to disable. To persist a local Ipfs node, set BACALHAU_SERVE_IPFS_PATH to a valid path. (default true)
--rawDownloadrawresultCIDsinsteadofmergingmultipleCIDsintoasingleresult
The bacalhau job executions command retrieves a list of executions for a specific job based on its ID. This can be essential when tracking the various runs and their respective states for a particular job.
Flags:-h,--helphelpforexecutions--hide-headerdonotprintthecolumnheaderswhendisplayingtheresults.--limituint32Limitthenumberofresultsreturned (default 20)--next-tokenstringUsesthespecifiedtokenforpagination.Usefulforfetchingthenextsetofresults.--no-styleremoveallstylingfromtableoutputdisplayingrawdata. --order-by string Order results based on a specific field. Valid fields are: modify_time, create_time, id, state
--order-reversedReversetheorderoftheresults.Usefulinconjunctionwith--order-by. --output format Specify the output format for the command (one of ["table" "csv" "json" "yaml"]) (default table)
--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.--widePrintfullvaluesinthetableresultwithouttruncatinganyinformation.
The bacalhau job history command lists the history events of a specific job based on its ID. This feature allows users to track changes, executions, and other significant milestones associated with a particular job.
Flags:--event-typestringThetypeofhistoryeventstoreturn.Oneof:all,job,execution (default "all")--execution-idstringFiltersresultsbyaspecificexecutionID.-h,--helphelpforhistory--hide-headerdonotprintthecolumnheaders.--limituint32Limitthenumberofresultsreturned--next-tokenstringUsesthespecifiedtokenforpagination.--no-styleremoveallstylingfromtableoutput.--node-idstringFilterstheresultsbyaspecificnodeID.--order-bystringOrderresultsbyafield--order-reversedReversetheorderoftheresults--outputformatTheoutputformatforthecommand (one of ["table""csv""json""yaml"]) (defaulttable)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.--widePrintfullvaluesinthetableresultswithouttruncatinganyinformation.
The bacalhau job list command provides a listing of all submitted jobs. This command offers an overview of all tasks and processes registered in the system, allowing users to monitor and manage their jobs effectively.
Flags:-h,--helphelpforlist--hide-headerdonotprintthecolumnheaders. --labels string Filter nodes by labels. See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more information. (default "bacalhau_canary != true")
--limituint32Limitthenumberofresultsreturned (default 10)--next-tokenstringUsesthespecifiedtokenforpagination.--no-styleremoveallstylingfromtableoutput.--order-bystringOrderresultsbyafield.Validfieldsare:id,created_at--order-reversedReversetheorderoftheresults--outputformatTheoutputformatforthecommand (one of ["table""csv""json""yaml"]) (defaulttable)--prettyPrettyprinttheoutput.Onlyappliestojsonandyamloutputformats.--widePrintfullvaluesinthetableresultswithouttruncatinganyinformation.
The bacalhau job logs command allows users to retrieve logs from a job that has been previously submitted. This command is useful for tracking and debugging the progress and state of a running or completed job.
To display Logs for a Previously Submitted Job using Full Job ID, run:
bacalhaujoblogsj-51225160-807e-48b8-88c9-28311c7899e1ExpectedOutput:[2023-09-24 09:01:32] INFO - Application started successfully.[2023-09-24 09:01:33] DEBUG - Initializing database connections.[2023-09-24 09:01:35] WARN - API rate limit approaching.[2023-09-24 09:02:01] ERROR - Failed to retrieve data from endpoint: /api/v1/data.[2023-09-24 09:05:00] INFO - Data sync completed with 4500 new records.
To follow Logs in Real-Time, run:
bacalhaujoblogs--followj-51225160-807e-48b8-88c9-28311c7899e1ExpectedOutput:[2023-09-24 11:30:02] INFO - User 'john_doe' logged in successfully.[2023-09-24 11:30:15] DEBUG - Fetching data from cache for key: userSettings_john_doe.[2023-09-24 11:31:05] WARN - High memory usage detected: 85% of allocated resources.... [Logs continuetoappearinreal-time]...
The bacalhau job run command facilitates the initiation of a job from a file or directly from the standard input (stdin). The command supports both JSON and YAML data formats. This command is particularly useful for quickly executing a job without the need for manual configurations.
Flags:--dry-runDonotsubmitthejob,butinsteadprintoutwhatwillbesubmitted-f,--followWhenspecifiedwillcontinuouslydisplaytheoutputfromthejobasitruns-h,--helphelpforrun--id-onlyPrintoutonlytheJobIDonsuccessfulsubmission. --no-template Disable the templating feature. When this flag is set, the job spec will be used as-is, without any placeholder replacements
--node-details Print out details of all nodes (Note that this flag is overridden if --id-only is provided).
--show-warningsShowsanywarningsthatoccurduringthejobsubmission -E, --template-envs string Specify a regular expression pattern for selecting environment variables to be included as template variables in the job spec.
e.g.--template-envs".*"willincludeallenvironmentvariables.-V,--template-varsstringToStringReplaceaplaceholderinthejobspecwithavalue.e.g.--template-varsfoo=bar --wait Wait for the job to finish. Use --wait=false to return as soon as the job is submitted. (default true)
--wait-timeout-secs int If --wait is provided, this flag sets the maximum time (in seconds) the command will wait for the job to finish before it terminates. (default 600)
