Skip to content

Commit ae85b14

Browse files
awileysnykgitbook-bot
authored andcommitted
GITBOOK-8878: Universal Broker, replace deployment diagram with corrected diagram
1 parent 20e45a2 commit ae85b14

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/.gitbook/assets/image 5 (3).png

572 KB
Loading

docs/enterprise-setup/snyk-broker/universal-broker/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ The following pages guide you through a Broker deployment setup using the Univer
1717

1818
The Universal Broker separates deployment and container concerns from connection concerns. It allows for a smaller or a single deployment to support numerous connections of varied types.
1919

20-
<figure><img src="../../../.gitbook/assets/image 5.png" alt="Universal Broker Model"><figcaption><p>Universal Broker Model</p></figcaption></figure>
20+
<figure><img src="../../../.gitbook/assets/image 5 (3).png" alt=""><figcaption><p>Universal Broker deployment diagram</p></figcaption></figure>
2121

2222
In contrast to the existing Broker model, where each deployment and container supports only one connection type, Snyk is providing Broker deployments configured to support many connections in a set-and-forget approach.
2323

@@ -38,7 +38,7 @@ For example, deployments run a connection (type `github`) using the environment
3838
## Steps in implementing the Universal Broker
3939

4040
{% hint style="warning" %}
41-
Prerequisite: You must be tenant admin to be able to create deployments, credentials reference(s) and connection(s).
41+
Prerequisite: You must be a tenant admin to be able to create deployments, credentials reference(s), and connection(s).
4242
{% endhint %}
4343

4444
The high-level steps in implementing the Unversal Broker follow.

0 commit comments

Comments
 (0)