-
Notifications
You must be signed in to change notification settings - Fork 332
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
Update azure_rm_appgateway
to support setting WAF policy
#1725
base: dev
Are you sure you want to change the base?
Conversation
Co-authored-by: Fred-sun <[email protected]>
@l3ender In addition, I refer to the azure-mgmt-network file, where the parameter 'web_application_firewall_configuration', 'firewall_policy' and 'force_firewall_policy_association' are equal. Is it better to treat them side by side? Thank you! |
I saw the same but thought to keep the existing Ansible structure intact (everything under Thanks! |
@l3ender Your comment has a comment on several parameters will be abandoned, but there is no message indicating that the reference document should be abandoned, could you please inform your reference document? Thank you! |
SUMMARY
This PR updates the app gateway module so that a web application firewall (WAF) policy can be configured.
Due to previous updates in dependencies (#1697), the WAF settings for an app gateway can only be configured via a separate WAF policy resource. Therefore other options are now deprecated as they are unused. If it is attempted to use the deprecated policies, the following error occurs:
ISSUE TYPE
COMPONENT NAME
azure_rm_appgateway
ADDITIONAL INFORMATION
This change was tested by running the integration test for the module. As there is no module to create a WAF policy, that resource needs to be created separately before referencing it from this module!
Click to expand output of integration test