Bash Handling Complex Commands as Strings: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 2: Line 2:
* [[Bash#bash_Script_Library|bash]]
* [[Bash#bash_Script_Library|bash]]
=Overview=
=Overview=
The essence of the example is building the command as a string while properly handling combinations of single and double quotes, then executing the command with:
<syntaxhighlight lang='bash'>
$(sh -c "${command}")
echo "${output}"
</syntaxhighlight>
=Example=
<syntaxhighlight lang='bash'>
<syntaxhighlight lang='bash'>
some_header_value='blue'
some_header_value='blue'

Revision as of 19:10, 14 August 2023

Internal

Overview

The essence of the example is building the command as a string while properly handling combinations of single and double quotes, then executing the command with:

$(sh -c "${command}")
echo "${output}"

Example

some_header_value='blue'
some_security_sensitive_header_value='red'
mode=POST
post_body='{"color": "green", "size": 10}'
url=https://example.com

command='curl -s -H "X-SOME-HEADER: '${some_header_value}'" -H "X-SOME-SECURITY-SENSITIVE-HEADER: '${some_security_sensitive_header_value}'" -H "Content-Type: application/json" -X '${mode}
if [[ ${mode} == 'POST' ]]; then
  command="${command} -d '${post_body}'"
fi
command="${command} ${url}"

command_with_masked_token=$(echo "${command}" | sed -e 's/X-SOME-SECURITY-SENSITIVE-HEADER: .*-H/X-SOME-SECURITY-SENSITIVE-HEADER: ***" -H/')
echo "[debug]: ${command_with_masked_token}"
output=$(sh -c "${command}") || { echo "command failed" 1>&2 2>/dev/stderr; }
echo "${output}"