...
You can use the $uri:pipeline scheme also in order to execute an adhoc pipeline. This is an adhoc a combination of commands to be executed in serial, one after another from left to right. The format is like this:
...
This approach is handy in case you would like to call one or more commands in serial without persisting a pipeline for this.
The Path path part of the URI is empty and only the query string is given, starting with ? whereas the name of a query param is the name of the command. The optional query param value contains the parameters to the command whereas name and value is separated by a colon : and multiple params are separated by by a semicolon ; . In case a command parameter is a default command parameter, it can be used without any parameter name prefix in the URI. For example:
| Code Block |
|---|
$uri:pipeline:?uri.get="uri:http://host/path;body=abc"&data.filter.jmespath="query:[?id=12]" |
Since uri of command In case a command parameter is a default command parameter, it can be used without any parameter name prefix in the URI. So the example from above can be simplified to this:
| Code Block |
|---|
$uri:pipeline:?uri.get="http://host/path"&data.filter.jmespath="[?id=12]" |
Since uri of command uri.get and query of command data.filter.jmespath are default parameters, these parameter names can be skipped. But this must be then the only parameter given to the command. If you need more parameters than one parameter per command, the pipeline must be written including the parameter names in the query like this:
...
.
...
$uri:property
This custom URI points to a property in the property store.
...