Closed dequbed closed 5 years ago
In the CLI the generated usage shell-function does not call exit after printing the usage guide, so commands will continue to run.
If too little parameters are given to config:set this will call config_set with no parameters, resulting in the CLI running
sed -i -r "s/^\s*export\s+${key}.*$//g" $(_p "/etc/${APP_NAME}/conf.d")/*
but with an empty $key:
$key
sed -i -r "s/^\s*export\s+.*$//g" $(_p "/etc/${APP_NAME}/conf.d")/*
which will whoops your entire config in one go. (It deletes every line that starts with export in every file)
In the CLI the generated usage shell-function does not call exit after printing the usage guide, so commands will continue to run.
If too little parameters are given to config:set this will call config_set with no parameters, resulting in the CLI running
but with an empty
$key:which will whoops your entire config in one go. (It deletes every line that starts with export in every file)