Skip to content

change sequential:true to strategy:sequential #301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NarcisDavins wants to merge 1 commit into
base: dev-v3.0-community
Choose a base branch
from
Open

change sequential:true to strategy:sequential #301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions endpoints/sequential-proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ To enable the sequential proxy, you need to add in the endpoint definition the f
"endpoint": "/hotels/{id}",
"extra_config": {
"proxy": {
"sequential": true
"strategy": "sequential"
}
}
}
Expand Down Expand Up @@ -156,7 +156,7 @@ The configuration needed for this example is:
],
"extra_config": {
"proxy": {
"sequential": true
"strategy": "sequential"
}
}
}
Expand All @@ -173,9 +173,9 @@ On the other hand, when your backend is `no-op` you can access the full response


## Passing previous values outside the `url_pattern`
By setting the flag `"sequential": true`, the responses of the backends are available in the following `url_pattern`s. But there will be times when you don't want the value in the `url_pattern`. You can reuse the payload of previous responses elsewhere by propagating the values using the `sequential_propagated_params` attribute. These are the sequential flags you have on the `proxy` configuration:
By setting the config `"strategy": "sequential"`, the responses of the backends are available in the following `url_pattern`s. But there will be times when you don't want the value in the `url_pattern`. You can reuse the payload of previous responses elsewhere by propagating the values using the `sequential_propagated_params` attribute. These are the sequential flags you have on the `proxy` configuration:

{{< schema data="endpoint_extra_config.json" property="proxy" filter="sequential,sequential_propagated_params" title="Fields of endpoint's proxy property">}}
{{< schema data="endpoint_extra_config.json" property="proxy" filter="strategy,sequential_propagated_params" title="Fields of endpoint's proxy property">}}


### Example: Setting a previous response as the payload of the next
Expand All @@ -192,7 +192,7 @@ You can copy the code of this endpoint and test locally (it requires you to have
"endpoint": "/sequential/propagate-body",
"extra_config": {
"proxy": {
"sequential": true,
"strategy": "sequential",
"sequential_propagated_params": ["resp0"]
}
},
Expand Down