Routing guest Restore point requests to native path #1873
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 0011cd4.
arisettisanjana
requested review from
iamashwani-who,
mearvind and
vityagi
as code owners
arisettisanjana
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently the restore point request for a managed vm can either reach Xstore's Native or Managed Path. For managed disk storage accounts, Xstore is planning to block requests that land on managed path. So Including the port (8443) in snapshot request urls to route requests of managed disks to always land on native path.
To ensure that the request is for a managed Vm, checking if the request was created by CRP and this entire flow would be enabled based on the TTL config.