You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Select this option if this issue appears to be a regression.
Last Known Working CDK Version
No response
Expected Behavior
sqlKnowledgeBaseConfiguration should not be missing in L1 construct.
Current Behavior
CDK gives the following error: Object literal may only specify known properties, and 'sqlKnowledgeBaseConfiguration' does not exist in type 'IResolvable | KnowledgeBaseConfigurationProperty'.
@nroshanr Good morning. Thanks for opening the issue. I do see that schema file aws-bedrock-knowledgebase.json was updated 14 hrs ago. It could take a while for CDK to be updated with the new schema changes. Please wait for next release for sqlKnowledgeBaseConfiguration to be included in CfnKnowledgeBaseProps.
Thanks,
Ashish
ashishdhingra
added
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
and removed
investigating
This issue is being investigated and/or work is in progress to resolve the issue.
labels
Jan 16, 2025
Describe the bug
KnowledgeBaseConfigurationProperty is missing the
sqlKnowledgeBaseConfiguration
property which is currently supported by CloudFormation AWS::Bedrock::KnowledgeBase KnowledgeBaseConfigurationRegression Issue
Last Known Working CDK Version
No response
Expected Behavior
sqlKnowledgeBaseConfiguration
should not be missing in L1 construct.Current Behavior
CDK gives the following error:
Object literal may only specify known properties, and 'sqlKnowledgeBaseConfiguration' does not exist in type 'IResolvable | KnowledgeBaseConfigurationProperty'.
Reproduction Steps
Here's a sample code to replicate the error:
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.176.0
Framework Version
No response
Node.js Version
v18.20.5
OS
Linux
Language
TypeScript
Language Version
5.3.3
Other information
No response
The text was updated successfully, but these errors were encountered: