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

Implement validate #40

Merged
merged 1 commit into from
Oct 7, 2024
Merged

Implement validate #40

merged 1 commit into from
Oct 7, 2024

Conversation

laurenleach
Copy link
Contributor

@laurenleach laurenleach commented Oct 4, 2024

Pull Request

To help us get this pull request reviewed and merged quickly, please be sure to include the following items:

  • Tests (if applicable)
  • Documentation (if applicable)
  • Changelog entry
  • A full explanation here in the PR description of the work done

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Tests
  • Other

Backward Compatibility

Is this change backward compatible with the most recently released version? Does it introduce changes which might change the user experience in any way? Does it alter the Connector in any way?

  • Yes (backward compatible)
  • No (breaking changes)

Useful links:

  • [https://github.com/ConductorOne/baton-sdk/wiki/Coding-Guidelines](Baton SDK coding guidelines)
  • [https://github.com/ConductorOne/baton/blob/main/CONTRIBUTING.md](New contributor guide)

Issue Linking

What's new?

  • Implement Validate method to ensure that the connector is properly configured and has a valid personal access token

Summary by CodeRabbit

  • New Features

    • Introduced a method to retrieve information about the authenticated user from the Jira API.
    • Enhanced the validation process to check API credentials by invoking the new user information method.
  • Bug Fixes

    • Updated the validation method to ensure proper handling of API credential checks.

Copy link

coderabbitai bot commented Oct 4, 2024

Walkthrough

The changes introduce a new method Myself in the Client struct of the pkg/client/client.go file, which constructs an HTTP request to retrieve information about the authenticated user from the Jira API. Additionally, a constant myself is defined for the endpoint. In the pkg/connector/connector.go file, the Validate method is modified to call the Myself method, altering its return statement to include a check for API credentials or connector configuration.

Changes

File Change Summary
pkg/client/client.go Added constant myself and method func (client *Client) Myself(ctx context.Context) error.
pkg/connector/connector.go Modified Validate method return statement to nil, d.jiraClient.Myself(ctx).

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant JiraAPI
    participant Connector

    Client->>JiraAPI: GET /myself
    JiraAPI-->>Client: User Info
    Connector->>Client: Validate
    Client->>Connector: Call Myself
    Connector-->>Client: Validation Result
Loading

🐰 In the code, a new method hops,
To fetch user info, it never stops.
The connector checks with a gentle call,
Validating all, it ensures no fall.
With each change, our code does bloom,
A better path, dispelling gloom! 🌼


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 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

@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: 1

🧹 Outside diff range and nitpick comments (2)
pkg/connector/connector.go (1)

49-49: Approve the changes with minor suggestions.

The modification to the Validate method is a good improvement. It now actually tests the Jira client's ability to make an API call, which aligns with the PR objective of ensuring the connector is properly configured and has a valid personal access token.

Consider the following minor improvements:

  1. Add some logging before and after the API call for better observability.
  2. Consider returning a non-nil Annotations object with additional information about the validation process.

Example implementation:

func (d *Connector) Validate(ctx context.Context) (annotations.Annotations, error) {
    log.Println("Validating Jira connector...")
    _, err := d.jiraClient.Myself(ctx)
    if err != nil {
        log.Printf("Validation failed: %v", err)
        return nil, fmt.Errorf("failed to validate Jira connector: %w", err)
    }
    log.Println("Jira connector validated successfully")
    return annotations.Annotations{
        "status": "validated",
        "method": "Myself",
    }, nil
}

This implementation provides more context and improves error handling and observability.

pkg/client/client.go (1)

674-685: Implement a Validate method using Myself

The new Myself method (or the suggested GetCurrentUser method) can be used to implement the Validate method mentioned in the PR objectives. This method can check if the client is properly configured and has a valid personal access token.

Here's a suggested implementation for a Validate method:

func (client *Client) Validate(ctx context.Context) error {
    _, err := client.GetCurrentUser(ctx)
    if err != nil {
        return fmt.Errorf("failed to validate client: %w", err)
    }
    return nil
}

This method attempts to get the current user information. If successful, it confirms that the client is properly configured and authenticated. If you'd like me to implement this method or open a GitHub issue for tracking this task, please let me know.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b7f5ce0 and f2867f5.

📒 Files selected for processing (2)
  • pkg/client/client.go (2 hunks)
  • pkg/connector/connector.go (1 hunks)
🔇 Additional comments (1)
pkg/client/client.go (1)

80-80: LGTM: Constant addition for myself endpoint

The new constant myself is correctly defined and follows the existing naming convention for API endpoints in this file. It represents the Jira API endpoint for retrieving information about the authenticated user.

pkg/client/client.go Show resolved Hide resolved
@laurenleach laurenleach requested a review from btipling October 5, 2024 01:07
@laurenleach laurenleach merged commit 1adf0c3 into main Oct 7, 2024
3 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