> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-release-bundle/get-artifactory-parameters-for-release-bundle.md).

# Get Artifactory Parameters for Release Bundle

Get configuration parameters that you need to configure a release bundle step type in a JFrog Connect workflow.

This page describes how you get some of the configuration parameters when you use the Download Release Bundle step type in a JFrog Connect workflow. 

The procedure describes how you get the following parameters from Artifactory:

* Name 
* Version 

The procedures are different for Release Bundles v1 and v2. Both procedures are detailed below.

To get to Artifactory from Connect:

* Go to the left navigation pane and choose **JFrog Platform**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/W8Oe8h6gbmV5f7jT7rzM/get-artifactory-path-01.png" alt="" width="215"><figcaption></figcaption></figure></div>

### Release Bundle v1

To get the configuration parameters for a release bundle v1:

1. In the left navigation pane of JFrog Platform, choose **Distribution**, and then choose **Release Bundles**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/8s56OzrsgQhHrxxTsXOW/get-release-bundle-parameters-02.png" alt="" width="216"><figcaption></figcaption></figure></div>

2. In the Release Bundles table, take the name of your release bundle from the **Name** column and take its version from the **Latest Version** column. Enter these as the **Name** and **Version** in the Download Release Bundle step in Connect.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/IMrmcbCSVwfQIKNXdQOk/get-release-bundle-parameters-03.png" alt=""><figcaption></figcaption></figure></div>

Now you can complete the rest of your Download Release Bundle step configuration in Connect and save it.

### Release Bundle v2

To get the configuration parameters for a release bundle v2:

1. In the left navigation pane of JFrog Platform, choose **Artifactory** and **Release Lifecycle**.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/BoatCAA3w4NkWdQKsvFP/get-release-bundle-parameters-04.png" alt="" width="219"><figcaption></figcaption></figure></div>

2. In the Release Bundles table, take the name of your release bundle from the **Name** column and take its version from the **Latest Version** column. Enter these as the **Name** and **Version** in the Download Release Bundle step in Connect.

<figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/1NAsRJm51hJsI8IGviIT/get-release-bundle-parameters-05.png" alt=""><figcaption></figcaption></figure>

Now you can complete the rest of your Download Release Bundle step configuration in Connect and save it.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-release-bundle/get-artifactory-parameters-for-release-bundle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.