Closed darksinge closed 7 months ago
Thanks for opening this issue! Please make sure to provide the following information to help us reproduce the issue:
Thanks for opening this issue. The ticket CLOUDP-231117 was created for internal tracking.
thanks @darksinge for opening this issue.
there is a mistake in the associated CloudFormation resource where Name is not specified as required. The required fields should be projectId, appId, name and type.
sorry for the inconvenience, we're working on it and it will be fixed in the next CDK release.
Is there an existing issue for this?
CDK package version
3.1.0
CFN Resource version
trigger: v1.4.0
CFN Resource Region
us-east-1
Current Behavior
I had a big ole description written up for another issue related to creating triggers, then figured out the problem. But, while I'm here I figured I'd complain about something else 🤓.
I copy/pasted this example, (modifying the event processor section to use EventBridge in AWS), and got the following error after deploying with
cdk deploy
:Indeed, after specifying a name for the trigger, the deployment succeeded.
Reviewing the type definition for
CfnTriggerProps
, I see:Maybe it's required if using event bridge as the "event processor"? At any rate, the CDK docs and admin API docs do not seem to be in agreement.
Deployments take a long time, especially when dealing with rollbacks and addressing one hiccup at a time. Ensuring required fields are marked as such makes a difference. Thanks for your attention on this matter!
AWS CDK code to reproduce the issue
Steps To Reproduce
npx cdk init app --language=typescript
lib/CdkTestingStack.ts
andbin/app.ts
, respectively.appId
,profile
,dbName
, etc.) and run the following command:cdk synth
Code of Conduct