fix(airflow): add DriveService to ENTITY_CLASS_MAP

[AntoineGlacet]

Summary

• Add missing driveService entry to ENTITY_CLASS_MAP in common.py
• Add corresponding DriveService import

Problem

When attempting to deploy ingestion pipelines for DriveService entities (used by the new Drive/SharePoint connector), the workflow deployment fails with:

InvalidServiceException: Invalid Service Type: driveService

This happens because the ENTITY_CLASS_MAP dictionary in openmetadata-airflow-apis/openmetadata_managed_apis/workflows/ingestion/common.py was missing the driveService entry.

Root Cause

The build_source function uses ENTITY_CLASS_MAP to look up the entity class for a given service type. When driveService is passed (from ingestion_pipeline.service.type), the lookup returns None, triggering the InvalidServiceException.

Fix

Added the missing entry:

from metadata.generated.schema.entity.services.driveService import DriveService
# ...
ENTITY_CLASS_MAP = {
    # ...
    \"driveService\": DriveService,
    # ...
}

Testing

Tested manually with a custom SharePoint connector ingesting files and directories into OpenMetadata 1.11.8. After applying this fix, the ingestion pipeline deploys and runs successfully.

Fixes #25611"

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[gitar-bot]

🔍 CI failure analysis for b0d4975: All CI failures caused by missing 'safe to test' GitHub label - jobs blocked before running actual tests

Issue

All 11 CI job failures are caused by a missing GitHub label requirement, not code issues.

Root Cause

The CI pipeline requires the safe to test label to be applied to the PR before running any tests, builds, or checks. This is a gating mechanism implemented using the jesusvasquez333/verify-pr-label-action@v1.4.0 action that prevents untrusted code from consuming CI resources.

Each failing job follows this pattern:

1. The job starts and checks out the code
2. The label verification action runs
3. It finds the PR lacks the safe to test label
4. The action exits with an error: Error! This pull request does not contain any of the valid labels: ['safe to test']
5. The job fails before reaching actual tests/checks

Details

Affected Jobs:

• java-checkstyle (62826134570)
• py-checkstyle (62826134590)
• build-and-scan (62826134596, 62826134610)
• playwright-ci-postgresql (all 6 shards: 62826134601, 62826134603, 62826134606, 62826134608, 62826134611, 62826134613)
• airflow-apis-tests (62826134602)

Important: None of these jobs reached the actual code validation phase. The PR changes to openmetadata-airflow-apis/openmetadata_managed_apis/workflows/ingestion/common.py were never tested because the label check failed first.

This is a workflow policy control, not a code quality issue. The actual code changes (adding DriveService to ENTITY_CLASS_MAP) have not been validated yet by CI.

Code Review ✅ Approved

Clean, minimal bug fix that adds the missing DriveService registration to ENTITY_CLASS_MAP, following established patterns exactly. No issues found.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}