Onboarding Process to Data Rules is by
...
Request
Onboarding is a required step and performed by R&D/Data Rules team for every required tenant.https://eagleinvsys.atlassian.net/wiki/spaces/MC2/pages/3315138607/Data+Rules+Tenant+Onboarding
Supported use cases:
Eagle clients, that will use Core Resources with no customizations
Eagle clients, that will use Core Resources + Extensions off Core Resources or Eagle tables
Custom Oracle and Snowflake tables
Data Rules Core implementation - Is required for Eagle Clients, who want to move their data to Vaulthttps://eagleinvsys.atlassian.net/wiki/spaces/SOLUTIONSDEL/pages/3693215818/Data+Rules+Resource+. See Data Rules Resource Availability
All Core Inflow resources are available after Dara Rules deployment to specific tenant via Metadata API:
https://apps.sd.dev.az.eagleinvsys.com/api/vault/metadata/api/doc#/full-update/fullupdate
...
Data Rules Core deployment is required: https://apps.sd.dev.az.eagleinvsys.com/api/vault/metadata/api/doc#/full-update/fullupdatehttps://eagleinvsys
.atlassian.net/wiki/spaces/SOLUTIONSDEL/pages/3454730431/Data + Rules +Extensions+a+stepExtensions: A Step-by-step+guideStep Guide
Define metadata/ontology based on Eagle data for extension on Eagle/Oracle side
Generate Processing rules
Create Extension of Core Resource for Vault tenant
Generate DDL
Generate Processing Rules
...
Create a custom EDS object in Eagle
Run EDS extract in Eagle
Use Schema Drift functionality in AUTO_APPROVE mode - new resource will be created automatically in Vault and the following steps will be executed:
generate ontology for new resource
generate processing rule
execute DDL
publish data models
load data into new table
https://eagleinvsys.atlassian.net/wiki/spaces/SOLUTIONSDEL/pages/3495919683/Schema+drift Schema Drift