Generic shares_base module and specific s3_datasets_shares module - part 8 (share_item_service) #1350
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
As explained in the design for #1123 and #1283 we are trying to implement generic
datasets_base
andshares_base
modules that can be used by any type of datasets and by any type of shareable object in a generic way.The goal of this PR is to split the
share_item_service
logic into the a generic service inshares_base
and an specific service in s3_datasets_shares.ShareItemService
in shares_base only has shareItem logic without references to S3 or Glue.S3ShareItemService
in s3_datasets_shares has logic for share items that are tables and folders.The files' names are a bit messy but i don't want to pollute this PR with more changes. I'll do a review of the file names in part 10.
Relates
Security
Please answer the questions below briefly where applicable, or write
N/A
. Based onOWASP 10.
fetching data from storage outside the application (e.g. a database, an S3 bucket)?
eval
or similar functions are used?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.