.TH "GCLOUD_AI_MODEL\-GARDEN_MODELS_LIST\-DEPLOYMENT\-CONFIG" 1



.SH "NAME"
.HP
gcloud ai model\-garden models list\-deployment\-config \- list the machine specifications supported by and verified for a model in Model Garden



.SH "SYNOPSIS"
.HP
\f5gcloud ai model\-garden models list\-deployment\-config\fR \fB\-\-model\fR=\fIMODEL\fR [\fB\-\-hugging\-face\-access\-token\fR=\fIHUGGING_FACE_ACCESS_TOKEN\fR] [\fB\-\-filter\fR=\fIEXPRESSION\fR] [\fB\-\-sort\-by\fR=[\fIFIELD\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "EXAMPLES"

To list the supported machine specifications for
\f5google/gemma2@gemma\-2\-9b\fR, run:

.RS 2m
$ gcloud ai model\-garden models list\-deployment\-config \e
    \-\-model=google/gemma2@gemma\-2\-9b
.RE

To list the supported machine specifications for a Hugging Face model
\f5meta\-llama/Meta\-Llama\-3\-8B\fR, run:

.RS 2m
$ gcloud ai model\-garden models list\-deployment\-config \e
    \-\-model=meta\-llama/Meta\-Llama\-3\-8B
.RE



.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-model\fR=\fIMODEL\fR

The model to be deployed. If it is a Model Garden model, it should be in the
format of \f5{publisher_name}/{model_name}@{model_version_name}, e.g.
\fRgoogle/gemma2@gemma\-2\-2b\f5. If it is a Hugging Face model, it should be in
the convention of Hugging Face models, e.g.
\fRmeta\-llama/Meta\-Llama\-3\-8B\f5.


\fR
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-hugging\-face\-access\-token\fR=\fIHUGGING_FACE_ACCESS_TOKEN\fR

The access token from Hugging Face needed to read the model artifacts of gated
models in order to generate the deployment configs. It is only needed when the
Hugging Face model to deploy is gated and not verified by Model Garden. You can
use the \f5gcloud ai alpha/beta model\-garden models list\fR command to find out
which ones are verified by Model Garden.


.RE
.sp

.SH "LIST COMMAND FLAGS"

.RS 2m
.TP 2m
\fB\-\-filter\fR=\fIEXPRESSION\fR

Apply a Boolean filter \fIEXPRESSION\fR to each resource item to be listed. If
the expression evaluates \f5True\fR, then that item is listed. For more details
and examples of filter expressions, run $ gcloud topic filters. This flag
interacts with other flags that are applied in this order: \fB\-\-flatten\fR,
\fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.

.TP 2m
\fB\-\-sort\-by\fR=[\fIFIELD\fR,...]

Comma\-separated list of resource field key names to sort by. The default order
is ascending. Prefix a field with ``~'' for descending order on that field. This
flag interacts with other flags that are applied in this order:
\fB\-\-flatten\fR, \fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.


.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha ai model\-garden models list\-deployment\-config
.RE

.RS 2m
$ gcloud beta ai model\-garden models list\-deployment\-config
.RE