Fix databricks_share update logic
#2022
Merged
Conversation
This file contains 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
|
acceptance tests passed |
nkvuong
force-pushed
the
fix/delta-sharing-update
branch
from
0216eb7
to
b8b86a2
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2022 +/- ##
=======================================
Coverage 89.51% 89.52%
=======================================
Files 140 140
Lines 11039 11043 +4
=======================================
+ Hits 9882 9886 +4
Misses 767 767
Partials 390 390
|
nfx
approved these changes
Feb 21, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Current logic only sends update if a new share name is added/removed.
This PR compares the properties of a share and send the appropriate update payload as well