Hi Alexey,
thanks for your response.
About the environment properties, makes sense. Although, I think it's a different issue from interactive value prompting.
I put the environment properties in there since i thought they could share the same foundation, e.g. same substitution/defaults syntax.
While conditions and force are interesting features, you can achieve repeatable script executions by using batches which make a script an atomic action, i.e. everything in the script will be applied or rolled back.
Sorry, my explenation concerning repeatable script executions wasn't precise enough. What i'm looking for is a way to repeat the execution (with corrected parameters) in case of a missconfiguration (wrong IP, DB port, etc.). Since the CLI can't recognize a misconfigured DB port i doubt that batches can help in this case.
The force in the suggested form (for operations especially) won't be implemented. For some commands, perhaps. In general, though, I, personally, don't like the idea... but I see your point. Conditions are interesting.
Conditions as an alternative to force would be absolutely okay. I just suggested the force (probably "override" would be a better name) option since i thought it would be easier to implement than conditions.
Can you make any predictions about if an when parameter substitution and conditions could be available? As i mentioned in my initial post i'm currently evaluating which way to go concerning the scipt automation and it would be great if we could accieve that with the CLI and discard additional scripting languages in the near future.