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

feat(ingest): Support config variable for specifying a direct privat… #6609

Merged

Conversation

mayurinehate
Copy link
Collaborator

@mayurinehate mayurinehate commented Dec 2, 2022

…e key

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Dec 2, 2022
@github-actions
Copy link

github-actions bot commented Dec 2, 2022

Unit Test Results (metadata ingestion)

       8 files         8 suites   58m 29s ⏱️
   765 tests    763 ✔️ 2 💤 0
1 532 runs  1 527 ✔️ 5 💤 0

Results for commit 604e57e.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Dec 2, 2022

Unit Test Results (build & test)

621 tests  ±0   617 ✔️ ±0   15m 33s ⏱️ -49s
157 suites ±0       4 💤 ±0 
157 files   ±0       0 ±0 

Results for commit 604e57e. ± Comparison against base commit 4f7b5ac.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@treff7es treff7es left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Collaborator

@hsheth2 hsheth2 left a comment

Choose a reason for hiding this comment

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

one nit but LGTM other than that

raise ValueError(
f"'private_key_path' was none "
f"but should be set when using {v} authentication"
f"Both `private_key` and `private_key_path` are none. "
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: i see that we're throwing the error below, but ideally we should just be doing the error checking in one place

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes. This is the main place I intend to keep error checking at. The assertion in below method was added primarily for linter.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

To remove the assert, we can add if.. elif.. , however assert seemed cleaner to me.

@anshbansal anshbansal merged commit fdcb731 into datahub-project:master Dec 5, 2022
cccs-Dustin pushed a commit to CybercentreCanada/datahub that referenced this pull request Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ingestion PR or Issue related to the ingestion of metadata
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants