Skip to content

Options: Rename CRATEDB_MCP_HTTP_URL to CRATEDB_CLUSTER_URL#21

Merged
amotl merged 1 commit intomainfrom
cratedb-cluster-url
May 19, 2025
Merged

Options: Rename CRATEDB_MCP_HTTP_URL to CRATEDB_CLUSTER_URL#21
amotl merged 1 commit intomainfrom
cratedb-cluster-url

Conversation

@amotl
Copy link
Member

@amotl amotl commented May 16, 2025

About

CrateDB Toolkit started to standardize on common naming conventions. In this case, its Cluster API and many subsystems it supports now understand the CRATEDB_CLUSTER_URL environment variable. This patch also uses the same name here.

... standardizing on common naming conventions.
@coderabbitai
Copy link

coderabbitai bot commented May 16, 2025

Walkthrough

The changes update the environment variable used to configure the CrateDB instance URL from CRATEDB_MCP_HTTP_URL to CRATEDB_CLUSTER_URL across documentation and code. This includes updates to documentation files and the relevant environment variable lookup in the settings module. No other logic or functionality was modified.

Changes

File(s) Change Summary
CHANGES.md, README.md Updated documentation to reference CRATEDB_CLUSTER_URL instead of CRATEDB_MCP_HTTP_URL in all instructions.
cratedb_mcp/settings.py Changed environment variable for HTTP URL from CRATEDB_MCP_HTTP_URL to CRATEDB_CLUSTER_URL.

Poem

A hop, a skip, a variable's name,
From MCP to Cluster, it's never the same.
Docs and code now both align,
With URLs set, all works just fine.
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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

@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 (2)
README.md (1)

94-103: Consider adding a migration note for existing users.

For users who might be currently using the old environment variable name, consider adding a transition note mentioning that CRATEDB_MCP_HTTP_URL is no longer supported and should be replaced with CRATEDB_CLUSTER_URL.

cratedb_mcp/settings.py (1)

6-6: Consider backward compatibility options.

Since this is a breaking change for users who have set CRATEDB_MCP_HTTP_URL in their environment, consider one of these approaches:

  1. Add a fallback to check the old environment variable if the new one isn't set
  2. Add a deprecation warning when detecting the old variable

Example implementation with fallback:

-HTTP_URL: str = os.getenv("CRATEDB_CLUSTER_URL", "http://localhost:4200")
+HTTP_URL: str = os.getenv("CRATEDB_CLUSTER_URL", os.getenv("CRATEDB_MCP_HTTP_URL", "http://localhost:4200"))

Example with deprecation warning:

-HTTP_URL: str = os.getenv("CRATEDB_CLUSTER_URL", "http://localhost:4200")
+old_url = os.getenv("CRATEDB_MCP_HTTP_URL")
+if old_url:
+    warnings.warn(
+        "Environment variable `CRATEDB_MCP_HTTP_URL` is deprecated and will be removed in a future version. "
+        "Use `CRATEDB_CLUSTER_URL` instead.",
+        category=DeprecationWarning,
+        stacklevel=2,
+    )
+HTTP_URL: str = os.getenv("CRATEDB_CLUSTER_URL", old_url or "http://localhost:4200")
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b1e4718 and 64b0881.

📒 Files selected for processing (3)
  • CHANGES.md (1 hunks)
  • README.md (2 hunks)
  • cratedb_mcp/settings.py (1 hunks)
🔇 Additional comments (6)
CHANGES.md (1)

4-5: Changelog entry correctly documents the environment variable renaming.

The entry clearly states both the old and new environment variable names and provides context about standardizing naming conventions.

README.md (4)

94-94: Environment variable name consistently updated in documentation.

The main configuration instruction has been updated to use the new environment variable name.


99-99: Example for CrateDB Cloud updated to use new environment variable.

The export example for cloud connections has been correctly updated to use CRATEDB_CLUSTER_URL.


102-102: Example for localhost updated to use new environment variable.

The export example for localhost connections has been correctly updated to use CRATEDB_CLUSTER_URL.


132-132: Claude Desktop JSON configuration updated to use new environment variable.

The Anthropic Claude Desktop configuration example has been correctly updated to use CRATEDB_CLUSTER_URL.

cratedb_mcp/settings.py (1)

6-6: Environment variable correctly renamed in code.

The environment variable has been updated from CRATEDB_MCP_HTTP_URL to CRATEDB_CLUSTER_URL while maintaining the same default value and variable name, which minimizes impact on the rest of the codebase.

@amotl amotl marked this pull request as ready for review May 16, 2025 20:43
@amotl
Copy link
Member Author

amotl commented May 17, 2025

@coderabbitai: Thanks for your suggestions about adding backward compatibility or emphasizing adjustments to option names: The project is still in its infancy, and the change log item has all relevant information. We think it is sufficient for this very early alpha state of the project.

@coderabbitai
Copy link

coderabbitai bot commented May 17, 2025

Tip

For best results, initiate chat on the files or code changes.

@amotl Thanks for providing that context! I completely understand your approach - for projects in early alpha stages, maintaining simplicity is often more valuable than implementing backward compatibility. The changelog entry you've included is indeed sufficient for communicating this change to users at this point in the project's lifecycle. I appreciate you sharing your reasoning.

🐰✨

Copy link
Member

@kneth kneth left a comment

Choose a reason for hiding this comment

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

It makes good sense to use the same environment variables. Maybe we should document them?

@amotl
Copy link
Member Author

amotl commented May 19, 2025

Maybe we should document the (designated) environment variables relevant for connecting to CrateDB?

I've just started using them after renaming another one the other day just recently. The only one that is of general purpose now, is CRATEDB_CLUSTER_URL. 1

https://cratedb-toolkit.readthedocs.io/search.html?q=CRATEDB_CLUSTER_URL

Can we agree on using it across all projects or snippets going forward? /cc @surister, @hlcianfagna, @hammerhead

Footnotes

  1. It has been called CRATEDB_SQLALCHEMY_URL beforehand.

@amotl amotl merged commit aa6e9b0 into main May 19, 2025
6 checks passed
@amotl amotl deleted the cratedb-cluster-url branch May 19, 2025 22:58
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