This is an automated email from the ASF dual-hosted git repository. heneveld pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit 5743a1590bda055592b29919c1b34a7995724dde Author: Alex Heneveld <[email protected]> AuthorDate: Wed Mar 22 16:23:02 2023 +0000 fix reference in http workflow step referring to query params --- guide/blueprints/workflow/steps/steps.yaml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/guide/blueprints/workflow/steps/steps.yaml b/guide/blueprints/workflow/steps/steps.yaml index 5bf117f3..522cc0bd 100644 --- a/guide/blueprints/workflow/steps/steps.yaml +++ b/guide/blueprints/workflow/steps/steps.yaml @@ -232,9 +232,8 @@ summary: Sends an HTTPS (or HTTP) request and returns the response content and code. shorthand: '`http ENDPOINT`' input: | - * `endpoint`: the URL to connect to, optionally omitting the protocol and slash prefix if `https://` is intended - (e.g. just the host and any path); per URL standard any unusual characters such as query parameters should be URL-encoded, - so if e.g. passing parameters containing spaces, `params` should be used instead of `host/path?param=${value}` + * `endpoint`: the URL to connect to; protocol can be omitted to use the default `https://`; + query parameters can be supplied via the separate `query` input and/or here as `?param1¶m2` * `query`: a map of query parameters to URL encode and add to the URL * `body`: an object to be serialized and sent as the body (or just set as body if it is an array of bytes) * `charset`: the character set to use to convert between byte arrays and strings for the request body and response content;
