Skip to content

refactor(e2e): support fail fast in get_lambda_response #2912

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

Conversation

heitorlessa
Copy link
Contributor

@heitorlessa heitorlessa commented Aug 2, 2023

Issue number: #2911

Summary

This PR enables a fail fast mode in get_lambda_response data fetcher when invoking functions to shorten the feedback
loop in diagnosing E2E errors.

It also refactored execute_lambdas_in_parallel to make it more maintainable. It's now called get_lambda_response_in_parallel, it's documented, typed, and allows additional arguments to without refactoring.

Changes

Please provide a summary of what's being changed

Unrelated issues also fixed:

  • Idempotency DynamoDB payload wasn't sorted so assertion failed randomly
  • Narrowed X-Ray Trace search to Lambda Function FQDN node

User experience

Please share what the user experience looks like before and after this change

Before

image

After

image

Checklist

If your change doesn't seem to apply, please leave them unchecked.

Is this a breaking change?

RFC issue number:

Checklist:

  • Migration process documented
  • Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

* develop:
  chore: cleanup, add test for single and nested
  fix(parameters): make cache aware of single vs multiple calls
  fix(metrics): proxy service and namespace attrs to provider (aws-powertools#2910)
  chore(deps-dev): bump ruff from 0.0.281 to 0.0.282 (aws-powertools#2905)
@heitorlessa heitorlessa requested a review from a team August 2, 2023 11:57
@boring-cyborg boring-cyborg bot added the tests label Aug 2, 2023
@pull-request-size pull-request-size bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 2, 2023
@heitorlessa heitorlessa requested review from leandrodamascena and removed request for a team August 2, 2023 11:57
@github-actions github-actions bot added the bug Something isn't working label Aug 2, 2023
@sonarqubecloud
Copy link

sonarqubecloud bot commented Aug 2, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
25.2% 25.2% Duplication

@heitorlessa heitorlessa linked an issue Aug 2, 2023 that may be closed by this pull request
2 tasks
@heitorlessa heitorlessa changed the title fix(parameters): make cache aware of single vs multiple calls refactor(e2e): support fail fast in get_lambda_response Aug 2, 2023
@heitorlessa heitorlessa merged commit 6df9b1d into aws-powertools:develop Aug 2, 2023
@heitorlessa heitorlessa deleted the refactor/e2e-get-lambda-response branch August 2, 2023 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement size/L Denotes a PR that changes 100-499 lines, ignoring generated files. tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maintenance: Shorten feedback loop in E2E tests upon function invocation errors
2 participants