Managing group of projects with dip is hard, imagine having multiple gems with such setup
interaction:
brakeman:
description: Check brakeman sast
command: docker run ...
gitleaks:
description: Check gitleaks sast
command: docker run ...
bearer:
description: Check bearer sast
command: docker run ...
trivy:
description: Check trivy sast
command: docker run ...
Every change in sast configuration leads to change in all dip.yml among gems.
Related tickets
-
What's inside
This PR introduces new concept of modules, modules are stored in .dip folder. This folder should be synced among group for example with git submodules, so it is stored in one place and synced among group.
Each module contains dip configuration so it can be splitted logically, e.g.
# ./.dip/sasts.yml
interaction:
brakeman:
description: Check brakeman sast
command: docker run ...
gitleaks:
description: Check gitleaks sast
command: docker run ...
bearer:
description: Check bearer sast
command: docker run ...
trivy:
description: Check trivy sast
command: docker run ...
Now sasts are managed in one place and can be included via modules.
Context
Managing group of projects with
dip
is hard, imagine having multiple gems with such setupEvery change in sast configuration leads to change in all
dip.yml
among gems.Related tickets
-
What's inside
This PR introduces new concept of
modules
, modules are stored in.dip
folder. This folder should be synced among group for example with git submodules, so it is stored in one place and synced among group.Each module contains dip configuration so it can be splitted logically, e.g.
Now sasts are managed in one place and can be included via modules.
See more examples in
README
Checklist: