azure.azcollection.azure_rm_registrationdefinition module – Manage Azure RegistrationDefinition instance
Note
This module is part of the azure.azcollection collection (version 1.19.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_registrationdefinition
.
New in azure.azcollection 1.3.0
Synopsis
Create, update and delete instance of Azure RegistrationDefinition.
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-azure.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: |
|
Use to control if tags field is canonical or just appends to existing tags. When canonical, any tags not found in the tags parameter will be removed from the object’s metadata. Choices:
|
|
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. |
|
For cloud environments other than the US public cloud, the environment name (as defined by Azure Python SDK, eg, Default: |
|
Parent argument. |
|
Parent argument. |
|
Active Directory user password. Use when authenticating with an Active Directory user rather than service principal. |
|
Plan details for the managed services. |
|
The plan name. |
|
The product code. |
|
The publisher ID. |
|
The plan’s version. |
|
Security profile found in ~/.azure/credentials file. |
|
Properties of a registration definition. |
|
Authorization tuple containing principal ID of the user/security group or service principal and ID of the build-in role. |
|
Principal ID of the security group/service principal/user that would be assigned permissions to the projected subscription. |
|
The role definition identifier. This role will define all the permissions that the security group/service principal/user must have on the projected subscription. This role cannot be an owner role. |
|
Description of the registration definition. |
|
ID of the managedBy tenant. |
|
Name of the registration definition. |
|
ID of the registration definition. If is not specified, an UUID will be generated for it. |
|
The subscription ID defines the subscription in which the registration definition will be created. If not specified, will use the subscription derived from AzureRMAuth. |
|
Azure client secret. Use when authenticating with a Service Principal. |
|
Assert the state of the RegistrationDefinition. Use Choices:
|
|
Your Azure subscription Id. |
|
Dictionary of string:string pairs to assign as metadata to the object. Metadata tags on the object will be updated with any provided values. To remove tags set append_tags option to false. Currently, Azure DNS zones and Traffic Manager services also don’t allow the use of spaces in the tag. Azure Front Door doesn’t support the use of Azure Automation and Azure CDN only support 15 tags on resources. |
|
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: Create Registration Definition without scope
azure_rm_registrationdefinition:
registration_definition_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
properties:
description: test
authorizations:
- principal_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
role_definition_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
managed_by_tenant_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
registration_definition_name: def4
- name: Create Registration Definition with scope
azure_rm_registrationdefinition:
scope: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
registration_definition_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
properties:
description: test
authorizations:
- principal_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
role_definition_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
managed_by_tenant_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
registration_definition_name: def5
- name: Delete Registration Definition
azure_rm_registrationdefinition:
registration_definition_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The state info of the registration assignment. Returned: always |
|
Fully qualified path of the registration definition. Returned: always |
|
Name of the registration definition. Returned: always Sample: |
|
Plan details for the managed services. Returned: always |
|
The plan name. Returned: always |
|
The product code. Returned: always |
|
The publisher ID. Returned: always |
|
The plan’s version. Returned: always |
|
Properties of a registration definition. Returned: always |
|
Authorization tuple containing principal ID of the user/security group or service principal and ID of the build-in role. Returned: always |
|
Principal ID of the security group/service principal/user that would be assigned permissions to the projected subscription Returned: always Sample: |
|
The role definition identifier. This role will define all the permissions that the security group/service principal/user must have on the subscription. This role cannot be an owner role. Returned: always Sample: |
|
Description of the registration definition. Returned: always Sample: |
|
ID of the managedBy tenant. Returned: always |
|
Name of the registration definition. Returned: always |
|
Type of the resource. Returned: always Sample: |