Skip to content

Conversation

@baoqihuang0326
Copy link

@baoqihuang0326 baoqihuang0326 commented Oct 27, 2025

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

@azure-client-tools-bot-prd
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@dolauli dolauli added the Contains Breaking Change This PR contains breaking change label Oct 30, 2025
@github-actions
Copy link

To the author of the pull request,
This PR was labeled "Contains Breaking Change" because breaking changes have been detected by the static analysis pipeline.

  • According to our policy, breaking changes can only take place during major release and they must be preannounced.
  • Please follow our guide on the detailed steps.
  • Required: Please fill in the task below to facilitate our contact,you will receive notifications related to breaking changes.

@dolauli
Copy link
Contributor

dolauli commented Oct 30, 2025

@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.

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@dedhar
Copy link
Contributor

dedhar commented Oct 30, 2025

@dedhar
Copy link
Contributor

dedhar commented Oct 30, 2025

Can you confirm if you can set DDoS RuleSet as RuleSet Type in PS

@dedhar
Copy link
Contributor

dedhar commented Oct 30, 2025

Have we tested generated cmdlets once E2E to ensure all steps to set up DDoS Rule Set work E2E

@dedhar
Copy link
Contributor

dedhar commented Oct 30, 2025

Sample tests

$ddosmanagedRuleSet = New-AzApplicationGatewayFirewallPolicyManagedRuleSet -RuleSetType "Microsoft_HTTPDDoSRuleSet" -RuleSetVersion "1.0" -RuleGroupOverride $ruleGroupOverrideEntry

@dedhar
Copy link
Contributor

dedhar commented Oct 30, 2025

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

@baoqihuang0326
Copy link
Author

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.

@Shawnli222
Copy link
Contributor

Shawnli222 commented Oct 30, 2025

same comment as above, pls add a unit test would return error if the field is none for sensitivity

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@baoqihuang0326
Copy link
Author

@microsoft-github-policy-service agree company="Microsoft"

@baoqihuang0326
Copy link
Author

@baoqihuang0326 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

@isra-fel
Copy link
Member

isra-fel commented Nov 1, 2025

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

isra-fel commented Nov 3, 2025

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

isra-fel commented Nov 3, 2025

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

isra-fel commented Nov 3, 2025

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@dolauli dolauli merged commit f76dd2a into Azure:release-network-2025-03-01 Nov 4, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Contains Breaking Change This PR contains breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants