Skip to content

Triggers: Error case returns bytes #27113

@mrgrain

Description

@mrgrain

In the integ test triggers/test/integ.triggers.ts
Go and find the test handler in the lib directory and break it.
Run the test case and see it fail with an error similar to the one below.

This is bad for users of Triggers, since they won't be able to debug their Triggers anymore.

The stack named MyStack failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Received response status [FAILED] from custom resource. Message returned: Error: 123,34,101,114,114,111,114,84,121,112,101,34,58,34,82,117,110,116,105,109,101,46,73,109,112,111,114,116,77,111,100,117,108,101,69,114,114,111,114,34,44,34,101,114,114,111,114,77,101,115,115,97,103,101,34,58,34,69,114,114,111,114,58,32,67,97,110,110,111,116,32,102,105,110,100,32,109,111,100,117,108,101,32,39,97,119,115,45,115,100,107,39,92,110,82,101,113,117,105,114,101,32,115,116,97,99,107,58,92,110,45,32,47,118,97,114,47,116,97,115,107,47,105,110,100,101,120,46,106,115,92,110,45,32,47,118,97,114,47,114,117,110,116,105,109,101,47,105,110,100,101,120,46,109,106,115,34,44,34,116,114,97,99,101,34,58,91,34,82,117,110,116,105,109,101,46,73,109,112,111,114,116,77,111,100,117,108,101,69,114,114,111,114,58,32,69,114,114,111,114,58,32,67,97,110,110,111,116,32,102,105,110,100,32,109,111,100,117,108,101,32,39,97,119,115,45,115,100,107,39,34,44,34,82,101,113,117,105,114,101,32,115,116,97,99,107,58,34,44,34,45,32,47,118,97,114,47,116,97,115,107,47,105,110,100,101,120,46,106,115,34,44,34,45,32,47,118,97,114,47,114,117,110,116,105,109,101,47,105,110,100,101,120,46,109,106,115,34,44,34,32,32,32,32,97,116,32,95,108,111,97,100,85,115,101,114,65,112,112,32,40,102,105,108,101,58,47,47,47,118,97,114,47,114,117,110,116,105,109,101,47,105,110,100,101,120,46,109,106,115,58,49,48,54,49,58,49,55,41,34,44,34,32,32,32,32,97,116,32,97,115,121,110,99,32,85,115,101,114,70,117,110,99,116,105,111,110,46,106,115,46,109,111,100,117,108,101,46,101,120,112,111,114,116,115,46,108,111,97,100,32,40,102,105,108,101,58,47,47,47,118,97,114,47,114,117,110,116,105,109,101,47,105,110,100,101,120,46,109,106,115,58,49,48,57,51,58,50,49,41,34,44,34,32,32,32,32,97,116,32,97,115,121,110,99,32,115,116,97,114,116,32,40,102,105,108,101,58,47,47,47,118,97,114,47,114,117,110,116,105,109,101,47,105,110,100,101,120,46,109,106,115,58,49,50,53,54,58,50,51,41,34,44,34,32,32,32,32,97,116,32,97,115,121,110,99,32,102,105,108,101,58,47,47,47,118,97,114,47,114,117,110,116,105,109,101,47,105,110,100,101,120,46,109,106,115,58,49,50,54,50,58,49,34,93,125

Metadata

Metadata

Assignees

Labels

@aws-cdk/triggersRelated to the triggers packagebugThis issue is a bug.node18-upgradeAny work (bug, feature) related to Node 18 upgradesdk-v3-upgradeTag issues that are associated to SDK V3 upgrade. Not limited to CR usage of SDK only.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions