-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[Do Not Merge]Adding Cmdlet New-AzApplicationGatewayRewriteRuleUrlConfiguration to support url rewrite capability for V2 application gateways #10097
Conversation
Co-Authored-By: Mark Cowlishaw <[email protected]>
Add tooling documentation for Tools.Common, StaticAnalysis, and CI Filter
…Application Gateway
Can one of the admins verify this patch? |
Changes made in according with NRP 127 (2019-08-01) and targetting network-september branch and need to release by Oct 15. Please verify the milestone and update if it is wrong. Update: Should not be released as a part of OCT 15. |
src/Network/Network/help/New-AzApplicationGatewayRewriteRuleUrlConfiguration.md
Outdated
Show resolved
Hide resolved
@@ -973,6 +973,262 @@ function Test-ApplicationGatewayCRUDRewriteRuleSetWithConditions | |||
} | |||
} | |||
|
|||
function Test-ApplicationGatewayCRUDRewriteRuleSetWithUrlConfiguration |
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.
Can you test your changes in existing test function like ApplicationGatewayCRUDRewriteRuleSet
or ApplicationGatewayCRUDSubItems
? I'm concerned that there are a lot of very similar tests in AppGw when each of them takes about 30 minutes to run
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 v2 gateways, any update should take maximum 5 mins. In this test, there are two create/update hence it will take maximum 10-12 minutes. You must be seeing 30 mins in the test cases when there are many creates/updates. We have around 20 mins time for V1 gateways so you might see high test running time for V1 gateways.
Is there any check in gate where these tests run in record mode? I won't mind adding each tests with different scenario if they are running locally only and check in gates run the playback tests.
I agree that there are many tests which can be merged into single test like RewriteRuleCRUD and RewriteRuleCRUDwithConditions. I think it would be better to open a work item on AppGW team to merge them and it should not be the part of this PR.
Apart from that, it would require making changes in the existing test cases which would require loop from the tests author itself to avoid any potential assert missing.
@number213 Checks are still failing. Can you point me the reason? Is it related to checkin of local sdk? |
@abjai right now there are two issues
|
This should not be released as the part of October 15 release. We have reverted the swagger changes as well. However we want to continue with the PR so that we can release it as a part of later milestone. |
Closing for now. When you're ready please rebase against release branch and re-open |
Description
This should not be released as a part of October 15 release
Adding Support for UrlConfiguration under RewriteRuleActionset for Application Gateway Url Rewrite Feature
Checklist
CONTRIBUTING.md
ChangeLog.md
file(s) has been updated:ChangeLog.md
file can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
## Upcoming Release
header -- no new version header should be addedPowershell design review link: https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/339
Swagger link:
Azure/azure-rest-api-specs#7030
Azure/azure-rest-api-specs#7275