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
Currently, the end-to-end tests do not work. It seems that the infrastructure cannot be created in the AWS account due to some issues with bootstrapping the account/CDK stack. Since we don't deploy using CDK but only synthesize CloudFormation using CDK, maybe there is some incompatibility.
Current error:
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 14.41 s <<< FAILURE! -- in software.amazon.lambda.powertools.MetricsE2ET
[ERROR] software.amazon.lambda.powertools.MetricsE2ET -- Time elapsed: 14.41 s <<< ERROR!
software.amazon.awssdk.services.cloudformation.model.CloudFormationException: Unable to fetch parameters [/cdk-bootstrap/hnb659fds/version] from parameter store for this account. (Service: CloudFormation, Status Code: 400, Request ID: 2bcf84dd-75e3-4f7b-83fc-4f93f6f0e0c0)
Summary
Currently, the end-to-end tests do not work. It seems that the infrastructure cannot be created in the AWS account due to some issues with bootstrapping the account/CDK stack. Since we don't deploy using CDK but only synthesize CloudFormation using CDK, maybe there is some incompatibility.
Current error:
It also seems that some of the test assertions were not updated with features added to the library or AWS services at a later point after initial implementation. For example, AWS X-RAY creates a default "Init" trace for Lambda functions now which is ignored in this assertion: https://github.com/aws-powertools/powertools-lambda-java/blob/v2/powertools-e2e-tests/src/test/java/software/amazon/lambda/powertools/TracingE2ET.java#L79.
The goal of this issue is to:
Why is this needed?
Restoring the functionality of end-to-end tests is crucial to assure the functionality of the library at runtime and achieve a safe release process.
Which area does this relate to?
No response
Solution
No response
Acknowledgment
The text was updated successfully, but these errors were encountered: