api

http4k / org.http4k.serverless

Package org.http4k.serverless

Common code relevant to HTTP serverless implementations.

Types

Name Summary
AlibabaCloudFunction abstract class AlibabaCloudFunction : HttpRequestHandler
ApiGatewayV1AwsHttpAdapter object ApiGatewayV1AwsHttpAdapter : AwsHttpAdapter<Map<String, Any>, Map<String, Any>>
ApiGatewayV1LambdaFunction This is the main entry point for lambda invocations using the V1 payload format. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class ApiGatewayV1LambdaFunction : AwsLambdaFunction<Map<String, Any>, Map<String, Any>>, RequestHandler<Map<String, Any>, Map<String, Any>>
ApiGatewayV2AwsHttpAdapter object ApiGatewayV2AwsHttpAdapter : AwsHttpAdapter<Map<String, Any>, Map<String, Any>>
ApiGatewayV2LambdaFunction This is the main entry point for lambda invocations using the V2 payload format. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class ApiGatewayV2LambdaFunction : AwsLambdaFunction<Map<String, Any>, Map<String, Any>>, RequestHandler<Map<String, Any>, Map<String, Any>>
ApplicationLoadBalancerAwsHttpAdapter object ApplicationLoadBalancerAwsHttpAdapter : AwsHttpAdapter<Map<String, Any>, Map<String, Any>>
ApplicationLoadBalancerLambdaFunction This is the main entry point for lambda invocations coming from an Application LoadBalancer. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class ApplicationLoadBalancerLambdaFunction : AwsLambdaFunction<Map<String, Any>, Map<String, Any>>, RequestHandler<Map<String, Any>, Map<String, Any>>
AppLoader interface AppLoader : (Map<String, String>) -> HttpHandler
AppLoaderWithContexts interface AppLoaderWithContexts : (Map<String, String>, RequestContexts) -> HttpHandler
AwsHttpAdapter interface AwsHttpAdapter<Req, Resp>
AwsLambdaFunction abstract class AwsLambdaFunction<Req : Any, Resp>
AzureFunction abstract class AzureFunction
DetectBinaryBody OpenWhisk Base64 encodes Binary requests and responses when they are sent to the deployed Function. This interface allows for custom implementations of that logic, which might be required if your function supports more than one endpoint (with mixed request/response types).interface DetectBinaryBody
GoogleCloudFunction open class GoogleCloudFunction : HttpFunction
InvocationLambdaAwsHttpAdapter object InvocationLambdaAwsHttpAdapter : AwsHttpAdapter<InputStream, InputStream>
InvocationLambdaFunction This is the main entry point for lambda invocations using the direct invocations. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class InvocationLambdaFunction : AwsLambdaFunction<InputStream, InputStream>, RequestStreamHandler
OpenWhiskFunction class OpenWhiskFunction : (JsonObject) -> JsonObject
RequestContent class RequestContent
TencentCloudFunction abstract class TencentCloudFunction

Extensions for External Classes

Name Summary
com.microsoft.azure.functions.HttpRequestMessage  

Properties

Name Summary
ALIBABA_CONTEXT_KEY const val ALIBABA_CONTEXT_KEY: String
ALIBABA_REQUEST_KEY const val ALIBABA_REQUEST_KEY: String
AZURE_CONTEXT_KEY const val AZURE_CONTEXT_KEY: String
AZURE_REQUEST_KEY const val AZURE_REQUEST_KEY: String
GCF_REQUEST_KEY const val GCF_REQUEST_KEY: String
LAMBDA_CONTEXT_KEY const val LAMBDA_CONTEXT_KEY: String
LAMBDA_REQUEST_KEY const val LAMBDA_REQUEST_KEY: String
OW_REQUEST_KEY const val OW_REQUEST_KEY: String
TENCENT_CONTEXT_KEY const val TENCENT_CONTEXT_KEY: String
TENCENT_REQUEST_KEY const val TENCENT_REQUEST_KEY: String

Functions

Name Summary
<no name provided> Http4k app loader - instantiate the application from the environment configfun <no name provided>(): Unit
asAzure fun Response.asAzure(request: HttpRequestMessage<Optional<String>>): HttpResponseMessage!
then fun Filter.then(appLoader: AppLoader): AppLoader
fun Filter.then(appLoader: AppLoaderWithContexts): <ERROR CLASS>