pub struct SSLPolicyResult {
pub creation_timestamp: Output<String>,
pub custom_features: Output<Option<Vec<String>>>,
pub description: Output<Option<String>>,
pub enabled_features: Output<Vec<String>>,
pub fingerprint: Output<String>,
pub min_tls_version: Output<Option<String>>,
pub name: Output<String>,
pub profile: Output<Option<String>>,
pub project: Output<String>,
pub self_link: Output<String>,
}Fields§
§creation_timestamp: Output<String>Creation timestamp in RFC3339 text format.
custom_features: Output<Option<Vec<String>>>Profile specifies the set of SSL features that can be used by the
load balancer when negotiating SSL with clients. This can be one of
COMPATIBLE, MODERN, RESTRICTED, or CUSTOM. If using CUSTOM,
the set of SSL features to enable must be specified in the
customFeatures field.
See the official documentation
for which ciphers are available to use. Note: this argument
must be present when using the CUSTOM profile. This argument
must not be present when using any other profile.
description: Output<Option<String>>An optional description of this resource.
enabled_features: Output<Vec<String>>The list of features enabled in the SSL policy.
fingerprint: Output<String>Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
min_tls_version: Output<Option<String>>The minimum version of SSL protocol that can be used by the clients
to establish a connection with the load balancer.
Default value is TLS_1_0.
Possible values are: TLS_1_0, TLS_1_1, TLS_1_2.
name: Output<String>Name of the resource. Provided by the client when the resource is
created. The name must be 1-63 characters long, and comply with
RFC1035. Specifically, the name must be 1-63 characters long and match
the regular expression a-z? which means the
first character must be a lowercase letter, and all following
characters must be a dash, lowercase letter, or digit, except the last
character, which cannot be a dash.
profile: Output<Option<String>>Profile specifies the set of SSL features that can be used by the
load balancer when negotiating SSL with clients. If using CUSTOM,
the set of SSL features to enable must be specified in the
customFeatures field.
See the official documentation
for information on what cipher suites each profile provides. If
CUSTOM is used, the custom_features attribute must be set.
Default value is COMPATIBLE.
Possible values are: COMPATIBLE, MODERN, RESTRICTED, CUSTOM.
project: Output<String>The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
self_link: Output<String>The URI of the created resource.