feat: add a static inbound option for the private dns resolver#313
Merged
MacMur85 merged 2 commits intoJun 19, 2026
Merged
Conversation
6ce003c to
855985b
Compare
saliceti
approved these changes
Jun 19, 2026
rfk-nc
approved these changes
Jun 19, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Description
Change is adding a
private_ip_addresssupport to Private DNS Resolver inbound endpoint and extends theinbound_endpoint_configvariable in the Private DNS Resolver module to support static IP address assignment for the inbound endpoint.Changes
private_ip_addressas an optional field to theinbound_endpoint_configobject typeazurerm_private_dns_resolver_inbound_endpointto conditionally passprivate_ip_addressto theip_configurationsblock only whenprivate_ip_allocation_methodis set to"Static"Validations
Two validation rules have been added to the
inbound_endpoint_configvariable:private_ip_allocation_methodmust be either"Static"or"Dynamic". Any other value will fail at plan time.private_ip_addressmust be provided whenprivate_ip_allocation_methodis set to"Static". If omitted, Terraform will fail at plan time with a descriptive error message.Usage
No breaking changes. Existing callers using
"Dynamic"allocation do not need to update their configuration -private_ip_addressdefaults tonulland is silently ignored.Context
private_ip_addressas an optional field to theinbound_endpoint_configobject typeazurerm_private_dns_resolver_inbound_endpointto conditionally passprivate_ip_addressto theip_configurationsblock only whenprivate_ip_allocation_methodis set to"Static"Validations
Two validation rules have been added to the
inbound_endpoint_configvariable:private_ip_allocation_methodmust be either"Static"or"Dynamic". Any other value will fail at plan time.private_ip_addressmust be provided whenprivate_ip_allocation_methodis set to"Static". If omitted, Terraform will fail at plan time with a descriptive error message.Usage
No breaking changes. Existing callers using
"Dynamic"allocation do not need to update their configuration -private_ip_addressdefaults tonulland is silently ignored.Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.