CustomDrive pipeline deploy fails with `Invalid Service Type: driveService` (1.11.6)

[AntoineGlacet]

Summary

Deploying a Drive metadata ingestion pipeline for a CustomDrive service fails with Invalid Service Type: driveService during workflow generation.

Environment

• OpenMetadata: 1.11.6 (docker-compose)
• Ingestion: Airflow (managed by OM)
• Service type: CustomDrive

Steps to reproduce

1. Create a Drive Service with serviceType: CustomDrive.
2. Create a Drive Metadata ingestion pipeline for that service.
3. Deploy the pipeline via UI or API (POST /api/v1/services/ingestionPipelines/deploy/{id}).

Example service connection (CustomDrive):

{
  "type": "CustomDrive",
  "sourcePythonClass": "<custom_source_class>",
  "connectionOptions": {
    "tenantId": "...",
    "clientId": "...",
    "clientSecret": "...",
    "siteUrl": "https://.../sites/...",
    "siteName": "...",
    "libraryName": "Shared Documents",
    "extensions": ".csv,.xlsx,.xls"
  }
}

Actual behavior

Deploy fails with:

Failed to deploy Ingestion Pipeline due to airflow API returned Internal Server Error and response {"error": "Internal error while deploying due to [Failed to generate workflow [<pipeline_name>] verify config is correct: Invalid Service Type: driveService] "}

Expected behavior

CustomDrive pipelines should deploy successfully (service type should resolve to CustomDrive), and the workflow should be generated without error.

Notes

It looks like the deploy workflow generation uses the entity type driveService instead of the service type enum CustomDrive when validating the source, causing the invalid service type error.