HEX

File: //snap/google-cloud-cli/current/help/man/man1/gcloud_looker_instances_update.1

.TH "GCLOUD_LOOKER_INSTANCES_UPDATE" 1

.SH "NAME"
.HP
gcloud looker instances update \- update a Looker instance

.SH "SYNOPSIS"
.HP
\f5gcloud looker instances update\fR (\fIINSTANCE\fR\ :\ \fB\-\-region\fR=\fIREGION\fR) [\fB\-\-allowed\-email\-domains\fR=[\fIALLOWED_EMAIL_DOMAINS\fR,...]] [\fB\-\-async\fR] [\fB\-\-class\-type\fR=\fICLASS_TYPE\fR] [\fB\-\-custom\-domain\fR=\fICUSTOM_DOMAIN\fR] [\fB\-\-linked\-lsp\-project\-number\fR=\fILINKED_LSP_PROJECT_NUMBER\fR] [\fB\-\-public\-ip\-enabled\fR] [\fB\-\-add\-developer\-users\fR=\fIADD_DEVELOPER_USERS\fR\ \fB\-\-add\-standard\-users\fR=\fIADD_STANDARD_USERS\fR\ \fB\-\-add\-viewer\-users\fR=\fIADD_VIEWER_USERS\fR] [\fB\-\-clear\-psc\-allowed\-vpcs\fR\ |\ \fB\-\-psc\-allowed\-vpcs\fR=[\fIPSC_ALLOWED_VPCS\fR,...]\ \fB\-\-clear\-psc\-service\-attachments\fR\ |\ \fB\-\-psc\-service\-attachment\fR=[\fIattachment\fR=\fIATTACHMENT\fR],[\fIdomain\fR=\fIDOMAIN\fR],[\fImultiple\-domains\fR=\fIMULTIPLE\-DOMAINS\fR]] [\fB\-\-deny\-maintenance\-period\-end\-date\fR=\fIDENY_MAINTENANCE_PERIOD_END_DATE\fR\ \fB\-\-deny\-maintenance\-period\-start\-date\fR=\fIDENY_MAINTENANCE_PERIOD_START_DATE\fR\ \fB\-\-deny\-maintenance\-period\-time\fR=\fIDENY_MAINTENANCE_PERIOD_TIME\fR] [\fB\-\-maintenance\-window\-day\fR=\fIMAINTENANCE_WINDOW_DAY\fR\ \fB\-\-maintenance\-window\-time\fR=\fIMAINTENANCE_WINDOW_TIME\fR] [\fB\-\-oauth\-client\-id\fR=\fIOAUTH_CLIENT_ID\fR\ \fB\-\-oauth\-client\-secret\fR=\fIOAUTH_CLIENT_SECRET\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]

.SH "DESCRIPTION"

Update the metadata and/or configuration parameters of a Looker instance.

This command can fail for the following reasons:
.RS 2m
.IP "\(bu" 2m
The instance specified does not exist.
.IP "\(bu" 2m
The active account does not have permission to update the given instance.
.RE
.sp

.SH "EXAMPLES"

To update the maintenance window to Sunday at 11:00 PM for a Looker instance
with the name \f5my\-looker\-instance\fR, run:

.RS 2m
$ gcloud looker instances update my\-looker\-instance \e
\-\-maintenance\-window\-day=sunday \e
\-\-maintenance\-window\-time='23:00' \-\-async
.RE

.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Instance resource \- Arguments and flags that specify the Looker instance you
want to update. The arguments in this group can be used to specify the
attributes of this 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 \f5instance\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

This must be specified.

.RS 2m
.TP 2m
\fIINSTANCE\fR

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

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

This positional argument must be specified if any of the other arguments in this
group are specified.

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

The name of the Looker region of the instance. Overrides the default
looker/region property value for this command invocation.

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

.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m

Email Domain Allowlist for Scheduled Content \- Define the email domains to
which your users can deliver Looker (Google Cloud core) content.

.RS 2m
.TP 2m
\fB\-\-allowed\-email\-domains\fR=[\fIALLOWED_EMAIL_DOMAINS\fR,...]

This specifies the entire allowed email domain list.

.RE
.sp
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.

.TP 2m
\fB\-\-class\-type\fR=\fICLASS_TYPE\fR

The class type of the Looker instance. \fICLASS_TYPE\fR must be one of:
\fBp1\fR, \fBr1\fR.

.TP 2m

Custom Domains \- Looker (Google Cloud core) lets you serve your application
through a custom domain. If you use a custom domain, Google will provide a
managed auto\-renewing SSL certificate for security.

DNS changes can take up to 24 hours to take effect. Your SSL certificate will
take several minutes to activate. Note that you must get the Type A DNS Record
from the Google Cloud Console and update with your domain registrar for your
custom domain to work properly.

.RS 2m
.TP 2m
\fB\-\-custom\-domain\fR=\fICUSTOM_DOMAIN\fR

Domain name wanted to serve the Looker instance.

.RE
.sp
.TP 2m
\fB\-\-linked\-lsp\-project\-number\fR=\fILINKED_LSP_PROJECT_NUMBER\fR

The Looker Studio Pro project number to be linked.

.TP 2m
\fB\-\-public\-ip\-enabled\fR

This specifies whether public IP is enabled on the Looker instance.

.TP 2m

User Allocations \- There are ten Standard and two Developer users included in
the cost of the product. You can allocate additional Standard, Viewer, and
Developer users for this instance. It is an optional step and can be modified
later.

With the Standard edition of Looker (Google Cloud core), you can provision up to
50 total users, distributed across Viewer, Standard, and Developer.

.RS 2m
.TP 2m
\fB\-\-add\-developer\-users\fR=\fIADD_DEVELOPER_USERS\fR

Number of additional Developer Users to allocate to the Looker Instance.

.TP 2m
\fB\-\-add\-standard\-users\fR=\fIADD_STANDARD_USERS\fR

Number of additional Standard Users to allocate to the Looker Instance.

.TP 2m
\fB\-\-add\-viewer\-users\fR=\fIADD_VIEWER_USERS\fR

Number of additional Viewer Users to allocate to the Looker Instance.

.RE
.sp
.TP 2m

Private Service Connect \- Private Service Connect allows the Looker Instance to
be reached via a private connection from inside a VPC network, and for the
Looker Instance to connect to managed services via private connections.

.RS 2m
.TP 2m

At most one of these can be specified:

.RS 2m
.TP 2m
\fB\-\-clear\-psc\-allowed\-vpcs\fR

Remove all service attachments from the PSC config of the instance.

.TP 2m
\fB\-\-psc\-allowed\-vpcs\fR=[\fIPSC_ALLOWED_VPCS\fR,...]

List of VPCs that are allowed ingress into the Looker instance.

.RE
.sp
.TP 2m

At most one of these can be specified:

.RS 2m
.TP 2m
\fB\-\-clear\-psc\-service\-attachments\fR

Remove all allowed VPCs from the PSC config of the instance.

.TP 2m
\fB\-\-psc\-service\-attachment\fR=[\fIattachment\fR=\fIATTACHMENT\fR],[\fIdomain\fR=\fIDOMAIN\fR],[\fImultiple\-domains\fR=\fIMULTIPLE\-DOMAINS\fR]

Service attachments representing egress connections for the Looker instance.
This flag can be repeated. (Example: \-\-psc\-service\-attachment
domain="mydomain.com",attachment="projects/my\-project/regions/us\-east1/serviceAttachments/sa"
\-\-psc\-service\-attachments
domain="mydomain2.com",attachment="projects/my\-project/regions/us\-east1/serviceAttachments/sa2")

You can also assign multiple domains to a single service attachment. (Example:
\-\-psc\-service\-attachment
multiple\-domains="mydomain.com;mydomain2.com",attachment="projects/my\-project/regions/us\-east1/serviceAttachments/sa")

.RE
.RE
.sp
.TP 2m

Deny Maintanence Period \- You must allow at least 48 hours of maintenance
availability in a 60\-day rolling window. Only contiguous availability windows
of at least two hours are considered. When setting a maintenance exclusion
please be aware that excluding application upgrades cannot exceed 60\-days and
excluding infrastructure upgrades cannot exceed 90\-days.

.RS 2m
.TP 2m
\fB\-\-deny\-maintenance\-period\-end\-date\fR=\fIDENY_MAINTENANCE_PERIOD_END_DATE\fR

End date of the deny maintenance period in format: YYYY\-MM\-DD