stephrobert.scaleway.lb_route_info module – Gather information about Scaleway Load Balancer routes
Note
This module is part of the stephrobert.scaleway collection (version 0.7.0).
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install stephrobert.scaleway.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: stephrobert.scaleway.lb_route_info.
New in stephrobert.scaleway 0.1.0
Synopsis
Retrieve information about an existing route, specified by its route ID. Its full details, origin frontend, target backend and match condition, are returned in the response object.
List all routes for a given frontend. The response is an array of routes, each one with a specified backend to direct to if a certain condition is matched (based on the value of the SNI field or HTTP Host header).
Requirements
The below requirements are needed on the host that executes this module.
scaleway >= 2.9.0
Parameters
Parameter |
Comments |
|---|---|
Scaleway API access key. |
|
Allow the API endpoint to be reached without verifying its TLS certificate. Falls back to the Scaleway configuration file, then to Choices:
|
|
Seconds allowed for a single API call, connection and read. Without a limit a silent connection would hang the module forever: the Scaleway SDK issues its requests with no timeout at all. This bounds a single call, not a whole wait. Modules that can wait for a state bound the overall wait separately. Default: |
|
URL of the Scaleway API endpoint. Point it at a local emulator to exercise a playbook without credentials. Falls back to the Scaleway configuration file, then to |
|
Path to the Scaleway configuration file. |
|
Frontend ID to filter for, only Routes from this Frontend will be returned. |
|
Sort order of routes in the response. Choices:
|
|
Default Organization ID used when an operation does not name one. |
|
Name of the profile to read in the Scaleway configuration file. |
|
Default Project ID used when an operation does not name one. |
|
Route ID. |
|
Scaleway API secret key. |
|
Value of the User-Agent header sent to the API. |
|
The zone you want to target Choices:
|
Attributes
Attribute |
Support |
Description |
|---|---|---|
Support: full |
This module only reads, so check mode changes nothing about how it runs. |
|
Support: none |
This module changes nothing, so it has no difference to report. |
Notes
Note
Every option can be set from its environment variable, respectively
SCW_PROFILE,SCW_CONFIG_PATH,SCW_ACCESS_KEY,SCW_SECRET_KEY,SCW_API_URL,SCW_DEFAULT_ORGANIZATION_IDandSCW_DEFAULT_PROJECT_ID.Module options take precedence over environment variables, which take precedence over the configuration file.
Examples
# This module only reads: it never changes anything, and check mode
# is native.
#
# `route_id` decides which of the two reads runs: given, the
# module returns that one resource; omitted, it lists them all,
# walking every page rather than returning the first one in silence.
- name: Get a route
stephrobert.scaleway.lb_route_info:
zone: fr-par-1
route_id: 11111111-2222-3333-4444-555555555555
register: result
- name: List all routes
stephrobert.scaleway.lb_route_info:
zone: fr-par-1
register: result
- name: Filter Scaleway Load Balancer routes by frontend_id
stephrobert.scaleway.lb_route_info:
zone: fr-par-1
frontend_id: 11111111-2222-3333-4444-555555555555
register: result
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
Retrieve information about an existing route, specified by its route ID. Its full details, origin frontend, target backend and match condition, are returned in the response object. The API contract names no payload field for this operation: the response body is returned as is. Returned: when route_id is provided |
|
ID of the target backend. Returned: when the API returns it |
|
Date on which the route was created. (RFC 3339 format) Returned: when the API returns it |
|
ID of the source frontend. Returned: when the API returns it |
|
Route ID. Returned: when the API returns it |
|
Object defining the match condition for a route to be applied. If an incoming client session matches the specified condition (i.e. it has a matching SNI value or HTTP Host header value), it will be passed to the target backend. Returned: when the API returns it |
|
Date on which the route was last updated. (RFC 3339 format) Returned: when the API returns it |
|
List all routes for a given frontend. The response is an array of routes, each one with a specified backend to direct to if a certain condition is matched (based on the value of the SNI field or HTTP Host header). Returned: when route_id is omitted |
|
ID of the target backend. Returned: when the API returns it |
|
Date on which the route was created. (RFC 3339 format) Returned: when the API returns it |
|
ID of the source frontend. Returned: when the API returns it |
|
Route ID. Returned: when the API returns it |
|
Object defining the match condition for a route to be applied. If an incoming client session matches the specified condition (i.e. it has a matching SNI value or HTTP Host header value), it will be passed to the target backend. Returned: when the API returns it |
|
Date on which the route was last updated. (RFC 3339 format) Returned: when the API returns it |