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

Solving issue with worksheets for catalog Dbs #1079

Merged

Conversation

TejasRGitHub
Copy link
Contributor

Feature or Bugfix

  • Bugfix

Detail

When using worksheet with a share made with a catalog account ( by using steps as described here in this PR - #1021 ) , the worksheet drop down list doesn't display the correct DB name. This is due to the fact that DB name is picked from the producer account ( where the S3 bucket is present and where the actualDB is not present ) which has the resource linked DB. Thus, the autogenerated querying doesn't work . Please refer to the screenshot
image

Also, on the share view, the db name mentioned on the query ( in the "Data Consumption details" ) is the resource linked DB name and not the correct DB name.

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)? No
    • 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? No
    • 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? No
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored? No
  • 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.

TejasRGitHub and others added 4 commits February 26, 2024 16:47
# Conflicts:
#	backend/dataall/modules/dataset_sharing/services/share_item_service.py
#	backend/dataall/modules/dataset_sharing/services/share_object_service.py
#	tests/modules/datasets/test_share.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.

lgtm - approving!

@noah-paige noah-paige merged commit 42a33a6 into data-dot-all:main Mar 4, 2024
8 checks passed
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