`wp config create` would benefit from clear path to defer all parameter initialization. about config-command HOT 2 OPEN

Thanks for the suggestion, @JollyWizard !

I'm open to the idea of making --dbname=<dbname> and --dbuser=<dbuser> optional. This is relevant for SQLite support too (#167). However, if we did so, we'd need to mark it as a breaking change, because there's some rare scenario where a script could be dependent on the current error behavior if dbname or dbuser are missing.

We're likely to tag a WP-CLI 3.0.0 in the next year (https://github.com/wp-cli/wp-cli/milestone/70), and could include this change in that release.

Another option (not necessarily a good one) is to introduce a wp config init or similar command that makes a very basic wp-config.php and incorporates different behavior.

cc @wp-cli/committers if there are other opinions.

from config-command.

I'd really like to see that in wp 3.0. Whatever the solution used, this would be really useful.

from config-command.