Closed DaleyKD closed 2 years ago
@DaleyKD I've used above config and things worked for me:
As is seen my Portal UI looks different from yours. Could you inspect the networkAcls
property in the Portal to see what's the value is set to the defaultAction
? Alternatively, can you run another terraform plan
after your first provisioning, to ensure the config matches the remote state.
For the error of your manual change, do you mean you manually check on the "Selected networks" and press "save"? If so, that looks like a Portal issue.
I'm going to go ahead and close this since it seems like it may have been a hiccup in the Azure Portal UI. However, my UI definitely looks different than yours, and has stayed that way for weeks.
FWIW, terraform plan
did match the remote state.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
1.2.4
AzureRM Provider Version
3.14.0
Affected Resource(s)/Data Source(s)
azurerm_key_vault
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The Azure Key Vault should be created where, on the Networking tab, one of the radio buttons (specifically "Selected Networks") is selected.
Actual Behaviour
The Azure Key Vault is created. When looking at the Networking tab, no radio button is selected.
If attempting to manually modify the Access Policies, an error is generated:
Steps to Reproduce
terraform apply
Important Factoids
No response
References
No response