Overview

DevOps teams use Projects to gain a file-centric view of their IaC. In projects errors are sorted by directory and file structure and provide instant visibility to each resource's dependencies and history. By evaluating resources alongside additional file in a subject directory and with the related context from a resource perspective DevOps can select which fixes should be promoted and which errors should remain as known accepted risks.

Click on the 🚀 symbol to navigate to ProjectsClick on the 🚀 symbol to navigate to Projects

Click on the 🚀 symbol to navigate to Projects

Repositories (aka Repos)

Git-based code repos are at the center of Projects. You can navigate between repos or go to a known branch scan in Code Reviews. Every repo loads all directories and sub-directories that currently include errors.

Selecting an error box automatically loads the related information in a Resource Explorer. Useful information here would include full resource metadata, related resources extracted from the graph as well as full resource history.

Navigate between connected reposNavigate between connected repos

Navigate between connected repos

File Details and Options

Policy and Severity

The colored row at the bottom shows a description of the Policy and its Severity.

Further Details

Press the colored bar to see:

  • Description and Rationale

Code Details and Proposed Fix

The body of the file information shows the details of the code and the proposed fix.

Fixing Errors

An option to automatically Fix or Remediate appears for most errors.
See also Manual Fix below.

  1. Press FIX. COMPLETED will appear at the top right.
  2. Press SUBMIT . This triggers a new build.
Click FIX to select errors you would like to include in a Fix PR. When you are done - Click Submit to open the PR.Click FIX to select errors you would like to include in a Fix PR. When you are done - Click Submit to open the PR.

Click FIX to select errors you would like to include in a Fix PR. When you are done - Click Submit to open the PR.

Manual Fix

In some cases, no automated Fix is available, but you will see an option for Fix Manually.

Read Guidelines and Manual Procedure

To read the explanation and procedure for Manual Remediation of this error, press More and then Full Guidelines. A new tab opens.

Open GitHub/Bitbucket to Implement Manual Fix

To open GitHub/Bitbucket in order to implement the Manual Fix, press FIX MANUALLY.

Filters

A filter pane on the right side of the page can help further narrow the scope of work on a given repo.

Category

Enables filtering between policy categories and select a sub group of issues to solve.

Severity

Enables filtering only on high impact issues and clearing low impact issue from the error view.

Tags

Enables filtering only on tagged individual key-value pairs.

Search

Use Search to pinpoint specific code snippets, file names or directories. To use search click the magnifier icon on the top right part of your screen. Enter the text you wish to find, and hit Enter. Search results immediately appear, highlighting the searched text across mediums.

Users

Bridgecrew automatically maps code changes to their individual commits and users. On the top right corner, the list of all contributing users enables quickly zooming in on changes introduced by specific developers. You can also select to view errors by user by clicking the name of a user in an error box.

Click on the 🔎 to search for specific codeClick on the 🔎 to search for specific code

Click on the 🔎 to search for specific code


What’s Next
Did this page help you?