feat(bedrock): replace PrepareAgent with shouldPrepareAgent prop #250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per discussions with @massi-ang and the CloudFormation team, there shouldn't be a resource to call PrepareAgent as it doesn't create anything. This change replaces the custom resource with an optional property called
shouldPrepareAgent
that calls and waits for the agent to be prepared after creating or updating the agent, action group, or knowledge base association custom resources.Alias creation and updates still prepare the agent first. Developers can choose whether to use
shouldPrepareAgent
or create an alias that tracks the latest changes to ensure that their agent is prepared. This change makes the alias custom resource use the same function to prepare the agent and wait as the others.This change replaces the complicated
changeId
hashes with theupdatedAt
timestamps returned by the SDK in order to determine when to update the alias.Custom Resource exceptions are reraised by the retry mechanism.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.