azure.azcollection.azure_rm_afdroute_info module – Get Azure Front Door Route facts to be used with Standard or Premium Frontdoor Service
Note
This module is part of the azure.azcollection collection (version 3.8.0).
You might already have this collection installed if you are using the ansible
package.
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 azure.azcollection
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: azure.azcollection.azure_rm_afdroute_info
.
New in azure.azcollection 3.4.0
Synopsis
Get facts for a specific Azure Front Door (AFD) Route or all AFD Routes.
This differs from the Front Door classic service and only is intended to be used by the Standard or Premium service offering.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.7
The host that executes this module must have the azure.azcollection collection installed via galaxy
All python packages listed in collection’s requirements.txt must be installed via pip on the host that executes modules from azure.azcollection
Full installation instructions may be found https://galaxy.ansible.com/azure/azcollection
Parameters
Parameter |
Comments |
---|---|
Active Directory username. Use when authenticating with an Active Directory user rather than service principal. |
|
Azure AD authority url. Use when authenticating with Username/password, and has your own ADFS authority. |
|
Selects an API profile to use when communicating with Azure services. Default value of Default: |
|
Controls the source of the credentials to use for authentication. Can also be set via the When set to When set to When set to When set to When set to The Choices:
|
|
Controls the certificate validation behavior for Azure endpoints. By default, all modules will validate the server certificate, but when an HTTPS proxy is in use, or against Azure Stack, it may be necessary to disable this behavior by passing Choices:
|
|
Azure client ID. Use when authenticating with a Service Principal or Managed Identity (msi). Can also be set via the |
|
For cloud environments other than the US public cloud, the environment name (as defined by Azure Python SDK, eg, Default: |
|
Determines whether or not instance discovery is performed when attempting to authenticate. Setting this to true will completely disable both instance discovery and authority validation. This functionality is intended for use in scenarios where the metadata endpoint cannot be reached such as in private clouds or Azure Stack. The process of instance discovery entails retrieving authority metadata from https://login.microsoft.com/ to validate the authority. By setting this to **True**, the validation of the authority is disabled. As a result, it is crucial to ensure that the configured authority host is valid and trustworthy. Set via credential file profile or the Choices:
|
|
Name of the endpoint under the profile which is unique globally. |
|
Parent argument. |
|
Parent argument. |
|
Name of the route. |
|
Active Directory user password. Use when authenticating with an Active Directory user rather than service principal. |
|
Security profile found in ~/.azure/credentials file. |
|
Name of the Azure Front Door Standard or Azure Front Door Premium profile which is unique within the resource group |
|
Name of the Resource group within the Azure subscription. |
|
Azure client secret. Use when authenticating with a Service Principal. |
|
Your Azure subscription Id. |
|
Azure tenant ID. Use when authenticating with a Service Principal. |
|
The thumbprint of the private key specified in x509_certificate_path. Use when authenticating with a Service Principal. Required if x509_certificate_path is defined. |
|
Path to the X509 certificate used to create the service principal in PEM format. The certificate must be appended to the private key. Use when authenticating with a Service Principal. |
Notes
Note
For authentication with Azure you can pass parameters, set environment variables, use a profile stored in ~/.azure/credentials, or log in before you run your tasks or playbook with
az login
.Authentication is also possible using a service principal or Active Directory user.
To authenticate via service principal, pass subscription_id, client_id, secret and tenant or set environment variables AZURE_SUBSCRIPTION_ID, AZURE_CLIENT_ID, AZURE_SECRET and AZURE_TENANT.
To authenticate via Active Directory user, pass ad_user and password, or set AZURE_AD_USER and AZURE_PASSWORD in the environment.
Alternatively, credentials can be stored in ~/.azure/credentials. This is an ini file containing a [default] section and the following keys: subscription_id, client_id, secret and tenant or subscription_id, ad_user and password. It is also possible to add additional profiles. Specify the profile by passing profile or setting AZURE_PROFILE in the environment.
See Also
See also
- Sign in with Azure CLI
How to authenticate using the
az login
command.
Examples
- name: Get facts for all Routes in the AFD Profile
azure_rm_afdroute_info:
endpoint_name: myEndpoint
profile_name: myProfile
resource_group: myResourceGroup
- name: Get facts of specific AFD Route
azure_rm_afdroute_info:
name: myRoute1
endpoint_name: myEndpoint
profile_name: myProfile
resource_group: myResourceGroup
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
List of AFD Routes. Returned: always |
|
List of content types (str) on which compression applies. The value should be a valid MIME type. Returned: success |
|
Domain id’s referenced by this endpoint. Returned: success |
|
Current state of the resource. Returned: success Sample: |
|
Whether to enable use of this rule. Returned: success |
|
Name of the endpoint. Returned: success |
|
Protocol this rule will use when forwarding traffic to backends. Returned: success |
|
Whether to automatically redirect HTTP traffic to HTTPS traffic. Note that this is a easy way to set up this rule and it will be the first rule that gets executed. Returned: success |
|
ID of the AFD Route. Returned: success Sample: |
|
Indicates whether content compression is enabled on AzureFrontDoor. If compression is enabled, content will be served as compressed if user requests for a compressed version. Content won’t be compressed on AzureFrontDoor when requested content is smaller than 1 byte or larger than 1 MB. Returned: success |
|
Whether this route will be linked to the default endpoint domain. Returned: success |
|
Name of the AFD Route. Returned: success |
|
The origin group id. Returned: success Sample: |
|
A directory path on the origin that AzureFrontDoor can use to retrieve content from, e.g. contoso.cloudapp.net/originpath. Returned: success |
|
The route patterns of the rule. Returned: success |
|
Name of the AFD Profile where the Route is. Returned: success |
|
Provisioning status of the AFD Route. Returned: success Sample: |
|
query parameters to include or exclude (comma separated). Returned: success |
|
Defines how Frontdoor caches requests that include query strings. You can ignore any query strings when caching, ignore specific query strings, cache every request with a unique URL, or cache specific query strings. Returned: success |
|
Name of a resource group where the AFD Route exists. Returned: success |
|
List of rule set id referenced by this endpoint. Returned: success |
|
List of supported protocols for this route. Returned: success |
|
Resource type. Returned: success Sample: |
Authors
Jarret Tooley (@jartoo)