- Add SCF/Azure Gradle sample and docs.
- Move the function-azure-di-samples into standalone projects.
- Apply the name convetion and project structure for the SCF adaptes.
E.g. function-sample-azure-XXX projects under the spring-cloud-function-samples root.
- Remove the redudant samples.
- Improve the samples docs and the Adapter generic docs.
- Streamline docs.
- Add azure web adapter sample and README.
- Add Spring Azure Functions banner for azure and azure web adapters.
- azure-web adapter fixes:
- Fix issues in serverles-web ProxyHttpServletResponse implementation.
- Remove the custom FunctionClassUtils utils in favor of scf-context/util/FunctionClassUtils.
- Remove redundant files.
- Add FunctionInvoker deprecation annotations.
- Extend the time trigger sample with Retry policies example.
This approach simplifies the existing request handlers while also fixing the invocation model to ensure AC is not created multiple times and ExecutionContext is properly propagated via Message headers
The old request handlers are deprecated
Documentation updates as well as tests
Resolves#437
* Handler extends AzureSpringBootRequestHandler with types
HttpRequestMessage and HttpResponseMessage (which are required by
Azure Functions for HTTP-triggered functions)
* Handler extracts request path, query string parameters as well as the
HTTP method from the HttpRequestMessage object and forwards them to
the function as message headers
* Handler creates an HttpResponseMessage with the response coming from
the called function
* Created unit tests accordingly
GH-317, Implement HTTP request-specific handler for Azure adapter
* Handler extends AzureSpringBootRequestHandler with types
HttpRequestMessage and HttpResponseMessage (which are required by
Azure Functions for HTTP-triggered functions)
* Handler extracts request path, query string parameters as well as the
HTTP method from the HttpRequestMessage object and forwards them to
the function as message headers
* Handler creates an HttpResponseMessage with the response coming from
the called function
* Created unit tests accordingly
GH-317, Implement HTTP request-specific handler for Azure adapter
* Handler extends AzureSpringBootRequestHandler with types
HttpRequestMessage and HttpResponseMessage (which are required by
Azure Functions for HTTP-triggered functions)
* Handler extracts request path, query string parameters as well as the
HTTP method from the HttpRequestMessage object and forwards them to
the function as message headers
* Handler creates an HttpResponseMessage with the response coming from
the called function
* Created unit tests accordingly
- Added support for injecting target execution context into the ApplicationContext in AbstractSpringFunctionAdapterInitializer, effectively making it available to all adapters (if one is provided)
- Added test, docs
Resolves#265
- Added ability to retrieve input type from FunctionRegistration (if available) in AbstractSpringFunctionAdapterInitializer
- Removed azure/AzureSpringFunctionInitializer and aws/SpringFunctionInitializer
- Added additional tests in AWS and Azure modules
- See 0189c578ef for additional info
