After #2242947: Integrate Symfony Console component to natively support command line operations is fixed, we can start porting the shell scripts in ./core/scripts to console commands. This issue keeps track of which scripts are to be ported and how far along the ports are.

Script Issue
./core/scripts/dump-database-d6.sh
./core/scripts/dump-database-d7.sh
./core/scripts/generate-d6-content.sh
./core/scripts/generate-d7-content.sh
./core/scripts/password-hash.sh #2289409: Port password-hash.sh to a console command
./core/scripts/rebuild_token_calculator.sh #2289447: Port rebuild_token_calculator.sh to a console command
./core/scripts/run-tests.sh
./core/scripts/transliteration_data.php.txt
./core/scripts/update-countries.sh #2289611: Port update-countries.sh to a console command

Comments

Xano’s picture

Issue summary: View changes
larowlan’s picture

Can I bags one?

Damien Tournoud’s picture

So feature freeze is absolutely meaningless?

Xano’s picture

Issue tags: +test coverage

Can I bags one?

Which means?

So feature freeze is absolutely meaningless?

Damien, please stop being sarcastic. Nobody said this has to go into 8.0. There are always later minor versions we can add this to. Add the very least, converting the scripts allows us to increase test coverage. We can also port the code without breaking BC, if we want to.

larowlan’s picture

Can I bags one = I want to claim one, keen

larowlan’s picture

Issue summary: View changes

Added rebuild token calculator

jibran’s picture

I think we should move all the work to a sandbox so that it can all be merged at once when core committers are ready to merge it.

Xano’s picture

What would be the advantage of that? AFAIK sandboxes are commonly used to work on large features that must go into core as a whole, but that are too big to add in one patch. These are a number of smaller features that bear no relationship to each other. In other words: we can decide to add only a few of them without consequences. I'd rather avoid the 'obscurity' of a sandbox (they are harder to find than issues).

jibran’s picture

My idea was to combine all the above patches and #2242947: Integrate Symfony Console component to natively support command line operations and post it here or to a sandbox. Because it is a feature request and we are in feature freeze until 8.1.x atleast and when issue is ready for commit we can pull up a patch and be done with it.

Xano’s picture

Issue summary: View changes
jmolivas’s picture

Since we have been working on this contributed project http://drupalconsole.com/ there is already code that could be reused on core or contributed space to facilitate the use of Console component in order to enable Drupal users to create commands easily.

Feel free to ping me or any console maintainers for help writing this commands.

Fabianx’s picture

Version: 8.0.x-dev » 8.1.x-dev
Status: Active » Postponed

This is 8.1 material.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Chi’s picture

Status: Postponed » Active

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

pingwin4eg’s picture

Category: Task » Plan
Issue summary: View changes
Status: Active » Postponed

Fixed link for update-countries.sh.

I suppose this is postponed on the integration issue.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jibran’s picture

andypost’s picture

Status: Postponed » Active

This should be opened again cos there are commands implemented already, few ones are in progress like #2911319: Provide a single command to install & run Drupal

As I see here is commands that depends on bootstrap & ones like install that don't

The question of error output handling & exit codes #2242947-98: Integrate Symfony Console component to natively support command line operations is not the same in current commands - needs separate issue to decide

Better to discus it here instead of issue that has 100 comments with patches that no longer "integration issue"

Mile23’s picture

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.