azure.azcollection.azure_rm_afdrules_info module – Get Azure Front Door Rule 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_afdrules_info
.
New in azure.azcollection 3.4.0
Synopsis
Get facts for a specific Azure Front Door (AFD) Rule or all AFD Rules in a Ruleset.
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:
|
|
Parent argument. |
|
Parent argument. |
|
Name of the delivery rule which is unique within the endpoint. |
|
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. |
|
Name of the rule set under the profile. |
|
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 Rules in the AFD Profile
azure_rm_afdrule_info:
rule_set_name: myRuleset
profile_name: myProfile
resource_group: myResourceGroup
- name: Get facts of specific AFD Rule
azure_rm_afdrule_info:
name: myRule1
rule_set_name: myRuleset
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 Rules. Returned: always |
|
A list of actions that are executed when all the conditions of a rule are satisfied. Returned: success |
|
Caching behavior for the requests. Returned: success |
|
The duration for which the content needs to be cached. Allowed format is [d.]hh:mm:ss. Returned: success |
|
Fragment to add to the redirect URL. Fragment is the part of the URL that comes after Returned: success |
|
Host to redirect. Leave empty to use the incoming host as the destination host. Returned: success |
|
The full path to redirect. Path cannot be empty and must start with /. Leave empty to use the incoming path as destination path. Returned: success |
|
The set of query strings to be placed in the redirect URL. Setting this value would replace any existing query string; leave empty to preserve the incoming query string. Query string must be in <key>=:code:<value> format. ? and & will be added automatically so do not include them. Returned: success |
|
Define the relative URL to which the above requests will be rewritten by. Returned: success |
|
Protocol to use for the redirect. Returned: success |
|
Protocol this rule will use when forwarding traffic to backends. Returned: success |
|
Action to perform. Returned: success |
|
Name of the header to modify. Returned: success |
|
The caching configuration for this route. 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 |
|
The name of the action for the delivery rule. Returned: success |
|
defines the OriginGroup that would override the DefaultOriginGroup. Returned: success |
|
Whether to preserve unmatched path. Returned: success |
|
query parameters to include or exclude (comma separated). Returned: success |
|
The caching configuration for this route. 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 |
|
The redirect type the rule will use when redirecting traffic. Returned: success |
|
Define a request URI pattern that identifies the type of requests that may be rewritten. If value is blank, all strings are matched. Returned: success |
|
Value for the specified action. Returned: success |
|
A list of conditions that must be matched for the actions to be executed. Returned: success |
|
The match value for the condition of the delivery rule. Returned: success |
|
The name of the condition for the delivery rule. Returned: success |
|
Describes if this is a negate condition or not. Returned: success |
|
Describes operator to be matched. Returned: success |
|
Name of item to be matched. Returned: success |
|
List of transforms. Returned: success |
|
If this rule is a match should the rules engine continue running the remaining rules or stop. Returned: success |
|
Name of the delivery rule which is unique within the endpoint. Returned: success |
|
The order in which the rules are applied for the endpoint. A rule with a lesser order will be applied before a rule with a greater order. Rule with order 0 is a special rule. It does not require any condition and actions listed in it will always be applied. Returned: success |
|
Name of the Azure Front Door Standard or Azure Front Door Premium profile which is unique within the resource group. Returned: success |
|
Name of the Resource group within the Azure subscription. Returned: success |
|
Name of the rule set under the profile. Returned: success |
|
Assert the state of the CDN profile. Use Returned: success |
|
Resource type. Returned: success |
Authors
Jarret Tooley (@jartoo)