azure.azcollection.azure_rm_containerappdaprcomponent module – Manage a Dapr component in an Azure Container Apps managed environment
Note
This module is part of the azure.azcollection collection (version 4.2.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_containerappdaprcomponent.
New in azure.azcollection 4.2.0
Synopsis
Create, update and delete a Dapr component in an Azure Container Apps managed environment.
Dapr components (state stores, pub/sub brokers, secret stores, input and output bindings) are shared by the container apps in the environment that reference the component in their
daprconfiguration or in the component’s scopes.The managed environment itself is managed with azure.azcollection.azure_rm_containerappenvironment.
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: |
|
Dapr component type, for example Required when creating the component. |
|
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 managed environment that hosts the Dapr component. |
|
Ignore Dapr component errors when the component fails to start. Choices:
|
|
Dapr component initialization timeout, in the |
|
Parent argument. |
|
Parent argument. |
|
Dapr component configuration metadata. Each entry is either a plain |
|
Metadata property name. |
|
Name of the secret in secrets to pull the value from. |
|
Metadata property value. |
|
Name of the Dapr component. |
|
Direct OpenID Connect (OIDC) token (JWT) used for workload identity authentication. This token is exchanged with Azure AD using OIDC federated identity. Useful in CI systems (for example GitHub Actions, Azure DevOps) where an OIDC token is provided directly by the platform. Can also be set via the |
|
Path to a file containing an OpenID Connect (OIDC) token (JWT) used for workload identity authentication. The file must contain only raw token. This method is commonly used in platforms that materialize OIDC tokens as files Can also be set via the |
|
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 resource group containing the managed environment. |
|
Names of the container apps that can use this Dapr component. When omitted, all container apps in the environment can use it. |
|
Azure client secret. Use when authenticating with a Service Principal. |
|
Name of a Dapr secret store component to retrieve component secrets from. |
|
Collection of secrets used by the Dapr component. Secret values are referenced from metadata entries by secret name. Each entry is an inline Inline secret values are write-only and never returned by Azure, so an update of a component that has secrets must resupply them when the update changes anything - the module fails instead of silently dropping them. Pass an empty list to remove all secrets. |
|
Secret name. |
|
Secret value. |
|
Assert the state of the Dapr component. 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. |
|
When secrets is sent to Azure for an existing component. Inline secret values are write-only and cannot be compared against the stored values, so a run that only changes a secret value is not detected as a change. With With Choices:
|
|
Version of the Dapr component, for example Required when creating the component. |
|
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
On update, fields that are omitted are carried forward from the existing component. Secret values are write-only, so an update of a component that has secrets must resupply secrets when the update changes anything, and the module fails otherwise. Use update_secrets=always to rotate secret values.
Azure Key Vault references are not supported for Dapr component secrets (the service rejects them with DaprComponentSecretNull). To consume Key Vault secrets, deploy a
secretstores.azure.keyvaultDapr component with the vault name in metadata and give the environment’s or apps’ managed identity access to the vault.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 OIDC, pass client_id, tenant and oidc_token or oidc_token_file_path, or set environment variables AZURE_CLIENT_ID, AZURE_TENANT and AZURE_FEDERATED_TOKEN or AZURE_FEDERATED_TOKEN_FILE.
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 logincommand.
Examples
- name: Create a Dapr state store backed by Azure Blob Storage
azure.azcollection.azure_rm_containerappdaprcomponent:
resource_group: myResourceGroup
environment_name: myenvironment
name: statestore
component_type: state.azure.blobstorage
version: v1
metadata:
- name: accountName
value: mystorageaccount
- name: containerName
value: dapr-state
- name: accountKey
secret_ref: storage-account-key
secrets:
- name: storage-account-key
value: "{{ vault_storage_account_key }}"
scopes:
- mycontainerapp
- name: Create a Redis pub/sub component restricted to two apps
azure.azcollection.azure_rm_containerappdaprcomponent:
resource_group: myResourceGroup
environment_name: myenvironment
name: pubsub
component_type: pubsub.redis
version: v1
init_timeout: 1m
metadata:
- name: redisHost
value: myredis.redis.cache.windows.net:6379
- name: redisPassword
secret_ref: redis-password
secrets:
- name: redis-password
value: "{{ vault_redis_password }}"
scopes:
- orders-api
- notifications-worker
- name: Update the scopes of the state store (secrets resupplied)
azure.azcollection.azure_rm_containerappdaprcomponent:
resource_group: myResourceGroup
environment_name: myenvironment
name: statestore
scopes:
- mycontainerapp
- anotherapp
secrets:
- name: storage-account-key
value: "{{ vault_storage_account_key }}"
- name: Rotate the secret value of the state store
azure.azcollection.azure_rm_containerappdaprcomponent:
resource_group: myResourceGroup
environment_name: myenvironment
name: statestore
secrets:
- name: storage-account-key
value: "{{ vault_storage_account_key }}"
update_secrets: always
- name: Delete the pub/sub component
azure.azcollection.azure_rm_containerappdaprcomponent:
resource_group: myResourceGroup
environment_name: myenvironment
name: pubsub
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
The Dapr component definition. Secret values are write-only and are never returned. Returned: when state=present Sample: |