Support for volume mount options in azurerm_container_app

[riskpoint-per]

Is there an existing issue for this?

• [X] I have searched the existing issues

Community Note

• Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

When adding a volume to the container, there should be a comma separated list of mount options, like in the image below.

New or Affected Resource(s)/Data Source(s)

azurerm_container_app

Potential Terraform Configuration

resource "azurerm_container_app" "example" {
  name                         = "example-app"
  container_app_environment_id = azurerm_container_app_environment.example.id
  resource_group_name          = azurerm_resource_group.example.name
  revision_mode                = "Single"

  ingress {
    target_port = 1234
    # The new item:
    additional_port_mapping {
      external_enabled = true
      target_port = 4321
    }
    additional_port_mapping {
      target_port = 2345
    }
  }

  template {
    container {
      name   = "examplecontainerapp"
      image  = "mcr.microsoft.com/azuredocs/containerapps-helloworld:latest"
      cpu    = 0.25
      memory = "0.5Gi"

      volume_mounts {
        name = "example"
        path = "/tmp/"
      }
    }

    volume {
      name         = "example"
      storage_type = "AzureFile"
      storage_name = azurerm_container_app_environment_storage.example.name
      # The new item:
      mount_options: [ "uid=999", "gid=999", "hard" ]
    }
  }
}

References

No response

[kawahara-titan]

This would be a nice feature. Until then, is using the azapi_update_resource to add the mountOption like below a potential workaround?

resource "azapi_update_resource" "update_resource" {
  name = "my_containerapp_resource"
  parent_id = data.azurerm_resource_group.rg.id
  type = "Microsoft.App/containerApps@2024-03-01"
  body = jsonencode({
    properties = {
      template = {
        volumes = [
          {
            mountOptions = "dir_mode=0777,file_mode=0777"
          }
        ]
      }
    }
  })
}

[matthieupetite]

This would be a nice feature. Until then, is using the azapi_update_resource to add the mountOption like below a potential workaround?

resource "azapi_update_resource" "update_resource" {
  name = "my_containerapp_resource"
  parent_id = data.azurerm_resource_group.rg.id
  type = "Microsoft.App/containerApps@2024-03-01"
  body = jsonencode({
    properties = {
      template = {
        volumes = [
          {
            mountOptions = "dir_mode=0777,file_mode=0777"
          }
        ]
      }
    }
  })
}

Don't forget the revision suffix in the template otherwise the update will not work. But unfortunatly it trigger tow revision instead one :(. It works indeed but we really need the fix

[mapperCoderZ]

any update on this ? we want to go live production, this is necessary for securing our landing zone