Resolve dataset share checks when deleting dataset #554
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.
Feature or Bugfix
Detail
The
existingSharedItems
property ofShareObject
was not resolving correctly to aTrue
orFalse
value but rather toNone
. The impact is:When checking a dataset's shares before deleting the dataset - we would not raise an exception for datasets that did in fact have existing shared items.
Additionally, when deleting a dataset with associated shared objects created - we would not successfully delete the associated share object and share object items and not clean up rows in the DB appropriately. This caused issues when viewing the Share Tab as the dataset does not exist but is still referenced in the outdated ShareObject and throws an error.
Relates
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.