This terraform module automates the creation of container app resources on the azure cloud platform, enabling easier deployment and management of container apps within a container app environment.
The main objective is to create a more logic data structure, achieved by combining and grouping related resources together in a complex object.
The structure of the module promotes reusability. It's intended to be a repeatable component, simplifying the process of building diverse workloads and platform accelerators consistently.
A primary goal is to utilize keys and values in the object that correspond to the REST API's structure. This enables us to carry out iterations, increasing its practical value as time goes on.
A last key goal is to separate logic from configuration in the module, thereby enhancing its scalability, ease of customization, and manageability.
These modules are not intended to be complete, ready-to-use solutions; they are designed as components for creating your own patterns.
They are not tailored for a single use case but are meant to be versatile and applicable to a range of scenarios.
Security standardization is applied at the pattern level, while the modules include default values based on best practices but do not enforce specific security standards.
End-to-end testing is not conducted on these modules, as they are individual components and do not undergo the extensive testing reserved for complete patterns or solutions.
- provides support for retrieval of container images from the registry using user-assigned identities
- provides support for secrets to retrieve from a key vault backend scope
- offers possibility to integrate the container app environment to your own vnet (vnet integration)
- allows for ingress to be set to external (limited to container app environment), limited to the vnet or wide open
- facilitates the use of custom domain names for your container apps
- provides support for certificates for custom domain names
- allows for multiple container apps to be deployed within a container app environment
- enables multiple container app jobs
- utilization of terratest for robust validation
| Name | Version |
|---|---|
| terraform | ~> 1.0 |
| azurerm | ~> 4.0 |
| Name | Version |
|---|---|
| azurerm | ~> 4.0 |
| Name | Type |
|---|---|
| azurerm_container_app.ca | resource |
| azurerm_container_app_custom_domain.domain | resource |
| azurerm_container_app_environment.cae | resource |
| azurerm_container_app_environment_certificate.certificate | resource |
| azurerm_container_app_job.job | resource |
| azurerm_role_assignment.role_acr_pull | resource |
| azurerm_role_assignment.role_acr_pull_jobs | resource |
| azurerm_role_assignment.role_secret_user | resource |
| azurerm_role_assignment.role_secret_user_jobs | resource |
| azurerm_user_assigned_identity.identity | resource |
| azurerm_user_assigned_identity.identity_jobs | resource |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| environment | describes container apps configuration | any |
n/a | yes |
| location | default azure region and can be used if location is not specified inside the object. | string |
null |
no |
| naming | contains naming convention | map(string) |
{} |
no |
| resource_group | default resource group and can be used if resourcegroup is not specified inside the object. | string |
null |
no |
| tags | default tags and can be used if tags are not specified inside the object. | map(string) |
{} |
no |
| Name | Description |
|---|---|
| certificates | contains all container app environment certificate(s) configuration |
| container_app_jobs | contains all container app jobs configuration |
| container_apps | contains all container app(s) configuration |
| custom_domains | contains all container app custom domain(s) configuration |
| environment | contains all container app environment configuration |
| user_assigned_identities | contains all user assigned identities configuration |
For more information, please see our testing guidelines
Using a dedicated module, we've developed a naming convention for resources that's based on specific regular expressions for each type, ensuring correct abbreviations and offering flexibility with multiple prefixes and suffixes.
Full examples detailing all usages, along with integrations with dependency modules, are located in the examples directory.
To update the module's documentation run make doc
Recommended Identity for Image Retrieval from Azure Container Registry (ACR): While it's technically possible to use a system-assigned identity for pulling images from an Azure Container Registry (ACR), we strongly recommend using user-assigned identities. Here's why:
The system-assigned identity requires 'AcrPull' permissions on the registry. However, you cannot assign this role until after the resource (in this case, the container app) has been deployed. This creates a catch-22, because the container app cannot be deployed without first retrieving an image.
By using a user-assigned identity, this issue can be avoided. The deployment order within the module would be as follows:
- deploy ACR
- deploy user-assigned identity
- assign the 'AcrPull' role
- deploy the container app
This way, the module ensures that all the necessary permissions are in place before the container app deployment. It is a smoother, first time right deployment and more reliable process that we strongly recommend for most use cases. See also here
Module is maintained by these awesome contributors.
We welcome contributions from the community! Whether it's reporting a bug, suggesting a new feature, or submitting a pull request, your input is highly valued.
For more information, please see our contribution guidelines.
MIT Licensed. See LICENSE for full details.