Update a configuration bundle
Update a configuration bundle to create a new immutable version with changed configuration. Each update produces a new version ID; existing versions are never modified. Versions form a chain via parentVersionIds, similar to git commits.
Code samples
Example
Request parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
|
|
String |
Yes |
The ID of the configuration bundle to update. Passed as a path parameter. |
|
|
String |
No |
Updated name for the bundle. |
|
|
String |
No |
Updated description. Maximum 500 characters. |
|
|
Map |
No |
Updated component configurations. Creates a new version with these components. |
|
|
List of strings |
Yes |
Parent version IDs for lineage tracking. Regular commits have one parent, the latest version on the branch. Merge commits have two parents: the latest version on the target branch, then the latest version on the source branch. If the branch already exists, the first parent must be the latest version on that branch. |
|
|
String |
No |
Branch name for this version. If not specified, inherits the parent’s branch or defaults to |
|
|
String |
No |
Commit message describing the changes. Maximum 500 characters. |
|
|
Object |
No |
Source that created this version. Contains |
|
|
String |
No |
Idempotency token. |
Response
| Field | Type | Description |
|---|---|---|
|
|
String |
ARN of the configuration bundle. |
|
|
String |
ID of the configuration bundle. |
|
|
String |
UUID of the new version created by this update. |
|
|
Timestamp |
When the update was applied. |
Branching and merges
Configuration bundles support git-like branching:
-
Linear commits. Pass the latest version on the branch as the single parent. The new version extends the branch lineage. The AgentCore CLI looks up the latest version on the branch and passes it as the parent for you.
-
New branch. Specify a
branchNamethat does not yet exist and aparentVersionIdspointing to the version you want to branch from. -
Merge commits. Pass two
parentVersionIds: the first is the latest version on the target branch, the second is the latest on the source branch. This creates a merge commit on the target branch.
Errors
| Error | HTTP status | Description |
|---|---|---|
|
|
400 |
Invalid request parameters. Check field constraints. |
|
|
404 |
The specified |
|
|
409 |
Version conflict. The specified parent version is not the latest on the branch. Fetch the latest version and retry. |
|
|
403 |
Insufficient permissions. Verify IAM policies include |
|
|
429 |
Request rate exceeded. Retry with exponential backoff. |
|
|
500 |
Service-side error. Retry the request. |