-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Application Gateway: Refactoring #2054
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of my comments are pretty minor, my only concern is how some of the waf variables are not dereferenced. Other then that LGTM 👍
74a2a0e
to
36482c6
Compare
36482c6
to
255f3b2
Compare
f2bcc00
to
77912b0
Compare
77912b0
to
3f93705
Compare
dff023a
to
80400a9
Compare
80400a9
to
f1efeeb
Compare
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 👉 [email protected]. Thanks! |
This PR normalizes the state of the
azurerm_application_gateway
resource to ensure that it can be iterated on in the future. Rather than making larger structural changes - this PR gets the resource to a known state (for example, ensuring that Lists are set as Lists rather than Sets, and rewriting the documentation) - and adds TODO's for future enhancements which are intentionally not implemented in this PR, for example:Given this is a large-scale refactor - to make this easier to review I've tried to keep one commit per 'thing' - so there's a large number of small commits (which I'm hoping makes this simpler to review but ¯_(ツ)_/¯)
Fixes #1907
Fixes #2155