The Git integration feature allows an operator to truly treat all policies as code and reflect them in a designated Git repository. This enables you to:
Perform a proper review and approval workflow
Comply with SDLC guidelines
To enable Git integration, see the git integration settings screen.
At any time, an operator can choose to commit the project settings and policies to a designated Git branch. build.security's control plane acts as a "Git client". When clicking the "commit" button, the following commands take place:
The operator is asked to provide the remote branch name
If the branch exists in the remote repository, build.security's git client will
pull latest and
commit the changes.
If the branch do not exist in the remote repository, build.security's git client will create a new branch with the same name under the repository's
default branch, and then will follow stop #2 above.
When pulling the remote git branch, build.server's git client looks for a
.buildsecurity yaml file, which can hold basic information on where to store the project's artifacts within the branch.
version: 0.1path: my_policies_folder
The version of the YAML file
The relative path to store the project's artifacts in
In order to enable the git integration feature, follow the instructions on the git settings screen.