Skip to content

Tenant level Mappings Enhancement

harshit aggarwal requested to merge tenant-level-mappings-enhancements into master

This PR is enabling the tenant level mappings in wks service

Brief Summary of this enhancement

Current default mappings are defined from a given source and entity type to a target schema. Current mappings hold no information about the authority and schema version of source. These mappings are deployed in a shared context and accessible to all the tenants

These schemas and mapping should be accessible in tenant’s scope as well. Schema creation will be done using schema service. Mappings will be deployed in tenant context using mapping deployment script. (In future it will be done using a dedicated mapping service)

To support above feature the mappings needs have source schema authority information also.

Hence a mapping will now be defined from a given source schema kind (till major version) to a given target schema kind (till major version)

Please refer this doc for more details

Changes made through this MR

  • Updating existing logic to fetch mapping files (Both in wks-core and wks-azure modules)

  • Updating WKS Id generation logic (In wks-core)

  • Unit Tests are added to maintain healthy code coverage

  • New Integration Test scenario are added and existing scenarios are updated accordingly

  • Updating bootstrapping scripts to upload mapping records as well as mapping files

Edited by harshit aggarwal

Merge request reports