Hide Forgot
Description of problem: when add a env var via `rhc env set= -a $appname`, it return ok, and new-added variables can list under `rhc env list` # rhc env set= -a app1 Setting environment variable(s) ... done # rhc env list -a app1 set= But `rhc env-set= -a $appname` can not add successfully. Version-Release number of selected component (if applicable): STG(devenv-stage_549) rhc 1.16.9 How reproducible: always Steps to Reproduce: 1.Create an app 2.set variables like following: rhc env set= -a $appname 3.check variables under `rhc env list` Actual results: # rhc env set= -a app1 Setting environment variable(s) ... done # rhc env list -a app1 set= Expected results: It can not add successfully. Additional info:
`rhc env set= -a app1` should be invalid syntax. Instead, it is matching the `rhc env set` command, then treating "set=" as an argument as well. Problem is in Commander::Runner.valid_command_names_from, which matches the full command against word boundaries, so "env set\b" matches "env set=". A bug against Commander is probably in order.