Notes
NOTE When review a holistics PR, I want to:
- View detailed change of dashboard: semantically what has been changed?
- Dashboard: which part of dashboard is changed (new filter/widget, move position, filter mapping)
- View detailed change of dashboard: semantically what has been changed?
Tasks
Partly today
- ((69e49c4a-0521-427f-8298-04b39bb5004d))
- ((69a2a1cc-fc1f-4802-ba56-48183fa9e9a5))
Done
- DONE Shorten dbt README
DONE Bicycle Transit questions
- Question: support for?
- Data source: Microsoft Fabric Data Warehouse
- At the moment, no. But we already have existing components in our system: SQL Server (without local SQL account) and Entra ID.
- Ask modeling team (anh Huy Vu, engineer) is it quick to support this? Since Bicycle Transit guys said “Entra ID is the only auth method for Azure databases, which nobody (Rill, Omni) does not provide yet”.
- SSO: Microsoft Entra ID / Azure AD SSO
- We already support Azure AD for SSO.
- FYI: Azure AD and Entra ID are the same, Entra ID is just rebranded in mid-2023.
- ((69fd5491-aaac-4137-92f4-170378c38911))
- Azure DevOps
- Azure DevOps no per-repo deploy key. SSH key sit on user account, not repo. So BTS need dedicated service user, grant permission on target repo only, paste our pubkey into that user’s SSH Public Keys page.
- Not a hack. Standard pattern. Valohai, Flux CD, ArgoCD all document same approach for Azure DevOps. BTS devops team will recognize.
- More catches:
- Azure DevOps RSA only (rsa-sha2-256/512). No Ed25519. Need confirm what algo our generator emits.
- SSH URL format:
[email protected]:v3/<org>/<project>/<repo>. Confirm “Other/SSH” dialog parse it ok. - No PR Workflow parity. GitHub App-only feature. PRs handled outside Holistics.
- Data source: Microsoft Fabric Data Warehouse
- Question: support for?
DONE fix(calendly): use unique_combination_of_columns for
dom_calendly__bookingsDONE Update docs to mention Entra ID