Dev

[Chenglong-MS]

This pull request introduces several improvements to the connector management experience, focusing on making advanced connection parameters less prominent, automating display name generation for connectors, and adding an API endpoint for renaming user connectors. The UI no longer prompts users for a connection name during creation; instead, a display name is auto-generated from key parameters, and users can rename connectors later if desired. Additionally, backend and API changes support these new behaviors.

Connector display name automation and API enhancements:

• Auto-generation of connector display names: The UI now derives a connector's display name automatically based on key connection parameters (e.g., host, database, project_id) using the new deriveConnectorDisplayName function in connectorNames.ts. Users are no longer prompted for a connection name during creation. [1] [2] [3] [4] [5] [6] [7] [8] [9]

• Backend support for renaming connectors: A new PATCH API endpoint (/api/connectors/<connector_id>) allows users to rename their connectors after creation, with validation and admin protections. [1] [2]

Parameter UI improvements:

• Advanced parameter labeling: Several connection parameters across various data loaders (e.g., port, endpoint, workgroup, output_location, location, query_timeout) are now marked as "advanced": true in their parameter definitions. This allows the UI to hide these fields by default, reducing clutter for most users. [1] [2] [3] [4] [5] [6] [7] [8] [9]

API and type updates:

• Connector type and display name fields: The backend now returns both type_name and display_name for connectors, and the frontend ConnectorInstance type reflects this. [1] [2]

These changes streamline the connector creation workflow, reduce user friction, and improve the clarity and management of connector display names.