v0.13.0

Breaking Change(s)

• module supports azurerm 4.8.x and later versions
• always_on defaults to true
• ftps_state defaults to "FtpsOnly"
• minimum_tls_version defaults to "1.3"

Feature(s)

None

Update(s)

• examples uses regions 0.8.x and later versions
• removed main.service_plan.tf and main.storage_account.tf
• removed comments from variables.tf

v0.12.1

Breaking Change(s)

None

Feature(s)

• addressing bug where slot.site_config was missing virtual_application block via Issue #140

Update(s)

• .github/workflows upgrades

v0.12.0

Breaking Change(s)

PLEASE READ! Includes VERY IMPORTANT Breaking Changes

• v0.12.0 will no longer support azurerm 3.xbut will now support azurerm 4.x

Feature(s)

• azurerm 4.x support addressing Issue #122
• enabling tls 1.3 support through azurerm 4.8 support (Issue #136)

Update(s)

• bug fixes to unmanaged private endpoints with deployment slots as highlighted in PR #129
• arguments removed as no longer supported by azurerm 4.x
  • docker_container_name (as part of application_stack)
  • docker_container_tag (as part of application_stack)
  • path (as part of slow_request. Please you slow_request_with_path if needed.)
  • auto_heal_enabled
• login map made optional by module (still required by provider for auth_settings_v2) so that a default login map can be automatically set for auth_settings_v2 addressing Issue #130

v0.11.0

Breaking Change(s)

PLEASE READ! Includes VERY IMPORTANT Breaking Changes

• module no longer supports the creation and management of App Service Plan
  • removed the following variables:
    • create_service_plan
    • new_service_plan
  • removed related outputs:
    • service_plan
    • service_plan_id
    • service_plan_name

Users will need to reference an app service plan using service_plan_resource_id, thus making it a required input.

• module no longer supports the creation and management of Storage Account for Function App
  • removed the following variables:
    • function_app_create_storage_account
    • function_app_storage_account
    • function_app_storage_account_access_key
    • function_app_storage_account_inherit_lock
    • function_app_storage_account_name
    • function_app_storage_uses_managed_identity
  • removed related outputs:
    • storage_account
    • storage_account_lock

Users can still supply an existing storage account using storage_account_access_key (or storage_uses_managed_identity) and storage_account_name.

• Terraform minimum required version raised to 1.9

Feature(s)

None

Update(s)

• fix: addressing Issue #120 where azurerm_windows_function_app site config was missing ip_restriction_default_action and scm_ip_restriction_default_action
• improvements variable documentation

v0.10.0

Breaking Change(s)

• migration to version 0.1.0 of avm-res-web-serverfarm from azurerm_service_plan
• removed certain outputs regarding service_plan

Feature(s)

• added addtitional support for avm-res-storage-storageaccount inputs
• added additional support for new_service_plan variable

Update(s)

• module now uses version 0.2.4 of avm-res-storage-storageaccount
• x_fd_health_probe to properly work when using ip_restriction/scm_ip_restriction and Azure Front Door
• module is now configured to zone redundant by default
  • worker_count defaults to 3
  • zone_balancing_enabled defaults to true
  • sku_name defaults to P1v2

v0.9.1

Breaking Change(s)

None

Feature(s)

None

Update(s)

• updates for github policies and workflows
• removed providers from yml templates and markdown documentation
• removed examples for:
  • linux_function_app
  • linux_web_app
  • windows_function_app
  • windows_web_app
• created examples for:
  • function_app
  • web_app

v0.9.0

Breaking Change(s)

• changes to key references of dynamic blocks application_logs and http_logs for logs via Issue #106

Feature(s)

None

Update(s)

• corrected azure_blob_storage block to reference azure_blob_storage_http instead of azure_blob_storage for http_logs
• added examples/logs

v0.8.1

Breaking Change(s)

None

Feature(s)

• azurerm_app_service_slot_custom_hostname_binding now supports azurerm_[windows|linux]_web_app_slot

Previous Logic:

app_service_slot_id = var.os_type == "Windows" ? azurerm_windows_function_app_slot.this[each.value.app_service_slot_key].id : azurerm_linux_function_app_slot.this[each.value.app_service_slot_key].id

Current Logic:

app_service_slot_id = var.kind == "functionapp" ? (var.os_type == "Windows" ? azurerm_windows_function_app_slot.this[each.value.app_service_slot_key].id : azurerm_linux_function_app_slot.this[each.value.app_service_slot_key].id) : (var.os_type == "Windows" ? azurerm_windows_web_app_slot.this[each.value.app_service_slot_key].id : azurerm_linux_web_app_slot.this[each.value.app_service_slot_key].id)

• thumbprint can now reference existing thumbprint value with thumbprint_value

Previous Logic:

thumbprint          = azurerm_app_service_certificate.this[each.value.thumbprint_key].thumbprint

Current Logic:

  thumbprint          = each.value.thumbprint_key != null ? azurerm_app_service_certificate.this[each.value.thumbprint_key].thumbprint : each.value.thumbprint_value

Update(s)

• thumbprints as new output
• cleaning exmples/cusom_domain/main.tf file

v0.8.0

Breaking Change(s)

• new mapping for azurerm_app_service_custom_hostname_binding

will likely affect any configurations with existing custom domains managed by terraform

Feature(s)

• functionality for custom domains for deployment slots using azurerm_app_service_slot_custom_hostname_binding resource via Issue #101.

uses slot_as_target in custom_domains as toggle to differentiate between azurerm_app_service_custom_hostname_binding and azurerm_app_service_slot_custom_hostname_binding

• azurerm_app_service_certificate to accept key_vault_id argument via Issue #102

Update(s)

• additional outputs added for:
  • function_app_active_slot
  • function_app_deployment_slots
  • kind
  • os_type

v0.7.3

Breaking Change(s):

None

Feature(s):

• new telemetry
  • transition to use of modtm provider (view here)
  • removed locals.telemetry.tf
  • removed locals.telemetry.tf.json

Update(s):

• added examples / storage_uses_managed_identity
• fixed logic for storage_uses_managed_identity for azurerm_(windows | linux)_function_app via Issue #96

Previous:

storage_uses_managed_identity                  = var.function_app_storage_uses_managed_identity == true && var.function_app_storage_account_access_key == null && var.function_app_storage_account == null ? var.function_app_storage_uses_managed_identity : null

Current:

storage_uses_managed_identity                  = var.function_app_storage_uses_managed_identity == true && var.function_app_storage_account_access_key == null ? var.function_app_storage_uses_managed_identity : null

• updated logic for azurerm_linux_function_app and azurerm_linux_function_app_slot to account for created storage account's access key

storage_account_access_key                     = var.function_app_storage_account_access_key != null && var.function_app_storage_uses_managed_identity != true && var.function_app_create_storage_account != true ? var.function_app_storage_account_access_key : var.function_app_storage_account_access_key == null && var.function_app_storage_uses_managed_identity != true && var.function_app_create_storage_account ? module.avm_res_storage_storageaccount[0].resource.primary_access_key : null