Update request idle timeout range#9073
Conversation
|
Hi @Tratcher, |
️✔️Azure CLI Extensions Breaking Change Test
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation for the request_idle_timeout parameter to reflect the allowed range enforced by the underlying Azure Load Balancer. The change clarifies that the minimum value is 4 minutes (not 1) and adds a maximum value of 30 minutes.
- Updated parameter help text to specify correct minimum and maximum values for request idle timeout
CodeGen Tools Feedback CollectionThank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey |
|
Hi @Tratcher Release SuggestionsModule: containerapp
Notes
|
|
The CI failed due to Microsoft.Network update the api-version from |
Hi @Tratcher |
|
@Greedygre rebased |
|
Hi @yanzhudd |
This is the range allowed by the underlying azure load balancer.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az containerapp env premium-ingress add/update
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.