.TH "GCLOUD_ALPHA_TRANSFER_APPLIANCES_ORDERS_UPDATE" 1



.SH "NAME"
.HP
gcloud alpha transfer appliances orders update \- update an order for a transfer appliance



.SH "SYNOPSIS"
.HP
\f5gcloud alpha transfer appliances orders update\fR \fIORDER\fR [\fB\-\-region\fR=\fIREGION\fR] [\fB\-\-submit\fR] [\fB\-\-cmek\fR=\fICMEK\fR\ \fB\-\-display\-name\fR=\fIDISPLAY_NAME\fR\ \fB\-\-model\fR=\fIMODEL\fR\ \fB\-\-offline\-export\fR=[\fImanifest\fR=\fIMANIFEST\fR],[\fIsource\fR=\fISOURCE\fR]\ \fB\-\-offline\-import\fR=\fIOFFLINE_IMPORT\fR\ \fB\-\-online\-import\fR=\fIONLINE_IMPORT\fR] [\fB\-\-address\fR=[\fIadministrative\-area\fR=\fIADMINISTRATIVE\-AREA\fR],[\fIlines\fR=\fILINES\fR],[\fIlocality\fR=\fILOCALITY\fR],[\fIpostal\-code\fR=\fIPOSTAL\-CODE\fR]\ \fB\-\-delivery\-notes\fR=\fIDELIVERY_NOTES\fR\ \fB\-\-order\-contact\fR=[\fIbusiness\fR=\fIBUSINESS\fR],[\fIemails\fR=\fIEMAILS\fR],[\fIname\fR=\fINAME\fR],[\fIphone\fR=\fIPHONE\fR]\ \fB\-\-shipping\-contact\fR=[\fIbusiness\fR=\fIBUSINESS\fR],[\fIemails\fR=\fIEMAILS\fR],[\fIname\fR=\fINAME\fR],[\fIphone\fR=\fIPHONE\fR]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR \fBgcloud alpha transfer appliances orders update\fR facilitates
the update of Transfer Appliance Orders.



.SH "EXAMPLES"

To update the shipping contact of an appliance called \f5my\-appliance\fR:

.RS 2m
$ gcloud alpha transfer appliances orders update my\-appliance \e
    \-\-shipping\-contact="name=Jane \e
Doe,emails=[jane@example.com],phone=12345678910"
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Order resource \- The order to update. This represents a Cloud resource. (NOTE)
Some attributes are not given arguments in this group but can be set in other
ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5order\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

To set the \f5region\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5order\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-region\fR on the command line.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIORDER\fR

ID of the order or fully qualified identifier for the order.

To set the \f5order\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5order\fR on the command line.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-region\fR=\fIREGION\fR

The location affiliated with the appliance order to update. \fIREGION\fR must be
one of: \fBus\-central1\fR, \fBeurope\-west1\fR, \fBasia\-southeast1\fR.

.TP 2m
\fB\-\-submit\fR

Submits an order that is in draft.


.RE
.sp

.SH "APPLIANCE FLAGS"

.RS 2m
.TP 2m
\fB\-\-cmek\fR=\fICMEK\fR

Customer\-managed key which will add additional layer of security. By default
data is encrypted with a Google\-managed key.

.TP 2m
\fB\-\-display\-name\fR=\fIDISPLAY_NAME\fR

A mutable, user\-settable name for both the appliance and the order.

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

Model of the appliance to order. \fIMODEL\fR must be one of:
\fBTA40_RACKABLE\fR, \fBTA40_STANDALONE\fR, \fBTA300_RACKABLE\fR,
\fBTA300_STANDALONE\fR, \fBTA7\fR, \fBEA_STORAGE_7\fR, \fBEA_GPU_T4\fR.

.TP 2m
\fB\-\-offline\-export\fR=[\fImanifest\fR=\fIMANIFEST\fR],[\fIsource\fR=\fISOURCE\fR]

Configuration for an offline export transfer, where data is downloaded onto the
appliance at Google and copied from the appliance at the customer site.

.RS 2m
.TP 2m
\fBsource\fR
The Cloud Storage bucket or folder where the data is located, in the form of
\f5gs://my\-bucket/path/to/folder/\fR.

.TP 2m
\fBmanifest\fR
Specifies the path to the manifest in Cloud Storage. An example path is
\f5gs://bucket_name/path/manifest.csv\fR. The paths in the manifest file are
relative to bucketname. For example, to export \f5SOURCE_PATH/object1.pdf\fR,
manifest will have \f5object1.pdf\fR in the first column, followed by object
version (optional). For more information see
https://cloud.google.com/storage\-transfer/docs/manifest#object_storage_transfers.

.RE
.sp
.TP 2m
\fB\-\-offline\-import\fR=\fIOFFLINE_IMPORT\fR

Destination for a offline import, where data is loaded onto the appliance at the
customer site and ingested at Google. Should be in the form of
\f5gs://my\-bucket/path/to/folder/\fR.

.TP 2m
\fB\-\-online\-import\fR=\fIONLINE_IMPORT\fR

Destination for a online import, where data is loaded onto the appliance and
automatically transferred to Cloud Storage whenever it has an internet
connection. Should be in the form of \f5gs://my\-bucket/path/to/folder/\fR.


.RE
.sp

.SH "DELIVERY FLAGS"

.RS 2m
.TP 2m
\fB\-\-address\fR=[\fIadministrative\-area\fR=\fIADMINISTRATIVE\-AREA\fR],[\fIlines\fR=\fILINES\fR],[\fIlocality\fR=\fILOCALITY\fR],[\fIpostal\-code\fR=\fIPOSTAL\-CODE\fR]

Address where the appliance will be shipped. All fields (or list items) have a
maximum of 80 characters. For more information see
https://support.google.com/business/answer/6397478.

.RS 2m
.TP 2m
\fBlines\fR
Line of the postal address that doesn't fit in the other fields. For most
countries/regions, the first line will include a street number and street name.
You can have up to 5 address lines.

.TP 2m
\fBlocality\fR
Generally refers to the city/town portion of the address.

.TP 2m
\fBadministrative_area\fR
The state or province where the business is located. Enter the full name (e.g.
"California"), common postal abbreviation (e.g. "CA"), or subdivision (ISO
3166\-2) code (e.g. "US\-CA").

.TP 2m
\fBpostal_code\fR
The postal code of the address.

.RE
.sp
.TP 2m
\fB\-\-delivery\-notes\fR=\fIDELIVERY_NOTES\fR

Add any additional details about your order, such as site details and a
preference date when the appliance should be delivered.

.TP 2m
\fB\-\-order\-contact\fR=[\fIbusiness\fR=\fIBUSINESS\fR],[\fIemails\fR=\fIEMAILS\fR],[\fIname\fR=\fINAME\fR],[\fIphone\fR=\fIPHONE\fR]

.RS 2m
.TP 2m
\fBbusiness\fR
Name of the business, if applicable.

.TP 2m
\fBname\fR
Name of the primary contact.

.TP 2m
\fBphone\fR
The phone number of the primary contact. Should be given in E.164 format
consisting of the country calling code (1 to 3 digits) and the subscriber
number, with no additional spaces or formatting, e.g. \f515552220123\fR.

.TP 2m
\fBemails\fR
The email of the primary contact along with any additional email addresses to
include with all correspondence.

.RE
.sp
.TP 2m
\fB\-\-shipping\-contact\fR=[\fIbusiness\fR=\fIBUSINESS\fR],[\fIemails\fR=\fIEMAILS\fR],[\fIname\fR=\fINAME\fR],[\fIphone\fR=\fIPHONE\fR]

.RS 2m
.TP 2m
\fBbusiness\fR
Name of the business, if applicable.

.TP 2m
\fBname\fR
Name of the primary contact.

.TP 2m
\fBphone\fR
The phone number of the primary contact. Should be given in E.164 format
consisting of the country calling code (1 to 3 digits) and the subscriber
number, with no additional spaces or formatting, e.g. \f515552220123\fR.

.TP 2m
\fBemails\fR
The email of the primary contact along with any additional email addresses to
include with all correspondence.


.RE
.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"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist.