gcloud privateca templates set-iam-policy - set the IAM policy for a certificate template
gcloud privateca templates set-iam-policy (CERTIFICATE_TEMPLATE : --location=LOCATION) POLICY_FILE [GCLOUD_WIDE_FLAG ...]
Sets the IAM policy for the given certificate template as defined in a JSON or YAML file.
See https://cloud.google.com/iam/docs/managing-policies for details of the policy file format and contents.
The following command will read an IAM policy defined in a JSON file 'policy.json' and set it for the certificate template 'my-template' with the location 'us-west1':
$ gcloud privateca templates set-iam-policy my-template \ --location=us-west1 policy.json
- Certificate Template resource - The certificate template for which to update
the IAM policy. 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 project attribute:
- —
provide the argument certificate_template on the command line with a fully specified name;
- —
set the property core/project;
- —
provide the argument --project on the command line.
This must be specified.
- CERTIFICATE_TEMPLATE
ID of the Certificate Template or fully qualified identifier for the Certificate Template. To set the certificate_template attribute:
provide the argument certificate_template on the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
- --location=LOCATION
The location of the Certificate Template. To set the location attribute:
provide the argument certificate_template on the command line with a fully specified name;
provide the argument --location on the command line;
set the property privateca/location.
- POLICY_FILE
Path to a local JSON or YAML formatted file containing a valid policy.
The output of the get-iam-policy 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.
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 $ gcloud help for details.
This command uses the privateca/v1 API. The full documentation for this API can be found at: https://cloud.google.com/