-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Release Az 15.5.0 #29356
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
Release Az 15.5.0 #29356
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -18,6 +18,10 @@ | |||||
| - Additional information about change #1 | ||||||
| --> | ||||||
| ## Upcoming Release | ||||||
| * Added announcement for upcoming breaking changes as part of the 2025-10-01-preview API migration: | ||||||
| - Removed parameter `ActionBlockResponseCode` from `New-AzDnsResolverPolicyDnsSecurityRule` and `Update-AzDnsResolverPolicyDnsSecurityRule`. The block response code is no longer configurable. | ||||||
| - Parameter `DnsResolverDomainList` is no longer mandatory on `New-AzDnsResolverPolicyDnsSecurityRule`. DNS security rules will support managed domain lists as an alternative to user-defined domain lists. | ||||||
| - Parameter `Domain` is no longer mandatory on `New-AzDnsResolverDomainList`. Domain lists will support bulk upload via the new cmdlet `Invoke-AzDnsResolverBulkDnsResolverDomainList`, which will be introduced in the upcoming release. | ||||||
|
||||||
| - Parameter `Domain` is no longer mandatory on `New-AzDnsResolverDomainList`. Domain lists will support bulk upload via the new cmdlet `Invoke-AzDnsResolverBulkDnsResolverDomainList`, which will be introduced in the upcoming release. | |
| - Parameter `Domain` is no longer mandatory on `New-AzDnsResolverDomainList`. Domain lists will support bulk upload via the new cmdlet `Invoke-AzDnsResolverBulkDnsResolverDomainList`, which is planned for a future release. |
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.
The
where.subject: PolicyDnsSecurityRuleselector does not match the actual generated cmdlet subject (DnsResolverPolicyDnsSecurityRule), so these breaking-change directives (and the existing preview-announcement selector that also usesPolicyDnsSecurityRule) won't apply toNew-AzDnsResolverPolicyDnsSecurityRule/Update-AzDnsResolverPolicyDnsSecurityRule. Update the subject matcher (e.g.,DnsResolverPolicyDnsSecurityRule, or a regex that matches the generated subject) so the intended breaking-change annotations are emitted on those cmdlets.