Request handlers expect a synchronous ProgressEvent response instead of async

Open
#402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, java
Domain
cloud, tooling

Research direction

Start by reading invokeHandler() in AbstractWrapper.java and handleRequest() in LambdaWrapper.java, then trace how the Java plugin represents ProgressEvent responses. Check the AWS Lambda and CloudFormation request lifecycle to determine whether asynchronous responses are supported. Done requires a clear decision on the response contract and an agreed implementation scope.

Written by the indexing model from the issue text.

Description

The invokeHandler() method in AbstractWrapper.java and handleRequest() method in LambdaWrapper.java seems to always return a synchronous response in form of ProgressEvent. With server side programming semantics, I would expect them to return an async response (like a JAVA future).

Is this a limitation of aws lambda or the cloudformation infra should use the async library for aws lambda?

Dominant language
Java
Stars
30
Forks
48
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-cloudformation/cloudformation-cli-java-plugin

All issues in aws-cloudformation/cloudformation-cli-java-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.