balena env rm <id> fails silently without --config option

[shawaj]

Expected Behavior

When running balena env rm <id> on a config variable, without specifying the --config flag, it should throw an error. Perhaps something like "ERROR: this is a config variable. Did you mean to use the --config flag?" or something similar.

Actual Behavior

When running balena env rm <id> on a config variable, without specifying the --config flag you get the following output:

% balena env rm 1689                     
? Are you sure you want to delete the environment variable? Yes

However when you then check the variables again for this fleet, the variable still shows, despite it looking like it was sucessful.

The issue, of course, is the missing --config flag - however this is not clear by the output and this should fail gracefully rather than silently like it does now

Steps to Reproduce the Problem

Try to delete a config variable without using the --config flag

Specifications

• balena CLI version: 16.7.5