Multi-env Data Product Promotion Hub
Use EntiHub packages and CLI service principals to promote governed entity definitions and seed data across environments with less model drift.
Why this is needed
- Dev and prod entity YAML diverge silently.
- Manual UI clicks do not scale for platform teams.
- Data products need the same gates as application code.
Proposed entities in EntiHub
Governance settings
| Setting | Recommended value | Why |
|---|---|---|
approvalRequired |
true |
Prod package deploy is a controlled change. |
historyEnabled |
true |
Deploy history shows what was promoted when. |
allowSameAuthorApproval |
false |
Maker/checker separation for sensitive changes. |
deletedRetentionDays |
90 (or higher) |
Soft-delete retention for auditability. |
Entity definition (YAML sketch)
This use case is primarily an operating model on top of EntiHub packages:
# Example: package contents (conceptual)
# EntiHub-package.json
# entities/business_term.yaml
# entities/business_rule.yaml
# seed/business_term.json
Recommended entity flags for anything promoted to prod: approvalRequired: true, historyEnabled: true.
Use CLI:
entihub packages export --file knowledge-package.zip --json
entihub packages deploy --file knowledge-package.zip --json
YAML sketches
Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.
Sample data
| environment | package | contents | promoted_by | result |
|---|---|---|---|---|
| test | knowledge-package.zip | terms, rules, kpi defs | sp-entihub-ci | success |
| prod | knowledge-package.zip | terms, rules, kpi defs | sp-entihub-ci | success |
Benefits for the company
- Less drift between environments.
- CI/CD-friendly with service principal.
- Same gates for knowledge entities as for code.