-
Notifications
You must be signed in to change notification settings - Fork 3.4k
User/jimmyca/app configuration retry policy #33219
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
Open
jimmyca15
wants to merge
4
commits into
Azure:dev
Choose a base branch
from
jimmyca15:user/jimmyca/AppConfigurationRetryPolicy
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+22
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
0234185
Update retry policy to be more resilient toward temporary issues.
jimmyca15 7569026
At least two spaces before in-line comment.
jimmyca15 c8f6a39
Set retry count to a high number to handle how the retry policy ignor…
jimmyca15 e4d4305
Update comment.
jimmyca15 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
@ChristineWanjau I'm still not familiar with the cli test setup. Should we set these as module constants, then mock them out so we can have some tests for them.
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.
Regarding the cli test setup, currently we only have integration tests which are recorded http request/response pairs. They are then replayed in an automation environment without actually making any http calls. I don't think we can test retry in the integration tests since we can't trigger errors or record the retry behavior. https://github.com/Azure/azure-cli/blob/dev/doc/authoring_tests.md
We can also test the retries using mock unit tests. Although I am wondering how would that look like? Do we mock http responses to return 503s, 429s. The check if the retry policy works? What did you have in mind in terms of the tests?
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.
@mrm9084 , what is it that you would like to test? Testing the retry policy is out of scope. Did you want to have some tests that the client created in the internal method has the correct retry policy values via some assertion in the tests?
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.
I was just thinking we might want some sort of test on our retry policy. I hadn't put too much thought into it.