Need clarity on destination of drush command

Created on 15 December 2016, over 7 years ago
Updated 22 February 2024, 4 months ago

The help text of the drush command shows the following output:

 drush config-partial-export --config  Export configuration; Save files in a backup directory named 
 core.date_format.long                 config-export.

Arguments:
 config                                    Configuration keys, comma separated                         
 label                                     A config directory label (i.e. a key in $config_directories 
                                           array in settings.php). Defaults to 'sync'

Upon reading this, I expect to be able to supply both the list of partial configs and the specific config directory I want to export it.

Upon entering a valid or invalid config directory label, I am prompted to "Choose a destination." with a list of the targets (that also show the same labels I entered).

We need to do one of the following:

1. Switch "destination" to an option that prompts these options, e.g. "--select-destination"

2. Fix the destination parameter (or, alternatively remove it)

3. Both

My recommendation is to respect an optional destination parameter (fix it) and offer the --select-destination for the current behavior. This seems to be the most robust and flexible option.

✨ Feature request
Status

Fixed

Version

1.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States nerdstein United States

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡§πŸ‡ͺBelgium iampuma Frankfurt am Main, Germany

    Was not working for 2.x, following patch adds destination parameter. Files argument can be left out to replace only the *yml files detected in the destination folder.

  • πŸ‡§πŸ‡ͺBelgium iampuma Frankfurt am Main, Germany

    Sorry, wrong patch for #6. Can not edit the patch from the comment in #6.

Production build 0.69.0 2024