> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/tools-and-integrations/integrations/argo-workflows.md).

# 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 <https://bitbucket.org/debricked/debricked-scan>

### **Configure** OpenText Core SCA **token**

Start by [generating an access token](/product/administration/generate-access-token.md). 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 to analyze all dependencies in your project, their versions, and relations, files containing the resolved dependency trees should be created prior to scanning. The file creation depends on the package manager used. OpenText Core SCA tries to generate the lacking files, which can negatively affect speed and accuracy.

**Example 1:** If [**npm**](https://www.npmjs.com/) is used in your project, you will have a "package.json" file, but in order to scan all your dependencies, OpenText Core SCA requires either "package-lock.json" or "yarn.lock" as well.

**Example 2:** If [**Maven**](https://maven.apache.org/) is used in your project, you will have a "pom.xml" file, but in order to resolve all your dependencies, OpenText Core SCA requires 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](http://github.com/debricked/cli/tree/main/examples/templates/Argo) to your ".circleci/config.yml" file (if the file does not exist, create one):

{% @github-files/github-code-block url="<https://github.com/debricked/cli/blob/main/examples/templates/Argo/argo.yml>" %}

Consider [using kubernetes](https://github.com/argoproj/argo-workflows/blob/master/examples/secrets.yaml) secrets instead of parameter binding with -p.

* <pre class="language-bash"><code class="lang-bash"><strong>argo submit -n {namespace} --watch {template} \
  </strong>-p debricked-token={debricked-token} \
  -p git-url={git-url}
  </code></pre>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.debricked.com/tools-and-integrations/integrations/argo-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.