feat(reports): Using Superset as reporting tool frontend

[bashanlam]

Summary: Apache Superset Selected as Frontend

To enable analysis on lakehouse data extracted from the FASE application, the organization evaluated open-source BI tools Apache Superset and Metabase #283 across data modeling, visualization, RBAC, and authentication criteria.

While both platforms offer comparable data visualization and modeling features, internal security requirements heavily favored Apache Superset. The organization’s analytics platform mandates centralized identity integration (OIDC/SAML). The open-source version of Metabase only supports LDAP, API keys, and Google OAuth, failing internal standards. Choosing Superset ensures full compliance with institutional security architecture without sacrificing vital business intelligence capabilities.

Summary by CodeRabbit

• Documentation
  • Documented the architectural decision regarding reporting tool platform selection and evaluation criteria.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d591e9e9-0186-44c8-923f-65d936b42947

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR introduces ADR 0008, documenting the decision to adopt Apache Superset as the reporting-tool frontend. The decision compares Superset and Metabase across evaluation criteria and selects Superset based on superior authentication and identity integration alignment.

Changes

Superset Selection ADR

Layer / File(s)	Summary
Superset versus Metabase evaluation and decision docs-devel/system-architecture/adrs/0008-use-superset-as-reporting-tool-frontend.md	ADR records the evaluation of Superset versus Metabase as BI frontend replacements against modelling, visualisation, RBAC, and authentication criteria. Superset is accepted based on OIDC/SAML integration alignment with central identity standards and feature parity for reporting and visualisation.

Poem

🐰 A choice recorded, clear and bright,
Superset shines with OIDC light,
Where Metabase could not align,
The architecture's grand design!
One tool to rule the queries fair,
With identity woven with care.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: documenting the decision to use Apache Superset as the frontend reporting tool, which is the primary objective of this ADR addition.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@docs-devel/system-architecture/adrs/0008-use-superset-as-reporting-tool-frontend.md`:
- Around line 18-23: Change the Decision section from future to past tense to
reflect that the evaluation already occurred: replace the opening sentence "We
will evaluate both Apache Superset and Metabase as potential frontend
replacements for the legacy reporting tool." with a past-tense variant like "We
evaluated both Apache Superset and Metabase as potential frontend replacements
for the legacy reporting tool." and update any supporting verbs in the bullet
list to past tense (e.g., "This evaluation was conducted locally" and "Assess
and compare" → "Assessed and compared") so the Decision block and its bullets
consistently reflect a completed evaluation; edit the block referenced as
"Decision" in the ADR document to apply these changes.
- Line 31: Locate the "Consequences" section in the ADR document and replace the
heading or label text "Final Outcome:" with the shorter "Outcome:" (search for
the exact string "Final Outcome:" to find the occurrence); ensure any internal
references or links that point to "Final Outcome" are updated to the new label
if present so consistency is preserved.

🪄 Autofix (Beta)

✅ Autofix completed

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 078d1633-8b9f-4ada-8571-7bf4090dff77

📥 Commits

Reviewing files that changed from the base of the PR and between a889ca0 and 7d4f38c.

📒 Files selected for processing (1)

• docs-devel/system-architecture/adrs/0008-use-superset-as-reporting-tool-frontend.md

[coderabbitai]

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Fixes Applied Successfully

Fixed 1 file(s) based on 2 unresolved review comments.

Files modified:

• docs-devel/system-architecture/adrs/0008-use-superset-as-reporting-tool-frontend.md

Commit: b44ae7a180ce71df0f1b3131eff07d897bc5d4b2

The changes have been pushed to the reporting-tool-frontend branch.

Time taken: 2m 46s

[martyngigg]

Thanks for this. It reads well and covers all the points.