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

fix: openapi schema for agent #2838

Merged
merged 2 commits into from
Jan 25, 2025
Merged

Conversation

Flo4604
Copy link
Contributor

@Flo4604 Flo4604 commented Jan 25, 2025

What does this PR do?

The openapi schema got changed in a recent commit which errors out the tests

--- FAIL: TestRatelimit (0.02s)

valerr: Error: POST Path '/ratelimit.v1.RatelimitService/Ratelimit' not found, Reason: The POST request contains a path of '/ratelimit.v1.RatelimitService/Ratelimit' however that path, or the POST method for that path does not exist in the specification
    handler_test.go:26: 
        	Error Trace:	/home/runner/work/unkey/unkey/apps/agent/pkg/api/routes/v1_ratelimit_ratelimit/handler_test.go:26
        	Error:      	Not equal: 
        	            	expected: 200
        	            	actual  : 400
        	Test:       	TestRatelimit

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • [] Chore (refactoring code, technical debt, workflow improvements)
  • [] Enhancement (small improvements)
  • [] New feature (non-breaking change which adds functionality)
  • [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [] This change requires a documentation update

How should this be tested?

Switch to apps/agent and run go test -cover -v -json -timeout=60m -failfast ./pkg/... ./services/... | tparse -all -progress and see if TestRatelimit passes.

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Unkey Docs if changes were necessary

Summary by CodeRabbit

  • API Changes
    • Updated rate limiting endpoint path and operation ID to improve versioning and service naming conventions
    • Maintained existing rate limiting functionality and request/response schemas

Copy link

changeset-bot bot commented Jan 25, 2025

⚠️ No Changeset found

Latest commit: 37a6352

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Jan 25, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 25, 2025 3:03pm

Copy link

vercel bot commented Jan 25, 2025

@Flo4604 is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Jan 25, 2025

📝 Walkthrough

Walkthrough

The pull request involves updating the OpenAPI specification for the Unkey API, specifically modifying the rate limiting endpoint path and operation ID. The changes rename the endpoint from "/v1/ratelimit.limit" to "/ratelimit.v1.RatelimitService/Ratelimit" and update the corresponding operation ID from "v1.ratelimit.limit" to "ratelimit.v1.ratelimit". These modifications align the API structure with improved versioning and service naming conventions while maintaining the existing functionality of the rate limiting endpoint.

Changes

File Change Summary
apps/agent/pkg/openapi/openapi.json - Updated rate limit endpoint path from "/v1/ratelimit.limit" to "/ratelimit.v1.RatelimitService/Ratelimit"
- Modified operation ID from "v1.ratelimit.limit" to "ratelimit.v1.ratelimit"

Possibly related PRs

Suggested reviewers

  • chronark

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b1820e2 and 37a6352.

📒 Files selected for processing (1)
  • apps/agent/pkg/openapi/openapi.json (1 hunks)
🔇 Additional comments (1)
apps/agent/pkg/openapi/openapi.json (1)

626-628: LGTM! The endpoint path and operation ID changes align with the service naming convention.

The changes follow the established pattern used by other service endpoints (e.g., VaultService) in the specification, making the API structure more consistent.

Let's verify if there are any clients still using the old endpoint path:


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. (Beta)
  • @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
Contributor

github-actions bot commented Jan 25, 2025

Thank you for following the naming conventions for pull request titles! 🙏

@chronark chronark merged commit 4d3e281 into unkeyed:main Jan 25, 2025
6 of 9 checks passed
@Flo4604 Flo4604 deleted the fix/agent-test-error branch January 25, 2025 15:50
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