Skip to content
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

Generic shares_base module and specific s3_datasets_shares module - part 8 (share_item_service) #1350

Merged
merged 1 commit into from
Jun 19, 2024

Conversation

dlpzx
Copy link
Contributor

@dlpzx dlpzx commented Jun 19, 2024

Feature or Bugfix

  • Refactoring

Detail

As explained in the design for #1123 and #1283 we are trying to implement generic datasets_base and shares_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_servicelogic into the a generic service in shares_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 on
OWASP 10.

  • Does this PR introduce or modify any input fields or queries - this includes
    fetching data from storage outside the application (e.g. a database, an S3 bucket)?
    • Is the input sanitized?
    • What precautions are you taking before deserializing the data you consume?
    • Is injection prevented by parametrizing queries?
    • Have you ensured no eval or similar functions are used?
  • Does this PR introduce any functionality or component that requires authorization?
    • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
    • Are you logging failed auth attempts?
  • Are you using or adding any cryptographic features?
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored?
  • Are you introducing any new policies/roles/users?
    • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dlpzx
Copy link
Contributor Author

dlpzx commented Jun 19, 2024

I tested locally that everything loads as usual , that the ShareItemService is reachable (by clicking in verify items) and that the S3ShareItemService is used in the sharing (by revoking a folder, the delete_permissions is called)

@dlpzx dlpzx merged commit dda4153 into main Jun 19, 2024
9 checks passed
@dlpzx dlpzx changed the title Generic shares_base module and specific s3_datasets_shares module - part 8 (sharei_item_service) Generic shares_base module and specific s3_datasets_shares module - part 8 (share_item_service) Jun 20, 2024
@dlpzx dlpzx deleted the feat/generic-dataset-sharing-8 branch June 26, 2024 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants