fix(e2e): re-add powerbi e2e tests

[harshsoni2024]

Describe your changes:

• re-adding powerbi e2e tests

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

High-level design:

N/A — small change.

Tests:

Use cases covered

Unit tests

Backend integration tests

Ingestion integration tests

Playwright (UI) tests

Manual testing performed

UI screen recording:

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• My PR is linked to a GitHub issue via Fixes #<issue-number> above.
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
• For a UI feature or feature task: as part of PR creation, I ran the PR build in Docker with sample data and embedded a verified GitHub-hosted recording plus build/health evidence above (or explained why this requirement is not applicable).
• I have added tests (unit / integration / Playwright as applicable) and listed them above.
• Decision check: if this PR decides something the next contributor could undo — a schema field, REST path or format another component or repo must agree with, a new default or limit, an ordering that must hold, or a rule stated only in this description — it adds a record under docs/decisions/ (see its README.md). This description is gone from git log after the squash-merge.

---

Summary by Gitar

• CI changes:
  • Added powerbi to the default E2E test matrix in py-cli-e2e-tests.yml
• Configuration:
  • Renamed dbServiceNames to dbServicePrefixes under lineageInformation in powerbi.yaml

_{This will update automatically on new commits.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

• No GitHub issue is linked. Link an issue in the Development section of the PR (or add Fixes #12345 to the description). For a same-org cross-repo issue, add Fixes open-metadata/<repo>#123 to the description.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

[gitar-bot]

Code Review ✅ Approved

🟡 Medium risk · Adding Power BI to the default E2E matrix and changing its lineage config could expose workflows to test failures or incorrect lineage matching.

Re-adds PowerBI E2E tests by adding powerbi to the default matrix in py-cli-e2e-tests.yml and renaming dbServiceNames to dbServicePrefixes under lineageInformation in powerbi.yaml. No issues found.

Verification

Rules No rules evaluated

Functional validation Not enabled

Set up

Auto-approval Not enabled

Set up

_{For more verification details, comment gitar display:verbose.}

Options

Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ingestion'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[harshsoni2024]

e2e run result on pr branch: https://github.com/open-metadata/OpenMetadata/actions/runs/38716968345

[github-actions]

🚦 Removed from the merge queue — failed_checks (2026-10-15T21:57:27Z)

Blocked the queue: playwright-summary

• Prune dead merge-queue refs — cancel-stale-runs
• Postgresql PR Playwright E2E Tests — playwright-summary, playwright / playwright-ci (chromium-14)

Failed Playwright tests:

• Features/BulkEditEntity.spec.ts › Database Schema