We request the introduction of a native SonarQube connector in the Harness Platform, similar to the existing native Nexus connector.

Currently, when creating a connector in Harness, a dedicated connector is available for Nexus. This allows administrators to centrally configure the Nexus endpoint, authentication details, connectivity through a Harness Delegate, validation, RBAC, and reuse of the connector across pipelines.

However, an equivalent native SonarQube connector is not available in the connector catalogue accessible to our licensed Harness modules. Consequently, teams must implement SonarQube integration through custom CI Run steps, SonarScanner commands, manually referenced secrets, API calls, or third-party/community plugins.

The current workaround can technically initiate a SonarQube scan, but it does not provide the same standardized, centrally governed connector experience available for other enterprise tools such as Nexus.

We need the "SonarQube" connector.