-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
location: eventBridgeEnabled not working with CfnTracker #29276
Comments
Yes it does exist in the CFN document and CFN spec 162.0.0. And it does exist in 2.130.0 api reference. I didn't see any error from my IDE
What made you believe it was missing in the data type and not mapped? |
That is strange! This is what I see.. The location was imported as...
When I tried Ctrl+Click on the CfnTracker, then CfnTrackerProps to see its code, this is what I see
There is no eventBridgeEnabled in there. Here is the record in my package.json
Am I using the wrong version? Or any error in the configuration? Can you please help me debug? |
Describe the bug
The EventBridgeEnabled property in the Location Tracker is not present in the CfnTrackerProps. Even if I add it forcefully with an @ts-ignore, it does not reflect in the generated CloudFormation stack.
After struggling hard, I had to set it manually. Can you please fix this?
Expected Behavior
CfnTrackerProps should have a property eventBridgeEnabled, and it should map to the EventBridgeEnabled in the Location Tracker resource of the CloudFormation template
Current Behavior
The field is missing in the data type, and not mapped to the CloudFormation stack
Reproduction Steps
const cfnTracker = new location.CfnTracker(this, "MyCfnTracker", { trackerName: "AssetTracker", description: "description", positionFiltering: "AccuracyBased", eventBridgeEnabled: true, });
Possible Solution
The CfnTrackerProps Type should be updated to include this field, and it should be appropriately mapped to the generated CloudFormation template
Additional Information/Context
No response
CDK CLI Version
2.130.0
Framework Version
No response
Node.js Version
18.16.0
OS
Windows
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: