Skip to content

Support for multiple servers in custom tools OpenAPI definition #10999

Closed as not planned
@guillaumemeyer

Description

@guillaumemeyer

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

As of today, if I want to debug a custom tool, I have to manually switch the server URL from the OpenAPI definition from one environment to another.
But it makes one environment unavailable during tests.

The alternative I've found is to create two custom tools, one per environment, and add a condition in a workflow like:

image

But this is prone to errors and makes workflows complex without a real reason.

The real answer would be to support multiple servers in the openapi definition:

  "servers": [
    {
      "url": "https://dev/v1.0",
      "description": "... (Dev)"
    },
    {
      "url": "https://prod/v1.0",
      "description": "... (Prod)"
    }
  ],

And be able to specify the server in the tool configuration as an input variable, like other operations parameters.
Bonus, if this input variable is not specified, the first server is used.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.

Metadata

Metadata

Assignees

No one assigned

    Labels

    💪 enhancementNew feature or request🔨 feat:toolsTools for agent, function call related stuff.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions