Azure/terraform-azurerm-avm-res-app-managedenvironment v0.3.0

on GitHub

What's Changed

• release 0.3 by @kewalaka in #137, with contributions from @bonddim & @Nepomuceno

Full Changelog: v0.2.1...0.3

Breaking Changes

1. Provider Version Requirements Increased

   • The minimum required Terraform version was raised to >= 1.10 (from >= 1.5.0).
   • The minimum AzureRM provider is now ~> 4.0 (was >= 3.71, < 5).
   • The AzAPI provider constraint is now ~> 2.4 (was >= 1.13, < 3).
   • Impact: Users on older provider versions will need to upgrade before using v0.3.

2. Input Variable Changes and Deprecations

   • New primary input for Log Analytics: log_analytics_workspace (object with resource_id).
     • The previous method of specifying log_analytics_workspace_customer_id and log_analytics_workspace_primary_shared_key directly is now considered legacy; the new input is preferred.
   • The input for managed identities has changed to a structured object (managed_identities).
     • If you previously set identities with other mechanisms, you must update to the new schema.
   • The storages variable has moved and/or been restructured (and the old variable file was deleted).
   • Impact: Any usage of the module with the previous scalar or old-style input patterns will require updates to the new structure.

3. Changed Required Fields in Workload Profiles

   • For dedicated workload profiles, minimum_count and maximum_count are now required fields.
   • The handling of workload profiles was refactored; omitting profiles now creates a Consumption Only plan.
   • Impact: Existing configurations with dedicated workload profiles must specify these counts or Terraform will fail to plan/apply.

4. Module Output Changes

   • New outputs and some renaming (e.g., for managed identities).
   • Some outputs may be missing or changed if you rely on exact output names/types.
   • Impact: Automated workflows or downstream modules that consume outputs may need adjustment.

5. Resource and Data Source Changes

   • Some internal data source and resource usage changed (e.g., switch from azurerm_client_config to azapi_client_config).
   • Impact: Should be transparent for most users, but custom forking/extending of the module may require updates.

6. Behavioral Changes in Examples

   • All examples now use new provider constraints and input/output patterns.
   • Impact: Copy-pasting from old examples will not work without migration.