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: oauth support in databricks source #1911

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

shekhar-rudder
Copy link
Member

@shekhar-rudder shekhar-rudder commented Feb 26, 2025

What are the changes introduced in this PR?

  • Added a new dropdown field, authenticationType, to allow selection between PAT and OAuth authentication.
  • Introduced two new fields, oauthClientId and oauthClientSecret, which are displayed only when OAuth authentication is selected.
  • Updated the rendering logic for the token field to be shown only when PAT authentication is chosen.

What is the related Linear task?

Resolves INT-XXX

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new checks got introduced or modified in test suites. Please explain the changes.

N/A


Developer checklist

  • My code follows the style guidelines of this project

  • No breaking changes are being introduced.

  • All related docs linked with the PR?

  • All changes manually tested?

  • Any documentation changes needed with this change?

  • I have executed schemaGenerator tests and updated schema if needed

  • Are sensitive fields marked as secret in definition config?

  • My test cases and placeholders use only masked/sample values for sensitive fields

  • Is the PR limited to 10 file changes & one task?

Reviewer checklist

  • Is the type of change in the PR title appropriate as per the changes?

  • Verified that there are no credentials or confidential data exposed with the changes.

Summary by CodeRabbit

  • New Features
    • Introduced an authentication type selector enabling users to choose between "Personal Access Token" and "M2M OAuth."
    • Added conditional credential fields for OAuth, including client ID and client secret with validation and enhanced security measures for sensitive inputs.

Copy link

coderabbitai bot commented Feb 26, 2025

Walkthrough

This update modifies the Databricks UI configuration. The changes update the secretFields list to mark both the existing "token" and the new "oauthClientSecret" as sensitive. Additionally, a new "Authentication Type" field is added, letting users choose between "Personal Access Token" (PAT) and "M2M OAuth" (default: "oauth"). Conditional requirements now enforce that the "Token" field is needed for PAT, while the "Client ID" and "Client secret" fields (with validation) become necessary for OAuth.

Changes

File Change Summary
src/configurations/.../databricks/ui-config.json - Updated secretFields to include "oauthClientSecret" alongside "token".
- Added "Authentication Type" (singleSelect) with default "oauth".
- Modified "Token" field to require authentication type "pat".
- Introduced "Client ID" and "Client secret" fields with regex validations and error messages.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UI
    participant ConfigHandler

    User->>UI: Open Databricks configuration
    UI->>ConfigHandler: Load ui-config.json
    ConfigHandler-->>UI: Return configuration with authentication type options
    User->>UI: Select "Personal Access Token"
    UI->>ConfigHandler: Validate Token field requirement
    ConfigHandler-->>UI: Display Token field only
    User->>UI: Switch to "M2M OAuth"
    UI->>ConfigHandler: Enforce OAuth validations
    ConfigHandler-->>UI: Display Client ID & Client secret fields
Loading

Poem

I'm a rabbit with a joyful beat,
Hopping through config changes oh so neat.
Secrets guarded like treasures in a burrow,
OAuth and PAT make me cheer and furrow.
Leaping forward with a twitch of delight! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Feb 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (fe22b4b) to head (38e16fa).

Additional details and impacted files
@@            Coverage Diff            @@
##           develop     #1911   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           53        53           
  Branches         7         7           
=========================================
  Hits            53        53           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/configurations/sources/databricks/ui-config.json (1)

92-105: Addition of Client Secret Field for OAuth
This segment introduces the "Client secret" field with the necessary validations and marks it as sensitive ("secret": true). The prerequisite condition ensures it is only required when OAuth is selected. Although the regex pattern and error message are functionally correct, you might consider refining the error message to provide more specific guidance to end users in case of invalid input.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fe22b4b and 38e16fa.

📒 Files selected for processing (1)
  • src/configurations/sources/databricks/ui-config.json (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java-kotlin)
🔇 Additional comments (4)
src/configurations/sources/databricks/ui-config.json (4)

5-5: Sensitive Field Update for OAuth Client Secret
Adding "oauthClientSecret" to the "secretFields" array ensures that the new OAuth client secret is properly treated as sensitive data. This change is consistent with the new OAuth support and helps prevent accidental exposure of credentials.


44-62: Addition of Authentication Type Dropdown
The new "Authentication Type" field (of type "singleSelect") correctly offers the options to choose between Personal Access Token (PAT) and M2M OAuth. Setting the default to "oauth" aligns with the PR’s objective of introducing OAuth support. The configuration ensures that subsequent credential fields can be conditionally rendered based on the selected authentication method.


63-77: Conditional Rendering for the Token Field
Modifying the "Token" field to include "inputFieldType": "password" and adding the "preRequisiteField" condition ("authenticationType": "pat") ensures that this field is only displayed when the PAT method is selected. This improves the UI clarity by hiding unnecessary fields when OAuth is being used.


78-91: Addition of Client ID Field for OAuth
The newly added "Client ID" field, complete with its regex validation and prerequisite condition ("authenticationType": "oauth"), is a solid addition for supporting OAuth. The regex pattern ensures a minimum input length of 1 character and limits the input to 100 characters, which is appropriate for most client IDs.

@shekhar-rudder shekhar-rudder added the DO NOT MERGE Approved but need to check more label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DO NOT MERGE Approved but need to check more
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant