-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Remove non sensitivity for DDoS ruleset #28757
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
Remove non sensitivity for DDoS ruleset #28757
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 |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
To the author of the pull request, |
|
@baoqihuang0326 There are breaking changes detected that have not been preannounced. Either target the next breaking change window May 2026, or make sure the PR contains no breaking change. Check the log of the static analysis pipeline for details. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Do we need to add tests here https://github.com/Azure/azure-powershell/tree/main/src/Network/Network.Test/ScenarioTests |
|
Can you confirm if you can set DDoS RuleSet as RuleSet Type in PS |
|
Have we tested generated cmdlets once E2E to ensure all steps to set up DDoS Rule Set work E2E |
|
Sample tests azure-powershell/src/Network/Network.Test/ScenarioTests/ApplicationGatewayTests.ps1 Line 4204 in 098c011
|
|
Please check Shawn's PR for tests and lets add similar one for sensitivity and ruleset type https://github.com/Azure/azure-powershell/pull/25705/files#diff-e25e8ac41faf3f4f48ae0c984fae653f6551d79ff413c6c54ebfcb5f6a5fd567 |
We already have test case for the normal Sensitivity. I don't think we should add test for None Sensitivity which we are planning to remove it. |
|
same comment as above, pls add a unit test would return error if the field is none for sensitivity |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@microsoft-github-policy-service agree company="Microsoft" |
@microsoft-github-policy-service agree company="Microsoft" |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Description
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.