Open TanmoySG opened 2 years ago
Service Onboarding/Initiation should stay as a separate micro-service/app , outside the scope or repo of wIP, as a service is only dependant on wIP when the service is already onboarded and exists in the "wunder service directory"(?).
Initiation/Onboarding a service, to use wIP is a step that comes before wIP Connection and uses no resources until the services are validated and onboarded
The only part of wIP and Service Manager that overlap, or are dependant is the "Service Connector" part.
Initiation is out of scope for this app and this repo.
Maybe Create a separate service manager repo to track and create the service manager framework and once done The integration with wIP and Connectors can be worked upon - here.
[x] Add a detailed diagram of how the framework should work and how wIP and Service Manager should work in the comments.
The Following diagram will act as a high level system flow for existing services data-access flow (eg. login)
Define Service Connector and Initialisation Architecture for wIP. Set Base rules/policies, how service verifies its identity and how to on-board apps/services securely and only verifies services get to access data.
[Checkpoints]
[Additional Information] Add additional information as per need. Snippets, References, etc.