Certificate
Create a new CertificateAuthority in a given Project and Location. Auto-naming is currently not supported for this resource.
Properties
URLs for accessing content published by this CA, such as the CA certificate and CRLs.
A structured description of this CertificateAuthority's CA certificate and its issuers. Ordered as self-to-root.
Required. It must be unique within a location and match the regular expression [a-zA-Z0-9_-]{1,63}
Immutable. The config used to create a self-signed X.509 certificate or CSR.
The time at which this CertificateAuthority was created.
The time at which this CertificateAuthority was soft deleted, if it is in the DELETED state.
The time at which this CertificateAuthority will be permanently purged, if it is in the DELETED state.
Immutable. The name of a Cloud Storage bucket where this CertificateAuthority will publish content, such as the CA certificate and CRLs. This must be a bucket name, without any prefixes (such as gs://) or suffixes (such as .googleapis.com). For example, to use a bucket named my-bucket, you would simply specify my-bucket. If not specified, a managed bucket will be created.
Immutable. Used when issuing certificates for this CertificateAuthority. If this CertificateAuthority is a self-signed CertificateAuthority, this key is also used to sign the self-signed CA certificate. Otherwise, it is used to sign a CSR.
This CertificateAuthority's certificate chain, including the current CertificateAuthority's certificate. Ordered such that the root issuer is the final element (consistent with RFC 5246). For a self-signed CA, this will only list the current CertificateAuthority's certificate.
Optional. An ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Optional. If this is a subordinate CertificateAuthority, this field will be set with the subordinate configuration, which describes its issuers. This may be updated, but this CertificateAuthority must continue to validate.
The time at which this CertificateAuthority was last updated.