SpringCloud/spring-cloud-function
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix antor warnings

Browse Source
This commit is contained in:
Oleg Zhurakousky
2023-09-12 16:35:46 +02:00
parent 8b1b83be03
commit e327d6ef2a
9 changed files with 331 additions and 222 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/modules/ROOT/pages/spring-cloud-function/apendix.adoc → docs/modules/ROOT/pages/spring-cloud-function/appendix.adoc
View File

@@ -1,5 +1,5 @@
[[apendix]]
= Apendix
[[appendix]]
= Appendix
:page-section-summary-toc: 1
Relevant Links:

4
docs/modules/ROOT/pages/spring-cloud-function/serverless-platform-adapters.adoc
View File

@@ -5,5 +5,5 @@
As well as being able to run as standalone process, Spring Cloud
Function application can be adapted to run one of the existing
serverless platforms. In the project there are adapters for
https://github.com/spring-cloud/spring-cloud-function/tree/{branch}/spring-cloud-function-adapters/spring-cloud-function-adapter-aws[AWS
Lambda], and https://github.com/spring-cloud/spring-cloud-function/tree/{branch}/spring-cloud-function-adapters/spring-cloud-function-adapter-azure[Azure].
https://github.com/spring-cloud/spring-cloud-function/tree/main/spring-cloud-function-adapters/spring-cloud-function-adapter-aws[AWS
Lambda], and https://github.com/spring-cloud/spring-cloud-function/tree/main/spring-cloud-function-adapters/spring-cloud-function-adapter-azure[Azure].

18
docs/modules/ROOT/pages/spring-cloud-function/standalone-web-applications.adoc
View File

@@ -21,13 +21,13 @@ It is primarily to accommodate _stateless serverless patterns_ where you simply
|===
| Method | Path | Request | Response | Status
| GET | /{supplier} | - | Items from the named supplier | 200 OK
| POST | /{consumer} | JSON object or text | Mirrors input and pushes request body into consumer | 202 Accepted
| PUT | /{consumer} | JSON object or text | Mirrors input and pushes request body into consumer | 202 Accepted
| DELETE | /{consumer} | JSON object or text | - | 204 NO CONTENT
| POST | /{function} | JSON object or text | The result of applying the named function | 200 OK
| PUT | /{function} | JSON object or text | The result of applying the named function | 200 OK
| GET | /{function}/{item} | - | Convert the item into an object and return the result of applying the function | 200 OK
| GET | /\{supplier} | - | Items from the named supplier | 200 OK
| POST | /\{consumer} | JSON object or text | Mirrors input and pushes request body into consumer | 202 Accepted
| PUT | /\{consumer} | JSON object or text | Mirrors input and pushes request body into consumer | 202 Accepted
| DELETE | /\{consumer} | JSON object or text | - | 204 NO CONTENT
| POST | /\{function} | JSON object or text | The result of applying the named function | 200 OK
| PUT | /\{function} | JSON object or text | The result of applying the named function | 200 OK
| GET | /\{function}/\{item} | - | Convert the item into an object and return the result of applying the function | 200 OK
|===
@@ -42,8 +42,8 @@ When POSTing text the response format might be different with Spring Boot 2.0 an
See <<Testing Functional Applications>> to see the details and example on how to test such application.
[[http-request-parameters]]
=== HTTP Request Parameters
As you have noticed from the previous table, you can pass an argument to a function as path variable (i.e., `/{function}/{item}`).
== HTTP Request Parameters
As you have noticed from the previous table, you can pass an argument to a function as path variable (i.e., `/\{function}/\{item}`).
For example, `http://localhost:8080/uppercase/foo` will result in calling `uppercase` function with its input parameter being `foo`.
While this is the recommended approach and the one that fits most use cases cases, there are times when you have to deal with HTTP request parameters (e.g., `http://localhost:8080/uppercase/foo?name=Bill`)