gcp_compute_ssl_policy – Creates a GCP SslPolicy
New in version 2.7.
Synopsis
- Represents a SSL policy. SSL policies give you the ability to control the features of SSL that your SSL proxy or HTTPS load balancer negotiates.
 
Requirements
The below requirements are needed on the host that executes this module.
- python >= 2.6
 - requests >= 2.18.4
 - google-auth >= 1.3.0
 
Parameters
| Parameter | Choices/Defaults | Comments | 
|---|---|---|
|   auth_kind    string / required    |   
  |    The type of credential used.   |  
|   custom_features    list    |    A list of features enabled when the selected profile is CUSTOM. The method returns the set of features that can be specified in this list. This field must be empty if the profile is not CUSTOM.   |  |
|   description    string    |    An optional description of this resource.   |  |
|   env_type    string    |    Specifies which Ansible environment you're running this module within.  This should not be set unless you know what you're doing.  This only alters the User Agent string for any API requests.   |  |
|   min_tls_version    string    |    The minimum version of SSL protocol that can be used by the clients to establish a connection with the load balancer. This can be one of `TLS_1_0`, `TLS_1_1`, `TLS_1_2`.  Some valid choices include: "TLS_1_0", "TLS_1_1", "TLS_1_2"   |  |
|   name    string / required    |    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]([-a-z0-9]*[a-z0-9])?` 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    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.  Some valid choices include: "COMPATIBLE", "MODERN", "RESTRICTED", "CUSTOM"   |  |
|   project    string    |    The Google Cloud Platform project to use.   |  |
|   scopes    list    |    Array of scopes to be used.   |  |
|   service_account_contents    jsonarg    |    The contents of a Service Account JSON file, either in a dictionary or as a JSON string that represents it.   |  |
|   service_account_email    string    |    An optional service account email address if machineaccount is selected and the user does not wish to use the default email.   |  |
|   service_account_file    path    |    The path of a Service Account JSON file if serviceaccount is selected as type.   |  |
|   state    string    |   
  |    Whether the given object should exist in GCP   |  
Notes
Note
- API Reference: https://cloud.google.com/compute/docs/reference/rest/v1/sslPolicies
 - Using SSL Policies: https://cloud.google.com/compute/docs/load-balancing/ssl-policies
 - for authentication, you can set service_account_file using the c(gcp_service_account_file) env variable.
 - for authentication, you can set service_account_contents using the c(GCP_SERVICE_ACCOUNT_CONTENTS) env variable.
 - For authentication, you can set service_account_email using the 
GCP_SERVICE_ACCOUNT_EMAILenv variable. - For authentication, you can set auth_kind using the 
GCP_AUTH_KINDenv variable. - For authentication, you can set scopes using the 
GCP_SCOPESenv variable. - Environment variables values will only be used if the playbook values are not set.
 - The service_account_email and service_account_file options are mutually exclusive.
 
Examples
- name: create a SSL policy
  gcp_compute_ssl_policy:
    name: test_object
    profile: CUSTOM
    min_tls_version: TLS_1_2
    custom_features:
    - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    project: test_project
    auth_kind: serviceaccount
    service_account_file: "/tmp/auth.pem"
    state: present
   Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Returned | Description | |
|---|---|---|---|
|   creationTimestamp    string    |  success |   Creation timestamp in RFC3339 text format.   |  |
|   customFeatures    list    |  success |   A list of features enabled when the selected profile is CUSTOM. The method returns the set of features that can be specified in this list. This field must be empty if the profile is not CUSTOM.   |  |
|   description    string    |  success |   An optional description of this resource.   |  |
|   enabledFeatures    list    |  success |   The list of features enabled in the SSL policy.   |  |
|   fingerprint    string    |  success |   Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.   |  |
|   id    integer    |  success |   The unique identifier for the resource.   |  |
|   minTlsVersion    string    |  success |   The minimum version of SSL protocol that can be used by the clients to establish a connection with the load balancer. This can be one of `TLS_1_0`, `TLS_1_1`, `TLS_1_2`.   |  |
|   name    string    |  success |   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]([-a-z0-9]*[a-z0-9])?` 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    string    |  success |   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.   |  |
|   warnings    complex    |  success |   If potential misconfigurations are detected for this SSL policy, this field will be populated with warning messages.   |  |
|   code    string    |  success |   A warning code, if applicable.   |  |
|   message    string    |  success |   A human-readable description of the warning code.   |  |
Status
- This module is not guaranteed to have a backwards compatible interface. [preview]
 - This module is maintained by the Ansible Community. [community]
 
Authors
- Google Inc. (@googlecloudplatform)
 
Hint
If you notice any issues in this documentation, you can edit this document to improve it.
    © 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
    https://docs.ansible.com/ansible/2.9/modules/gcp_compute_ssl_policy_module.html