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.

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

CID-2065: Update documentation on Limitations on Running Multiple Instances #79

Merged
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/github-enterprise-connector.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,10 @@ docker run --pull=always --restart=always \
5. Deploy the docker container in your preferred deployment mode (e.g. via K8s, via virtual machine ...)
6. Shortly after initialization the agent will connect with VSM and you should see logs appearing in the log section of the integration panel in VSM.

#### Limitations on Running Multiple Instances of GitHub Broker

For a given configuration name, we only support a single broker instance to be run at any given time. Any additional instance trying to communicate with VSM will be rejected to prevent race conditions. Please ensure a single instance is running at any time for optimal performance.
mohamedlajmileanix marked this conversation as resolved.
Show resolved Hide resolved

#### Multi-org support

VSM allows you to scan multiple GitHub organizations with the VSM GitHub broker. There are two scenarios:
Expand Down
Loading