Integrations Discussion: MVC for Integrations as data

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

This issue is for discussion toward an end for producing a MVC that treats integrations as data. For more context, we can refer to: #360742 (closed)

My proposal for the format of this discussion is to

High level Planning

1. Identify the high level needs of each integration
2. Think of how the high level needs could be represented by a manifest or metadata
3. Consider how to sometimes extend these behaviors with code for deep integrations
4. Consider the workflow in GitLab UI, and any changes that we'd need to accommodate it

Implementation Planning

5. Break needs for MVC into atomic tasks (considering any limitations for implementing into the rails application)
6. Create test plans for tasks and the anticipated E2E behavior
7. Create an Epic with issues that represents the work.

I feel this format will help us to incrementally plan toward an implementation without being coupled to a timeline. If it sounds good, I will create comments to represent each planning point, and update the table of contents accordingly.

Please let me know if another format would work better.