-
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
(integ-tests): awsApiCall()
cannot be used with same service and action
#23049
Comments
Thank you @yamatatsu !! It seems to make sense if we are allowed to pass an |
|
Related to #22043 |
This PR resolves errors in the integration test library when users run identical assertions multiple times. This change ensures that each use of `awsApiCall`, `httpApiCall`, and `invokeFunction` has a unique identifier, even when multiple identical assertions are used in the same context. We introduced a `uniqueAssertionId` function in the `DeployAssert` construct that maintains backward compatibility with the old id rendering scheme, but prevents the use of conflicting construct ids by tracking the usage of ids and differentiating them where there's a conflict. Closes #22043, #23049 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@yamatatsu a change referencing this issue was merged and released. Is your issue resolved? |
Closed by #27380 |
|
Describe the bug
Now,
awsApiCall()
cannot be used twice with same service and action.Because
AwsApiCall
's id is made by string literal as following:`AwsApiCall${service}${api}`
at here.
Expected Behavior
To be able to use with same service and action greater than twice.
Current Behavior
An error is occured.
Error message:
Reproduction Steps
See https://github.com/yamatatsu/represent-aws-cdk-integ-tests-bug .
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
v2.51.1
Framework Version
No response
Node.js Version
v18.12.1
OS
mac (apple silicon)
Language
Typescript
Language Version
3.9.10
Other information
No response
The text was updated successfully, but these errors were encountered: