You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Through PowerShell today you can create an SSL Policy on an application gateway. Ideally on the azurem_application_gateway module you should be able to specify an ssl_policy block as such:
Here is the documentation from azure-docs [https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/application-gateway/application-gateway-configure-ssl-policy-powershell.md]
The text was updated successfully, but these errors were encountered:
Support for this has previously been requested in #451 - as such I'm going to close this issue in favour of that one. Just to let you know that we've got a few enhancements we want to do for the Application Gateway resource - but we're actually waiting on a critical bug to be fixed in the Application Gateway API before we extend this resource further - but we'll be sure to take a look when that's resolved.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Through PowerShell today you can create an SSL Policy on an application gateway. Ideally on the azurem_application_gateway module you should be able to specify an ssl_policy block as such:
Here is the documentation from azure-docs [https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/application-gateway/application-gateway-configure-ssl-policy-powershell.md]
The text was updated successfully, but these errors were encountered: