Metaplay Docs

Appearance

metaplay debug image-registry ENVIRONMENT [flags]

Report how the CLI reaches an environment's images

metaplay debug image-registry ENVIRONMENT [flags] ​

Report both paths the CLI can take to an environment's image repository, what each of them answered, and which one a push or deploy would take.

A stack issues a credential for an environment's images from its image registry credentials endpoint. A stack older than that endpoint does not serve it, and the CLI then reaches the repository the environment's description names, in ECR, with AWS credentials the stack issues. Which path a command took is otherwise invisible: it shows only whatever failed afterwards.

Both paths are always asked. A path that fails is reported rather than stopping the command, so it exits successfully whatever they answered. The credential's expiry is shown where it states one. The password is never shown.

Needs no deployed game server and no access to its cluster: it talks to the stack's API, and to ECR for the older path.

Expected arguments:

  • ENVIRONMENT (optional) -- Target environment name or id, eg, 'lovely-wombats-build-nimbly'.

Related commands:

  • 'metaplay image push ...' pushes an image to the environment's repository.
  • 'metaplay image list ...' lists the images in it.

Examples ​

sh
# Report how the CLI reaches the images of environment 'nimbly'.
metaplay debug image-registry nimbly
# The same report as JSON.
metaplay debug image-registry nimbly --format=json

Flags ​

  • --format <string>: Output format. Valid values are 'text' or 'json' (default: text)

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]