-
Notifications
You must be signed in to change notification settings - Fork 89
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
feature: add Azure Virtual Network Gateway scanner #207
Conversation
@cmendible You have any requests for other scan rules? Thanks! |
0aad5bd
to
68ddaa6
Compare
@vanwinkelseppe I'm about to merge: #214 so please check if the new SDK for networking helps you with the SLA rule we are reviewing |
@cmendible will do thanks! |
4f272ce
to
809454c
Compare
@cmendible Still no SKU on the VPNGateway, bypassed it by querying for the VirtualNetworkGateway. Ready for review, have to do the list of rules, but with all the merges I'll do it when it looks ready to go! |
809454c
to
17ba909
Compare
Because the VPNGateway implementation doesn't expose SKU. I've implemented it with a bypass of VirtualNetworkGateway
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.
Hey! Check the following branch: https://github.com/Azure/azqr/tree/vpn I made some changes so we only query for Virtual Network Gateway objects and take decisions based on the type.
If you are ok with it merge it into your PR and if possible add an Availability Zone rule based on the service tier.
Will do tonight or tomorrow! Thanks for the refactor! |
8c28ce4
to
8956bdf
Compare
@cmendible, uncertain for the availability zones. I did make a list of which gateway skus can enable them:
|
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.
LGTM
@vanwinkelseppe let's use the SKU, and if SKU (to lower) contains |
Closed in favor of: #237 |
Description
Add a scanner for Azure Virtual Network Gateway
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #206
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: