Commit 772b1d1
authored
feat(stepfunctions-tasks): add guardrailConfiguration and trace property to the BedrockInvokeModel (#30426)
### Issue # (if applicable)
Closes #30425
### Reason for this change
In the current [BedrockInvokeModel](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_stepfunctions_tasks.BedrockInvokeModel.html), guardrail configuration and trace for the invocation are not supported.
### Description of changes
Add `gurdrailConfiguration` and `trace` property to the `BedrockInvokeModel`
### Description of how you validated changes
Add unit tests and integ tests.
### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*1 parent 76c140d commit 772b1d1
15 files changed
Lines changed: 34237 additions & 6 deletions
File tree
- packages
- @aws-cdk-testing/framework-integ/test/aws-stepfunctions-tasks/test/bedrock
- integ.invoke-model-guardrail-trace.js.snapshot
- asset.3cef2cdbb46b3821e641ffb8b9af9731af5f7e4a9e857ab633dbcd9023de724d.bundle
- aws-cdk-lib/aws-stepfunctions-tasks
- lib
- bedrock
- test/bedrock
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments