Problem/Motivation

The drush commands for config import and export work with config split already for quite a while.
Maintaining the functionality in only one place makes sense.

Steps to reproduce

Proposed resolution

Deprecate not passing an argument to the commands.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

bircher created an issue. See original summary.

  • bircher committed 25e5d7a on 8.x-1.x 
    Issue #3166128 by bircher: Deprecate config-split:export/import without...
bircher’s picture

bircher
Location 🇨🇿
commented
Status: Active » Fixed

  • bircher committed 25e5d7a on 2.0.x 
    Issue #3166128 by bircher: Deprecate config-split:export/import without...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

komlenic’s picture

komlenic commented

I'd like to know the motivation for this issue and the warning message, since it is not clear to me from the title and description. Does this mean that Drupal Console will eventually not be supported for use with Config Split? Thanks!

bircher’s picture

bircher
Location 🇨🇿
commented

Thanks for the question.
The command without the split argument was first added because at the time neither drush nor drupal console used cores sync storage. Drush started using that with Drush 8.1.10. Drupal console unfortunately never did.
The native drush command has a preview and all sorts of nice things that I don't have the time to maintain in config split.
The native drupal console command will start working with config split once they support the new core API.
See this issue: https://github.com/hechoendrupal/drupal-console/issues/4267
So with drupal console you can currently not reasonably expect all the configuration management features to work and it is outside of the scope of config split to maintain drupal console commands to fix the ones from drupal console itself.
If you are interested in that then you can either create your own module with import/export commands for drupal console that work (it would be completely agnostic to config split) or even better make a PR for drupal console to support them thus fixing the above mentioned issue.