[Sub Component] Intake Microservice

[TanmoySG]

The first part of the service onboarding flow is the service onboarding - intake microservice.

• It allows a service owner to register a request with the service for onboarding.
• Also, the contract and other requirements are also handled by this microservice.
• It also does the schema validation
• Once Validated it puts the contract in the intake topic.

[Parent Component]

• 1

• 2

[Checkpoints]

• [x] Service Intake Request handler
  • Should Handle New Onboarding Request
  • Should Return/Assign an UUID for request to owner email
  • Should Store UUID in a DS (Data Store)
  • Should Return the Schema and Contract Template
• [x] Service Contract Intake
  • Should be able to match/verify the email (service owner), UUID
  • Should be able to Validate Schema
  • Should Be able to handle Template Validation
• [x] Service Onboarding Queue (SOQ) Interaction
  • Once Validated, should be able to populate any extra fields required
  • Should be able to put the contract (populated) to the SOQ in intake Topic

[Additional Details]

Add Additional details and Sections

[TanmoySG]

https://stackoverflow.com/questions/34653612/what-does-return-keyword-mean-inside-foreach-function

For each Behaviour. While running the forEach here, the loop didn't stop on return. And came out of the loop once completed and returned true, thus failing the purpose of the validate method.

The above link - from stackoverflow , should be a good explanation for the behaviour and solution for same

[TanmoySG]

https://stackoverflow.com/questions/52122272/err-http-headers-sent-cannot-set-headers-after-they-are-sent-to-the-client

ERR_HTTP_HEADERS_SENT: Cannot set headers after they are sent to the client

[TanmoySG]

wDB Particular Data View Route

https://github.com/TanmoySG/wunderDB/blob/master/documentation/documentation.md

Can be used to get particular data and make changes or verify emails.