Assign Tag to Release Bundle v2 Version

JFrog REST APIs

Content Type
REST API
ft:sourceType
Paligo

Description: Assigns a descriptive tag to a Release Bundle v2 version. The tag will appear on the card for the Release Bundle version on the Release Lifecycle kanban board.Use the Release Bundle v2 Promotions Kanban Board

Since: 7.110.1

Security: requires Annotate permissions

Usage: PUT /lifecycle/api/v2/release_bundle/records/{name}/{version}/tag

Consumes: application/json

Sample Request:

curl --location --request PUT '{artifactory_host}/lifecycle/api/v2/release_bundle/records/rb1/1.0.0/tag?project=default' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=' \
--data '{
    "tag": "mytag2"
}'

The body of the request must include the following information:

Field

Type

Description

tag

string

The text of the tag to apply to the Release Bundle version.

The tag may contain alphanumeric characters, dashes (-), underscores (_), and periods (.). It should not contain spaces or special characters (@, #, etc.).

The maximum length is 128 characters.

Sample Response:

{
  "repository_key" : "release-bundles-v2",
  "release_bundle_name" : "rb1",
  "release_bundle_version" : "1.0.0",
  "release_bundle_tag" : "mytag2"
}

The response contains the following information:

Field

Type

Description

repository_key

string

The repository key related to the Release Bundle. By default, this is release-bundles-v2.

release_bundle_name

string

The name of the Release Bundle.

release_bundle_version

string

The Release Bundle version.

release_bundle_tag

string

The text of the tag applied to the Release Bundle version.

Status Codes:

Code

Description

200

OK

403

Permission Denied

404

Not Found

Remove a Tag from the Release Bundle Version

To remove a tag from a Release Bundle v2 version, execute the Assign Tag API described above with the tag empty or set to null in the body:

{
    "tag":null
}

Alternatively:

{
   "tag":""
}