Integrating Bridgecrew with GitLab Self-Managed makes it possible for Bridgecrew to scan your Infrastructure-as-code files (Terraform and CloudFormation) and monitor configuration issues in development.
For details on integrating Bridgecrew with GitLab.com, see Integrate with GitLab.
IP-based Network Access
If your organization requires IP-based access to its network, add all three IP addresses below to your ingress access configuration.
For Prisma cloud console integration - discover relevant IP addresses here
For Bridgecrew platform - Bridgecrew performs load balancing across these addresses.
- From Integrations Catalogue, under Code Integrations, select GitLab Self-Managed .
- Enter your GitLab Self-Managed domain, for example, gitlab.my_company.com, then select Register. A new tab opens for registering a new OAUTH app in GitLab Self-Managed.
- Copy Application Name and Redirect URI from the Register OAUTH app step.
- Paste the copied values for Name and Redirect URI from the previous step in Bridgecrew.
- Check API.
- Select Save Application. An Application Summary page opens in GitLab Self-Managed.
The Confidential setting shown in the image above, is checked by default in GitLab Self-Managed, however, it is not required for Bridgecrew Cloud.
- Copy the Application ID and Secret values.
- Paste the copied values in the Application ID and Secret fields, then select Authorize.
You are then redirected back to Bridgecrew on the same tab.
- Select one of the following options then select Next:
- Permit all existing repositories
- Permit all existing and future repositories
- Choose from the repository list.
If choosing from the repository list, select the relevant repositories.
- When the message "New account successfully configured" appears, select Done.
Note: after the next GitLab Self-Managed scan, the scanned repository will appear in the Integrations grid; for further details, see here.
The image below shows an example of a Bridgecrew comment on a license compliance error.
Updated 8 months ago