Fix CloudPath instantiation idempotency edge case#104
Merged
Conversation
jayqi
changed the title
Contributor
Codecov Report
@@ Coverage Diff @@
## master #104 +/- ##
========================================
- Coverage 91.7% 91.4% -0.3%
========================================
Files 8 8
Lines 668 680 +12
========================================
+ Hits 613 622 +9
- Misses 55 58 +3
|
pjbull
approved these changes
Nov 9, 2020
Member
|
🕺 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
CloudPath instantiation will use the same client as passed in CloudPath instance if a client is not explicitly specified. This was the only issue that made instantiation not idempotent in the case of using a non-default client.
Resolves #89