-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Add 2025-10-01-preview generation #28734
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
base: Az.DNSResolver-preview
Are you sure you want to change the base?
Add 2025-10-01-preview generation #28734
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 28734 in repo Azure/azure-powershell |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@jamesvoongms Please fix the test failures. |
|
@dolauli , could you help do the azp run again? There was some logic that was deleting my recordings so i have fixed the problem and re-recorded |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| westus2 sampleSecurityRule Microsoft.Network/dnsSecurityRules "00008cd5-0000-0800-0000-604016c90000" | ||
| ``` | ||
|
|
||
| This cmdlet creates a DNS security rule without a domain list. |
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.
Same issue here
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
…-resolver-2025-10-01
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
…-resolver-2025-10-01
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| @@ -1,26 +0,0 @@ | |||
| // Copyright (c) Microsoft Corporation. All rights reserved. | |||
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.
It seems this file is removed by mistake.
| --> | ||
| ## Upcoming Release | ||
| * Preannounced breaking changes. Please refer to https://go.microsoft.com/fwlink/?linkid=2333229 | ||
| * Add managedDomainList for usage in DnsSecurityRules |
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.
For changelogs, please use the past tense. So please use 'Added' and 'Removed'
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
Description
The PR makes the change from using 2025-05-01 to 2025-10-01-preview version as seen in the changeset:
Azure/azure-rest-api-specs#37724
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.