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 dataset module and specific s3_datasets module - part 4 (Create DatasetBaseRepository and move DatasetLock) #1276

Merged
merged 31 commits into from
May 21, 2024

Conversation

dlpzx
Copy link
Contributor

@dlpzx dlpzx commented May 16, 2024

Feature or Bugfix

⚠️ merge after #1258

  • Refactoring

Detail

As explained in the design for #1123 we are trying to implement a generic datasets_base module that can be used by any type of datasets in a generic way.

In this small PR:

  • we move the generic DatasetLock model to datasets_base
  • move the DatasetLock db operations to databasets_base DatasetBaseRepository
  • move activity to DatasetBaseRepository

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 added 30 commits May 6, 2024 14:33
…t-model-refactoring-2' into feat/generic-dataset-model-refactoring-3
…eric-dataset-model-refactoring-3

# Conflicts:
#	backend/dataall/modules/dataset_sharing/services/dataset_sharing_service.py
#	backend/dataall/modules/s3_datasets/api/dataset/resolvers.py
#	backend/dataall/modules/s3_datasets/db/dataset_models.py
#	backend/dataall/modules/s3_datasets/services/dataset_service.py
#	backend/dataall/modules/s3_datasets/services/dataset_table_service.py
…eric-dataset-model-refactoring-4

# Conflicts:
#	backend/dataall/modules/datasets_base/db/dataset_models.py
#	backend/dataall/modules/s3_datasets/db/dataset_repositories.py
#	tests/modules/datasets/test_dataset.py
#	tests/modules/datasets/test_dataset_resource_found.py
Copy link
Contributor

@noah-paige noah-paige left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tested update dataset and shares locally - changes look good

approving!

@dlpzx dlpzx merged commit d4915d1 into main May 21, 2024
9 checks passed
@dlpzx dlpzx deleted the feat/generic-dataset-model-refactoring-4 branch May 22, 2024 06:56
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.

None yet

2 participants