metaplay deploy botclient [ENVIRONMENT] [IMAGE_TAG] [flags] [-- EXTRA_ARGS]

PREVIEW: This command is in preview and subject to change! It also still lacks some key functionality.

Deploy bots into the target cloud environment using the specified docker image version. The image must exist in the target environment image repository.

Expected arguments:

• ENVIRONMENT (optional) -- Target environment name or id, eg, 'lovely-wombats-build-nimbly'.
• IMAGE_TAG -- Docker image name and tag, eg, '364cff09'.
• EXTRA_ARGS (optional) -- Passed as-is to Helm.

Related commands:

• 'metaplay build image ...' to build the docker image.
• 'metaplay image push ...' to push the built image to the environment.
• 'metaplay debug logs ...' to view logs from the deployed server.
• 'metaplay debug shell ...' to debug a running server pod.

Examples

# Deploy bots into environment nimbly with the docker image tag 364cff09.
metaplay deploy botclient nimbly 364cff09

Flags

• --helm-chart-repo <string>: Override for Helm chart repository to use for the metaplay-loadtest chart
• --helm-chart-version <string>: Override for Helm chart version to use, eg, '0.4.2'
• --helm-release-name <string>: Helm release name to use for the bot deployment (defaults to '<environmentID>-loadtest'
• --local-chart-path <string>: Path to a local version of the metaplay-loadtest chart (repository and version are ignored if this is set)
• --values <string>: Override for path to the Helm values file, e.g., 'Backend/Deployments/develop-botclients.yaml'

Inherited Flags

• --color <string>: Should the output be colored (yes/no/auto)? [env: METAPLAYCLI_COLOR] (default: auto)
• --project <string>: Path to the to project directory (where metaplay-project.yaml is located)
• --skip-version-check: Skip the check for a new CLI version being available
• --verbose: Enable verbose logging, useful for troubleshooting [env: METAPLAYCLI_VERBOSE]