Container recreate retry policy Support for Cosmos DB Python SDK
Description
This PR adds a new retry policy for when a container is recreated. This works in tandem with the container cache, in which case this PR adds the functionality of refreshing the container properties cache when a container recreate happens. This fixes the issue from Issue 35294.
The retry works based on if there is a mismatch with the intended container RID with container RID from the service. If there is a RID mismatch then we refresh the container cache to match the one in the backend and retry the operation. This will result in the operation succeeding or failing normally with the correct container properties.
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).
/azp run python - cosmos - tests
Azure Pipelines successfully started running 1 pipeline(s).