Open Joseluismantilla opened 1 month ago
Hi @Joseluismantilla , I believe this is a Terraform by-design behavior rather than a provider issue. If you believe it needs to be fixed, please file an issue in Terraform Core: https://github.com/hashicorp/terraform/issues
Is there an existing issue for this?
Community Note
Terraform Version
1.9.2
AzureRM Provider Version
3.112.0
Affected Resource(s)/Data Source(s)
azurerm_key_vault
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The output must add my public ip to the list, not to remove all the ip rules even when the local ip can't be calculated because of the concat function, additionally, the same line works with the storage account in the network_rules where this only adds the public ip.
Actual Behaviour
I wanted to add the local ip by adding...
ip_rules = var.disallow_public_traffic ? [] : concat(var.custom_ip_rules, [local.msft_agent_public_ip, "185.46.212.0/22", "104.129.192.0/20"... ])
This change deletes all the current ip rules:![image](https://github.com/user-attachments/assets/8377fef5-e0ab-4123-bd61-a6e619b282bd)
Steps to Reproduce
terraform plan with previous ip rules added in the azure key vault
Important Factoids
No response
References
No response