Argo Workflows

Learn how to integrate Debricked with Argo Workflows.

Argo Workflows is supported by using our debricked/debricked-scan Docker image.

Our Argo workflows integration support the same options as our Bitbucket integration, read more about the options here

Configure Debricked token

Start by generating an access token. Copy the token so that you can use it in the next step.

Configure Argo Workflow

Depending on what package manager you are using there are different step setups.

In order for us to analyze all dependencies in your project, their versions, and relations, files containing the resolved dependency trees have to be created prior to scanning. Those depend on the package manager used. If files are lacking we try to generate them on our side, which can negatively affect speed and accuracy.

Example 1: If npm is used in your project you will have a package.json file, but in order for us to scan all your dependencies we need either package-lock.json or yarn.lock as well.

Example 2: If Maven is used in your project you will have a pom.xml file, but in order for us to resolve all your dependencies we need a second file, as Maven does not offer a lock file system. Instead, Maven dependency:tree plugin can be used to create a file called .debricked-maven-dependencies.tgf.

  1. Add the template to your .circleci/config.yml file (if the file doesn't exist, create one)

Consider using kubernetes secrets instead of parameter binding with -p

  • argo submit -n {namespace} --watch {template} \
    -p debricked-token={debricked-token} \
    -p git-url={git-url}

Last updated