Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decouple the Control Plane Services and Operational Workflow #17

Closed
karthikksf opened this issue Jun 3, 2024 · 0 comments · Fixed by #33
Closed

Decouple the Control Plane Services and Operational Workflow #17

karthikksf opened this issue Jun 3, 2024 · 0 comments · Fixed by #33
Assignees
@shubhamp-sf
Labels
saas saas-phase2

Comments

@karthikksf
Copy link

karthikksf commented Jun 3, 2024 •
edited by shubhamp-sf
Loading

Current flow in a nutshell:

  • SaaS Admin calls the provisioning API of Tenant Management Service.
  • The service then starts the codebuild process using AWS SDK and requires the information such as the build process’s name etc.

Which is supposed to be decoupled in a manner that removes the responsibility of tenant service to trigger the build.

Following is the proposed architecture:

image

The invocation flow in the orchestrator service is the following:
image
@karthikksf karthikksf added the saas label Jun 3, 2024
@shubhamp-sf shubhamp-sf changed the title Add capability to use a different Build provider other than Code Build Decouple the Control Plane Services and Operational Workflow Jul 16, 2024
shubhamp-sf added a commit that referenced this issue Jul 16, 2024
@shubhamp-sf
feat(tenant-management): add event connector to avoid coupling with c…
e27f77d 
…odebuild

in the tenant provisioning flow

GH-17
@shubhamp-sf shubhamp-sf mentioned this issue Jul 16, 2024
Merged
8 tasks
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
3157b38 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
15bc04c 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
e8dba85 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
248e839 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
bc9340a 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
234c788 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
3172b49 
to be served as a common event target for control plane workflows

GH-17
shubhamp-sf added a commit that referenced this issue Jul 17, 2024
@shubhamp-sf
feat(orchestrator-service): add event orchestrator service
03dc193 
to be served as a common event target for control plane workflows

GH-17
a-ganguly pushed a commit that referenced this issue Jul 23, 2024
@shubhamp-sf
feat(tenant-management): decouple the event processing using a connec…
29dba9d 
…tor and an orchestrator service (#33)

## Description

This PR adds an overridable event connector to avoid coupling with AWS
CodeBuild and make the provisioning and other actions event driven.

This also adds an orchestrator service intended to help consumers deploy
a supporting serverless application as a common target for the control
plane events.


The invocation flow in the orchestrator service is the following:

![image](https://github.com/user-attachments/assets/d8ea5e4e-421a-4bf5-82f9-b5feb1907a2b)


GH-17

Fixes #17 

## Type of change

- [x] New feature (non-breaking change which adds functionality)

## How Has This Been Tested?

- [x] Testing in the sandbox application

## Checklist:

- [x] Performed a self-review of my own code
- [x] npm test passes on your machine
- [x] New tests added or existing tests modified to cover all changes
- [x] Code conforms with the style guide
- [x] API Documentation in code was updated
- [ ] Any dependent changes have been merged and published in downstream
modules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shubhamp-sf shubhamp-sf

Labels
saas saas-phase2
Projects
None yet
Milestone
No milestone
2 participants
@shubhamp-sf @karthikksf