gcp_compute_backend_service_facts – Gather facts for GCP BackendService¶
New in version 2.7.
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
-
/ required
|
|
The type of credential used.
|
filters
-
|
A list of filter value pairs. Available filters are listed here https://cloud.google.com/sdk/gcloud/reference/topic/filters. Each additional filter in the list will act be added as an AND condition (filter1 and filter2)
|
|
project
-
|
Default: null
|
The Google Cloud Platform project to use.
|
scopes
-
|
Array of scopes to be used.
|
|
service_account_email
-
|
An optional service account email address if machineaccount is selected and the user does not wish to use the default email.
|
|
service_account_file
-
|
The path of a Service Account JSON file if serviceaccount is selected as type.
|
Notes¶
Note
- For authentication, you can set service_account_file using the
GCP_SERVICE_ACCOUNT_FILE
env variable. - For authentication, you can set service_account_email using the
GCP_SERVICE_ACCOUNT_EMAIL
env variable. - For authentication, you can set auth_kind using the
GCP_AUTH_KIND
env variable. - For authentication, you can set scopes using the
GCP_SCOPES
env 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: a backend service facts
gcp_compute_backend_service_facts:
filters:
- name = test_object
project: test_project
auth_kind: service_account
service_account_file: "/tmp/auth.pem"
Return Values¶
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description | |||
---|---|---|---|---|---|
items
complex
|
always |
List of items
|
|||
affinity_cookie_ttl_sec
integer
|
success |
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day.
When the load balancing scheme is INTERNAL, this field is not used.
|
|||
backends
complex
|
success |
The list of backends that serve this BackendService.
|
|||
balancing_mode
string
|
success |
Specifies the balancing mode for this backend.
For global HTTP(S) or TCP/SSL load balancing, the default is UTILIZATION. Valid values are UTILIZATION, RATE (for HTTP(S)) and CONNECTION (for TCP/SSL).
This cannot be used for internal load balancing.
|
|||
capacity_scaler
string
|
success |
A multiplier applied to the group's maximum servicing capacity (based on UTILIZATION, RATE or CONNECTION).
Default value is 1, which means the group will serve up to 100% of its configured capacity (depending on balancingMode). A setting of 0 means the group is completely drained, offering 0% of its available Capacity. Valid range is [0.0,1.0].
This cannot be used for internal load balancing.
|
|||
description
string
|
success |
An optional description of this resource.
Provide this property when you create the resource.
|
|||
group
dictionary
|
success |
This instance group defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself.
No two backends in a backend service are allowed to use same Instance Group resource.
When the BackendService has load balancing scheme INTERNAL, the instance group must be in a zone within the same region as the BackendService.
|
|||
max_connections
integer
|
success |
The max number of simultaneous connections for the group. Can be used with either CONNECTION or UTILIZATION balancing modes.
For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.
This cannot be used for internal load balancing.
|
|||
max_connections_per_instance
integer
|
success |
The max number of simultaneous connections that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes.
For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.
This cannot be used for internal load balancing.
|
|||
max_rate
integer
|
success |
The max requests per second (RPS) of the group.
Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. For RATE mode, either maxRate or maxRatePerInstance must be set.
This cannot be used for internal load balancing.
|
|||
max_rate_per_instance
string
|
success |
The max requests per second (RPS) that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set.
This cannot be used for internal load balancing.
|
|||
max_utilization
string
|
success |
Used when balancingMode is UTILIZATION. This ratio defines the CPU utilization target for the group. The default is 0.8. Valid range is [0.0, 1.0].
This cannot be used for internal load balancing.
|
|||
cdn_policy
complex
|
success |
Cloud CDN configuration for this BackendService.
|
|||
cache_key_policy
complex
|
success |
The CacheKeyPolicy for this CdnPolicy.
|
|||
include_host
boolean
|
success |
If true requests to different hosts will be cached separately.
|
|||
include_protocol
boolean
|
success |
If true, http and https requests will be cached separately.
|
|||
include_query_string
boolean
|
success |
If true, include query string parameters in the cache key according to query_string_whitelist and query_string_blacklist. If neither is set, the entire query string will be included.
If false, the query string will be excluded from the cache key entirely.
|
|||
query_string_blacklist
list
|
success |
Names of query string parameters to exclude in cache keys.
All other parameters will be included. Either specify query_string_whitelist or query_string_blacklist, not both.
'&' and '=' will be percent encoded and not treated as delimiters.
|
|||
query_string_whitelist
list
|
success |
Names of query string parameters to include in cache keys.
All other parameters will be excluded. Either specify query_string_whitelist or query_string_blacklist, not both.
'&' and '=' will be percent encoded and not treated as delimiters.
|
|||
connection_draining
complex
|
success |
Settings for connection draining.
|
|||
draining_timeout_sec
integer
|
success |
Time for which instance will be drained (not accept new connections, but still work to finish started).
|
|||
creation_timestamp
string
|
success |
Creation timestamp in RFC3339 text format.
|
|||
description
string
|
success |
An optional description of this resource.
|
|||
enable_cdn
boolean
|
success |
If true, enable Cloud CDN for this BackendService.
When the load balancing scheme is INTERNAL, this field is not used.
|
|||
health_checks
list
|
success |
The list of URLs to the HttpHealthCheck or HttpsHealthCheck resource for health checking this BackendService. Currently at most one health check can be specified, and a health check is required.
For internal load balancing, a URL to a HealthCheck resource must be specified instead.
|
|||
id
integer
|
success |
The unique identifier for the resource.
|
|||
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.
|
|||
port_name
string
|
success |
Name of backend port. The same name should appear in the instance groups referenced by this service. Required when the load balancing scheme is EXTERNAL.
When the load balancing scheme is INTERNAL, this field is not used.
|
|||
protocol
string
|
success |
The protocol this BackendService uses to communicate with backends.
Possible values are HTTP, HTTPS, TCP, and SSL. The default is HTTP.
For internal load balancing, the possible values are TCP and UDP, and the default is TCP.
|
|||
region
string
|
success |
The region where the regional backend service resides.
This field is not applicable to global backend services.
|
|||
session_affinity
string
|
success |
Type of session affinity to use. The default is NONE.
When the load balancing scheme is EXTERNAL, can be NONE, CLIENT_IP, or GENERATED_COOKIE.
When the load balancing scheme is INTERNAL, can be NONE, CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO.
When the protocol is UDP, this field is not used.
|
|||
timeout_sec
integer
|
success |
How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
|
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.