Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azurerm_vpn_server_configuration should not require radius.server_root_certificate #16359

Closed
1 task done
derek-burdick opened this issue Apr 12, 2022 · 1 comment · Fixed by #16366
Closed
1 task done
Labels

Comments

@derek-burdick
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

1.1.7

AzureRM Provider Version

3.1.0

Affected Resource(s)/Data Source(s)

azurerm_vpn_server_configuration

Terraform Configuration Files

resource "azurerm_vpn_server_configuration" "test" {
  name                     = "example-config"
  resource_group_name      = azurerm_resource_group.example.name
  location                 = azurerm_resource_group.example.location
  vpn_authentication_types = ["Radius"]
  vpn_protocols            = ["OpenVPN"]
  radius {
    server {
      address = local.radius_IP
      secret  = local.radius_password
      score   = 1
    }
  }
}

Debug Output/Panic Output

N/A

Expected Behaviour

I should be able to create a vpn server configuration using Radius, without specifying a server_root_certificate.

Actual Behaviour

Provider complains that server_root_certificate is required.

Based on the UI and RestAPI, server_root_certificate is NOT required.

Steps to Reproduce

terraform apply

Important Factoids

No response

References

No response

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
2 participants