Skip to content

fix: prevent dns_prefix from being set when fqdn_subdomain is used#167

Merged
matt-FFFFFF merged 3 commits intomainfrom
fix/166-private-cluster-dns-prefix
Feb 27, 2026
Merged

fix: prevent dns_prefix from being set when fqdn_subdomain is used#167
matt-FFFFFF merged 3 commits intomainfrom
fix/166-private-cluster-dns-prefix

Conversation

@matt-FFFFFF
Copy link
Copy Markdown
Member

Summary

  • Fix private cluster deployments broken by v0.5.0 (PR Generate DNS prefix when unset #164) which always generated a dnsPrefix, even when fqdn_subdomain was set. Azure's API requires these to be mutually exclusive.
  • The dnsPrefix property is now set to null (and filtered from the request body) when fqdn_subdomain is provided.
  • Added unit tests covering all three scenarios: auto-generated prefix, explicit fqdn_subdomain, and explicit dns_prefix.

Closes #166

Private clusters that use fqdn_subdomain must not set dns_prefix as they
are mutually exclusive in the Azure API. The coalesce() introduced in
PR #164 always generated a dns_prefix, breaking private cluster
deployments with a PropertyChangeNotAllowed error.

Closes #166
@microsoft-github-policy-service
Copy link
Copy Markdown

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the Terraform Issue Triage documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs: Triage 🔍 Maintainers need to triage still

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[AVM Module Issue]: Version 0.5.0 breaks private clusters

1 participant