[AVM Module Issue]: Documentation of customer managed does not match its usage

[jo2]

Check for previous/existing GitHub issues

• [x] I have checked for previous/existing GitHub issues

Issue Type?

Bug

(Optional) Module Version

0.1.2

(Optional) Correlation Id

No response

Description

The variables.tf lists these attributes for customer_managed_key:

variable "customer_managed_key" {
  type = object({
    key_vault_resource_id = string
    key_name              = string
    key_version           = optional(string, null)
    user_assigned_identity = optional(object({
      resource_id = string
    }), null)
  })
  default     = null
  description = ..}

In its usage, totally different attributes are used:

dynamic "customer_managed_key" {
  for_each = var.customer_managed_key == null ? [] : [var.customer_managed_key]

  content {
    key_vault_key_id                     = customer_managed_key.value.key_vault_key_id
    geo_backup_key_vault_key_id          = customer_managed_key.value.geo_backup_key_vault_key_id
    geo_backup_user_assigned_identity_id = customer_managed_key.value.geo_backup_user_assigned_identity_id
    primary_user_assigned_identity_id    = customer_managed_key.value.primary_user_assigned_identity_id
  }
}

[microsoft-github-policy-service[bot]]

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!