Overview:
- Currently, changes in schema are delivered via new builds of microservices that consume them
- Tracking and testing changes via new builds takes longer
Requirements:
- AAI should support the ability to centrally persist and serve schema updates
- AAI should support the ability to centrally persist and serve custom queries updates
- AAI should support the ability to provide schema documents via a loosely coupled REST contract
- AAI should support the ability to provide the schema via flexible document formats (OXM, TOSCA etc.)
- AAI should support the ability to provide a list of documents stored
- AAI should support the ability to provide an individual document
- AAI should support the ability to provide associations between documents (eg. an OXM and Edgerules
- AAI should support the ability to consume new schema dynamically, without downtime (eg. when distributed by SDC)
- AAI should support the ability to notify consumers of schema when new updates are available
Scope for Dublin:
R1-R7
Design:
- A mS will load all the schema (OXM and edge rules) at start up
- A mS will load all the custom queries at start up
- The mS will provide REST endpoints such as GET /aai/schema-service/v1....... following the semantic versioning guidelines
- The REST endpoiint support a format query parameter which will describe what format it is requested in eg. GET /aai/schema-service/v1/nodes?version={version}&format=OXM
- The