-
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
azurerm_firewall: support snat private ip ranges #7535
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.
hey @magodo
Thanks for this PR :)
Taking a look through whilst this works it appears these fields need to be added to the Swagger?
Thanks!
rangeSlice := utils.ExpandStringSlice(v.(*schema.Set).List()) | ||
if rangeSlice != nil { | ||
privateIpRanges = strings.Join(*rangeSlice, ",") | ||
parameters.AdditionalProperties["Network.SNAT.PrivateRanges"] = &privateIpRanges |
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.
is there a reason these fields aren't exposed in the Swagger? historically the Networking API's have introduced breaking schema changes - so this is less likely if these are typed, since they'll be caught via ARM review?
@tombuildsstuff Seems ARM review will not check the changes on those mappings, as reviewer might not have knowledge on whether that is a regular map accepting arbitrary kv or a map playing role as special config using certain keys (as this one) |
@magodo in this instance we've had similar issues with DataBricks in the past and ended up having to send Swagger PR's to fix this (e.g. Azure/azure-rest-api-specs#7872) - so that'd be my next suggestion here |
@tombuildsstuff Thank you for the example/suggestion to submit a PR to the Swagger. Whilst currently there is no document enumerating all the available KVs. Hence I'll submit an issue (Azure/azure-rest-api-specs#10015) instead. |
as this is blocked on swagger i'm going to close it @magodo, we can revive the branch once they've updated it. |
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! |
Support SNAT private ip ranges in
azurerm_firewall
.Test Result
(Fix #7504)