Commit a144234c authored by Sarah Walker's avatar Sarah Walker
Browse files

Add deployment flow diagram to PREP docs

parent c9d3ba1e
Loading
Loading
Loading
Loading
+32 −0
Original line number Diff line number Diff line
@@ -48,6 +48,38 @@ A completed and approved PREP is **strongly recommended** as the fastest
and simplest way for any new feature or changeset to reach GA status across all deployment platforms.
{{% /alert %}}

### GitLab Deployments

The following diagram illustrates how GitLab features flow through different deployment targets. PREP facilitates this process at each step.

```mermaid
flowchart TD
    A[Architecture Design Document] --> B(Dev)
    B --> E
    B --> L
    subgraph GitLab.com
      E(staging.gitlab.com) --> G[gitlab.com]
      L(cellsdev) --> M[cellsprod]
    end
    G -->|Gather & Tag| K(Publish)
    K --> H2
    subgraph Self-Managed-Deploy
      N(Deploy)
    end
    subgraph Self-Managed-Ops
      O(Ops)
    end
    subgraph Self-Managed-Dev
      P(Dev)
    end
    K --> N
    K --> O
    K --> P
    subgraph Self-Managed
      H2(Dedicated sandbox) --> I2(UAT) --> J2[Dedicated preprod / Dedicated production]
    end
```

## When is the best time to engage with PREP?

We strongly recommend engaging with PREP as early as possible for any feature that introduces or makes significant changes to _infrastructure or core components_. Here are a