File: //snap/google-cloud-cli/current/help/man/man1/gcloud_logging_views_set-iam-policy.1
.TH "GCLOUD_LOGGING_VIEWS_SET\-IAM\-POLICY" 1
.SH "NAME"
.HP
gcloud logging views set\-iam\-policy \- set IAM policy for a view
.SH "SYNOPSIS"
.HP
\f5gcloud logging views set\-iam\-policy\fR \fIVIEW_ID\fR \fIPOLICY_FILE\fR \fB\-\-bucket\fR=\fIBUCKET\fR \fB\-\-location\fR=\fILOCATION\fR [\fB\-\-billing\-account\fR=\fIBILLING_ACCOUNT_ID\fR\ |\ \fB\-\-folder\fR=\fIFOLDER_ID\fR\ |\ \fB\-\-organization\fR=\fIORGANIZATION_ID\fR\ |\ \fB\-\-project\fR=\fIPROJECT_ID\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]
.SH "DESCRIPTION"
Set an IAM policy for a view.
.SH "EXAMPLES"
To set the IAM policy using a json file 'my_policy.json' for the view
\f5my\-view\fR in \f5my\-bucket\fR in the \f5global\fR location, run:
.RS 2m
$ gcloud logging views set\-iam\-policy my\-view \e
/path/to/my_policy.json \-\-bucket=my\-bucket \-\-location=global
.RE
.SH "POSITIONAL ARGUMENTS"
.RS 2m
.TP 2m
\fIVIEW_ID\fR
ID of the view to set IAM policy.
.TP 2m
\fIPOLICY_FILE\fR
Path to a local JSON or YAML formatted file containing a valid policy.
The output of the \f5get\-iam\-policy\fR command is a valid file, as is any JSON
or YAML file conforming to the structure of a Policy
(https://cloud.google.com/iam/reference/rest/v1/Policy).
.RE
.sp
.SH "REQUIRED FLAGS"
.RS 2m
.TP 2m
\fB\-\-bucket\fR=\fIBUCKET\fR
ID of the bucket that contains the view.
.TP 2m
\fB\-\-location\fR=\fILOCATION\fR
Location of the bucket that contains the view.
.RE
.sp
.SH "OPTIONAL FLAGS"
.RS 2m
.TP 2m
At most one of these can be specified:
.RS 2m
.TP 2m
\fB\-\-billing\-account\fR=\fIBILLING_ACCOUNT_ID\fR
Billing account of the view to set IAM policy.
.TP 2m
\fB\-\-folder\fR=\fIFOLDER_ID\fR
Folder of the view to set IAM policy.
.TP 2m
\fB\-\-organization\fR=\fIORGANIZATION_ID\fR
Organization of the view to set IAM policy.
.TP 2m
\fB\-\-project\fR=\fIPROJECT_ID\fR
Project of the view to set IAM policy.
The Google Cloud project ID to use for this invocation. If omitted, then the
current project is assumed; the current project can be listed using \f5gcloud
config list \-\-format='text(core.project)'\fR and can be set using \f5gcloud
config set project PROJECTID\fR.
\f5\-\-project\fR and its fallback \f5core/project\fR property play two roles in
the invocation. It specifies the project of the resource to operate on. It also
specifies the project for API enablement check, quota, and billing. To specify a
different project for quota and billing, use \f5\-\-billing\-project\fR or
\f5billing/quota_project\fR property.
.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.