-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 new beta non-rfc fields in dns managed zone #3026
Conversation
Forwarding path for this TargetNameServer. If unset or `default` Cloud DNS will make forwarding | ||
decision based on address ranges, i.e. RFC1918 addresses go to the VPC, Non-RFC1918 addresses go | ||
to the Internet. When set to `private`, Cloud DNS will always send queries through VPC for this target | ||
values: |
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 want to confirm that the API returns what we send it here- so if we send it "" it returns "" and if we send it "default" it returns "default"?
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.
Yep, it also unsets based on what we send in the PATCH request, so going from forwarding_path = 'private' to not setting forwarding_path in the config causes it to be removed on the API side as well
4ca6b59
to
3d08eab
Compare
3d08eab
to
adc2364
Compare
…oudPlatform#3026) * Add support for new beta non-rfc fields in dns managed zone * Test updating forwarding path * Forgot to remove a param * Typo
Fixes: hashicorp/terraform-provider-google#5062
I cribbed the object_to_bool and bool_to_object code from: #3007 as this will likely make it in before that.
Release Note Template for Downstream PRs (will be copied)