azure.azcollection.azure_rm_afdorigin module – Manage an Azure Front Door Origin to be used with Standard or Premium Frontdoor.
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_afdorigin
.
New in azure.azcollection 3.4.0
Synopsis
Create, update and delete an Azure Front Door (AFD) Origin to be used by a Front Door Service Profile created using azure_rm_cdnprofile.
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:
|
|
Resource reference to the AFD origin resource. |
|
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:
|
|
Whether to enable health probes to be made against backends defined under backend pools. Health probes can only be disabled if there is a single enabled backend in single enabled backend pool. Choices:
|
|
The address of the origin. Domain names, IPv4 addresses, and IPv6 addresses are supported. This should be unique across all origins in an endpoint. |
|
The value of the HTTP port. Must be between 1 and 65535. Default: |
|
The value of the HTTPS port. Must be between 1 and 65535. Default: |
|
Parent argument. |
|
Parent argument. |
|
Name of the origin that is unique within the AFD Profile. |
|
Name of the origin group which is unique within the profile. |
|
The host header value sent to the origin with each request. If you leave this blank, the request hostname determines this value. Azure Front Door origins, such as Web Apps, Blob Storage, and Cloud Services require this host header value to match the origin hostname by default. This overrides the host header defined at the AFD Endpoint. |
|
Active Directory user password. Use when authenticating with an Active Directory user rather than service principal. |
|
Priority of origin in given origin group for load balancing. Higher priorities will not be used for load balancing if any lower priority origin is healthy. Must be between 1 and 5. |
|
Security profile found in ~/.azure/credentials file. |
|
Name of the AFD Profile. |
|
Name of a resource group where the AFD Origin exists or will be created. |
|
Azure client secret. Use when authenticating with a Service Principal. |
|
The properties of the private link resource for private origin. |
|
The group id from the provider of resource the shared private link resource is for. |
|
The resource id of the resource the shared private link resource is for. |
|
The location of the shared private link resource. |
|
The request message for requesting approval of the shared private link resource. |
|
Status of the shared private link resource. Can be Pending, Approved, Rejected, Disconnected, or Timeout. Choices:
|
|
Assert the state of the AFD Profile. Use Choices:
|
|
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. |
|
Weight of the origin in given origin group for load balancing. Must be between 1 and 1000. |
|
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: Create an AFD Origin
azure_rm_afdorigin:
name: myOrigin
origin_group_name: myOriginGroup
profile_name: myProfile
resource_group: myResourceGroup
state: present
host_name: "10.0.0.1"
origin_host_header: "10.0.0.1"
http_port: 80
https_port: 443
priority: 1
weight: 1000
- name: Delete an AFD Origin
azure_rm_afdorigin:
name: myOrigin
origin_group_name: myOriginGroup
profile_name: myProfile
resource_group: myResourceGroup
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Host name of the AFD Origin. Returned: always Sample: |
|
ID of the AFD Origin. Returned: always Sample: |
Authors
Jarret Tooley (@jartoo)