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
integTest.assertions.awsApiCall will call the specified API Call twice: once on stack creation, and another time on stack deletion.
This can be a problem for API Calls with write actions.
Expected Behavior
The specified API is only called once on stack creation.
Current Behavior
The specified API is called twice, on stack deletion as well.
Reproduction Steps
Simply specify any API and monitor CloudWatch Logs of the integ-test provider function.
Possible Solution
Only call the API in cloudformation stack creation event.
Additional Information/Context
No response
CDK CLI Version
2.41.0
Framework Version
2.41.0
Node.js Version
16.15.1
OS
MacOS
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
integTest.assertions.awsApiCall will call the specified API Call twice: once on stack creation, and another time on stack deletion.
This can be a problem for API Calls with write actions.
Expected Behavior
The specified API is only called once on stack creation.
Current Behavior
The specified API is called twice, on stack deletion as well.
Reproduction Steps
Simply specify any API and monitor CloudWatch Logs of the integ-test provider function.
Possible Solution
Only call the API in cloudformation stack creation event.
Additional Information/Context
No response
CDK CLI Version
2.41.0
Framework Version
2.41.0
Node.js Version
16.15.1
OS
MacOS
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: