-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add support for standalone Distributed Firewall Rule management #587
Conversation
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
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.
This PR is close to magick. For some reason, you have two like that this week already (first was the partial matching of IP ranges in #1062) :) Hence, sharing some thoughts in-line.
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.
Just some really minor things. Other than that, great PR. The wrapper is really smart.
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
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.
Great implementation!
Signed-off-by: Dainius Serplis <dserplis@vmware.com>
This PR improves NSX-T Distributed Firewall Rule management.
VCD APIs do not provide a mechanism to create a single firewall rule, only all of them at once. This PR introduces types and methods for managing Distributed Firewall Rules one by one.
The main thing to note is that
VdcGroup.CreateDistributedFirewallRule
still leverages the API endpoint for "update all", but does the work of merging rules, preserving their order, usingjson.RawMessage
instead of exact types to prevent altering rules in any way now and in future.