gcloud alpha certificate-manager trust-configs update Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha certificate-manager trust-configs update - update TrustConfig
- SYNOPSIS
gcloud alpha certificate-manager trust-configs update(TRUST_CONFIG:--location=LOCATION)[--add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,…]][--async][--description=DESCRIPTION][--trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS]][--update-labels=[KEY=VALUE,…]][--clear-allowlisted-certificates|--remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES,…]][--clear-labels|--remove-labels=[KEY,…]][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(ALPHA)Update a TrustConfig.- EXAMPLES
- To update a TrustConfig, run:
gcloudalphacertificate-managertrust-configsupdatemy-trust-config--description="updated description"--trust-store=trust-anchors=ta.pem,intermediate-cas="ica1.pem;ica2.pem"--update-labels=my-key1=my-updated-value1--remove-labels=my-key2 - POSITIONAL ARGUMENTS
- TrustConfig resource - Name of the TrustConfig to update. The arguments in thisgroup can be used to specify the attributes of this resource. (NOTE) Someattributes are not given arguments in this group but can be set in other ways.
To set the
projectattribute:- provide the argument
trust_configon the command line with a fullyspecified name; - provide the argument
--projecton the command line; - set the property
core/project.
This must be specified.
TRUST_CONFIG- ID of the trustConfig or fully qualified identifier for the trustConfig.
To set the
trust_configattribute:- provide the argument
trust_configon the command line.
This positional argument must be specified if any of the other arguments in thisgroup are specified.
- provide the argument
--location=LOCATION- Certificate Manager location.
To set the
locationattribute:- provide the argument
trust_configon the command line with a fullyspecified name; - provide the argument
--locationon the command line; - default value of location is [global].
- provide the argument
- provide the argument
- TrustConfig resource - Name of the TrustConfig to update. The arguments in thisgroup can be used to specify the attributes of this resource. (NOTE) Someattributes are not given arguments in this group but can be set in other ways.
- FLAGS
--add-allowlisted-certificates=[ADD_ALLOWLISTED_CERTIFICATES,…]- Add allowlisted PEM-encoded certificates. Certificates should be provided infiles. For multiple file names, separate them by a comma (','). One file cancontain multiple certificates.
Examples:
Singlefile:--add-allowlisted-certificates=ac.pemMultiplefiles:--add-allowlisted-certificates=ac1.pem,ac2.pem --async- Return immediately, without waiting for the operation in progress to complete.
--description=DESCRIPTION- Human-readable description of the resource.
--trust-store=[intermediate-cas=INTERMEDIATE-CAS],[trust-anchors=TRUST-ANCHORS]- Trust Store with the given trust anchor and intermediate CA PEM-encodedcertificates. Certificates should be provided in files. For multiple file names,separate them by a semicolon (';') and quote them ('"'). One file can containmultiple certificates. Intermediate CAs are optional.
Examples:
Singlefiles:--trust-storetrust-anchors=ta.pem,intermediate-cas=ica.pem
NointermediateCAs:--trust-storetrust-anchors=ta.pemMultiplefiles:--trust-storetrust-anchors="ta1.pem;ta2.pem",intermediate-cas="ica1.pem;ica2.pem"
--update-labels=[KEY=VALUE,…]- List of label KEY=VALUE pairs to update. If a label exists, its value ismodified. Otherwise, a new label is created.
Keys must start with a lowercase character and contain only hyphens(
-), underscores (_), lowercase characters, andnumbers. Values must contain only hyphens (-), underscores(_), lowercase characters, and numbers. - At most one of these can be specified:
--clear-allowlisted-certificates- Clear all allowlisted certificates.
--remove-allowlisted-certificates=[REMOVE_ALLOWLISTED_CERTIFICATES,…]- Remove allowlisted PEM-encoded certificates. Certificates should be provided infiles. For multiple file names, separate them by a comma (','). One file cancontain multiple certificates.
Examples:
Singlefile:--remove-allowlisted-certificates=ac.pemMultiplefiles:--remove-allowlisted-certificates=ac1.pem,ac2.pem
- At most one of these can be specified:
--clear-labels- Remove all labels. If
--update-labelsis also specified then--clear-labelsis applied first.For example, to remove all labels:
gcloudalphacertificate-managertrust-configsupdate--clear-labelsTo remove all existing labels and create two new labels,
andfoo:bazgcloudalphacertificate-managertrust-configsupdate--clear-labels--update-labelsfoo=bar,baz=qux --remove-labels=[KEY,…]- List of label keys to remove. If a label does not exist it is silently ignored.If
--update-labelsis also specified then--update-labelsis applied first.
- 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
$gcloud helpfor details. - API REFERENCE
- This command uses the
certificatemanager/v1API. The fulldocumentation for this API can be found at:https://cloud.google.com/certificate-manager - NOTES
- This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist. These variants are also available:
gcloudcertificate-managertrust-configsupdategcloudbetacertificate-managertrust-configsupdate
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-22 UTC.