1248b147ac
Fixes #7975 This changes the InputMode for the CLI to always be: InputModeProvider | InputModeVar | InputModeVarUnset Which means: * Ask for provider variables * Ask for user variables _that are not already set_ The change is the latter point. Before, we'd only ask for variables if zero were given. This forces the user to either have no variables set via the CLI, env vars, tfvars or ALL variables, but no in between. As reported in #7975, this isn't expected behavior. The new change makes is so that unset variables are always asked for. Users can retain the previous behavior by setting `-input=false`. This would ensure that variables set by external sources cover all cases. |
||
|---|---|---|
| .. | ||
| apply | ||
| apply-config-invalid | ||
| apply-destroy-targeted | ||
| apply-error | ||
| apply-input | ||
| apply-input-partial | ||
| apply-sensitive-output | ||
| apply-shutdown | ||
| apply-vars | ||
| get | ||
| graph | ||
| init | ||
| parallelism | ||
| plan | ||
| plan-emptydiff | ||
| plan-invalid | ||
| plan-vars | ||
| push | ||
| push-input | ||
| push-input-partial | ||
| push-no-upload | ||
| push-tfvars | ||
| refresh | ||
| refresh-output | ||
| refresh-unset-var | ||
| refresh-var | ||
| validate-invalid | ||
| validate-valid | ||