spring-cloud-function | //// DO NOT EDIT THIS FILE | Serverless library

I've created an AWS Lambda based Spring Cloud Function with multiple functions and it works fine when I define exactly one "spring_cloud_function_definition" environment variable in the AWS Lambda Configuration panel. These functions' input and output is a Message, so the payload and http headers can be accessed runtime as well.

I'd like to use this AWS Lambda function in different API Gateway methods, so for example:

• /item [POST] -> saveItem should be called
• /item [DELETE] -> deleteItem should be called
• ... and so on...

https://cloud.spring.io/spring-cloud-static/spring-cloud-function/3.0.0.RC1/reference/html/spring-cloud-function.html#_function_catalog_and_flexible_function_signatures

I found this documentation on Spring.io which says it's feasible:

If the input argument is of type Message, you can communicate routing instruction by setting one of spring.cloud.function.definition or spring.cloud.function.routing-expression Message headers. For more static cases you can use spring.cloud.function.definition header which allows you to provide the name of a single function (e.g., …​definition=foo) or a composition instruction (e.g., …​definition=foo|bar|baz)

So the following test event should run in AWS Lambda without any failure:

{ "method": "POST", "body": "{ "key" : "value" }", "headers": { "spring.cloud.function.definition": "saveItem" } }

but of course it throws an exception:

I have a problem with routing using API Gateway headers. I am using org.springframework.cloud.function.adapter.aws.FunctionInvoker::handleRequest as a handler request. I have two functions, they work locally. They work if I set environment variable.

If I use API Gateway headers (spring.cloud.function.definition:lowercase), I get:

I am using Gradle 7.3.3 to build a Spring Boot Application that uses jooq to generate Table, POJO, and Record Classes from a pre-existing database schema. When attempting to upgrade jooqVersion from 3.15.5 to 3.16.0, :generateJooq returns the following error:

I am trying to create a Spring Cloud Function application which will have multiple functions defined in it. I need to use the Functional Bean definition approach for reduced cold start time. The jar will be deployed in AWS Lambda.

The code works in local environment and I am able to curl for all the functions defined. However when deployed in Lambda , the function is not getting located by AWS.

The code runs and is working as expected on Lambda ,if there is only 1 function defined.

I will mention below the things that I have tried.

1. Followed the Spring Doc to create the project
2. This works fine in local and also runs in Lambda with Handler org.springframework.cloud.function.adapter.aws.SpringBootStreamHandler::handleRequest as per the comment by Thannasi on mydeveloperplanet blog post
3. Next I added few more functions and registered them with the Generic ApplicationContext

getting below error while using tuple based input output arguments on azure spring boot function..

Trying to configure Spring to send bad messages to dead letter queue while using batch mode. But as a result in dlq topic there is nothing.

I use Spring Boot 2.5.3 and Spring Cloud 2020.0.3. This automatically resolves version of spring-cloud-stream-binder-kafka-parent as 3.1.3.

Here is application.properties:

I was trying to run this example. I made some changes in the function handlers, pom.xml and project structure but I don't think they would change the way the app runs.

Anyway, my problem occurs when I run ./mvnw azure-functions:run, for some reason it's not finding my handler.

I have created a simple Google Cloud Function with Spring Cloud Function library to get triggered on the arrival of the Pub/Sub message. I followed the sample function-sample-gcp-background. Whenever a message is triggered to the Pub/Sub, it gets printed from the Cloud Function as expected.

But I wonder how can I get the metadata of the Pub/Sub message in the Cloud Functon. The Google Cloud Function documentation says that

This metadata is accessible via the context object that is passed to your function when it is invoked.

How can I access this metadata (or the context object) in a Spring Cloud Function application?

UPDATE :- Version spring-cloud-function-adapter-gcp:3.1.2

UPDATE 2:- I raised an issue in github and got the issue resolved. Thanks to Spring Cloud Function team.

I'm using the last version of Spring Cloud Function as below