Description: Deletes the selected Release Bundle v2 version with all its promotions. Both the Release Bundle attestation and all artifacts are removed.
Note
To delete a Release Bundle v1 version, see Delete Release Bundle v1 Version. For information about the difference between v1 and v2 Release Bundles, see Types of Release Bundles.
Warning
Deleted Release Bundle v2 versions are not sent to the trash can , even when the trash can is enabled. This means that once deleted, the version cannot be recovered.
Since: 7.63.2
Security: Requires Read and Delete permissions to the target Release Bundle path.
Usage:DELETE /lifecycle/api/v2/release_bundle/records/{rb-name}/{rb-version}?project=<Project-Name>
Query Parameters (optional):
Parameter | Type | Description |
|---|---|---|
| boolean | Determines whether the operation should be asynchronous ( |
| string | Defines the project associated with the Release Bundle, if any. By convention, each project may contain only one Release Bundles system repository with the name |
| string | Optional Release Bundles repository identifier that identifies where a Release Bundle version resides. If this parameter and the |
Sample Request:
DELETE /lifecycle/api/v2/release_bundle/records/changedbundle/1.0.0?project=test
Response body: {empty}
Status Codes:
Code | Description |
|---|---|
200 | Submitted (Async) |
204 | Deleted (Sync) |
401 | Bad Credentials |
403 | Permission Denied |
404 | Not Found |
Tip
In addition to deleting Release Bundle v2 versions manually as described above, administrators can define a Cleanup policy that removes Release Bundle versions automatically according to defined criteria. For more information, see CLEANUP POLICIES - RELEASE BUNDLES V2 APIs.