Add kudu warm up logic #497
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A kudu container can be run on a particular instance before the deployment so that it prevents deployment time out issues.
Algorithm
Get all app service instances using arm api.
Sort them
Get the first instance and call warm up api on this.
And set up the cookies.
Now all further calls will be going on this instance in further deployments also.
Exception: If publish profile is being used as a credential then arm call can not be made.
So we have to make warm up call and that will land on a random instance.
After that cookies will be set and further calls will land on the same instance.
But for further deployments this will be repeated so less optimized than spn case.
SPN

https://github.com/kumaraksh1/msdocs-python-flask-webapp-quickstart/actions/runs/21391031834/job/61591086242
Publish Profile

https://github.com/kumaraksh1/msdocs-python-flask-webapp-quickstart/actions/runs/21392678109/job/61590074943
Tests
