Having configurable content stages

Problem/Motivation

In a development process it is sometimes necessary, to have dummy and and default content. Like having structural pages with menu items delivered to a customer, but for example News A, B and C should only end up on the development server.

For a development workflow that would mean, that it needs different content folders and an ability to mark content to be exported to one or the other folder. Being able to mark content individually would be a nice to have, but one could use the options for the drush commands to archive that.

I had a hard time getting my had around the $lable parameters for csi and cse drush commands, to have the ability to use different folders. As far as I can see, it isn't really used and the usage of content_sync_get_content_directory() with a hardcoded 'sync' option in many places, makes it even harder to configure the folder that way.

I ended up with custom drush commands, that overwrite $content_directories['sync'] before calling the drush commands from content_sync module.

class MyContentSyncCommands extends ContentSyncCommands {

  /**
   * Import content from custom folder.
   *
   * @usage my:importContent
   *   Import Content from custom folder.
   *
   * @command my:importContent
   * @aliases myic
   */
  public function importContent() {

    global $content_directories;
    $content_directories['sync'] = '../config/content_live';

    $options = [
      'entity-types' => '',
      'uuids' => '',
      'actions' => '',
      'skiplist' => FALSE,
    ];

    parent::import(NULL, $options);
  }
}

I have in mind creating config entities that would hold the folder and information about what to export, like in the config_split module and wanted to know, what your plans are about that. It seems that the you had something in mind with the $lable parameter,

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes