Delete a configuration bundle
Delete a configuration bundle and all of its versions. Deletion is asynchronous — the API returns immediately with a DELETING status, and the service removes the bundle and its version history in the background.
You cannot delete a bundle that is referenced by an active A/B test. Stop the A/B test first.
Code samples
Example
Request parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
|
|
String |
Yes |
The ID of the configuration bundle to delete. Passed as a path parameter. |
Response
The API returns HTTP 202 (Accepted), indicating the deletion has been queued.
| Field | Type | Description |
|---|---|---|
|
|
String |
ID of the bundle being deleted. |
|
|
String |
Status of the bundle. Returns |
Deletion behavior
-
The operation is idempotent — calling delete on an already-deleting bundle returns the same response without error.
-
All versions across all branches are deleted along with the bundle.
-
Once deletion completes, the bundle ID and name become available for reuse.
-
If the bundle is referenced by an active A/B test, the delete fails with a
ConflictException. Stop the A/B test first.
Errors
| Error | HTTP status | Description |
|---|---|---|
|
|
400 |
Invalid request parameters. |
|
|
404 |
The specified |
|
|
409 |
The bundle is in use by another resource (for example, an active A/B test) and cannot be deleted. |
|
|
403 |
Insufficient permissions. Verify IAM policies include |
|
|
429 |
Request rate exceeded. Retry with exponential backoff. |
|
|
500 |
Service-side error. Retry the request. |