Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
Drupal
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • Development
  • Drupal
  • Issues
  • #76

Closed
Open
Opened Jul 10, 2019 by JonGold@JonGoldDeveloper

Proposal: Don't migrate drush commands to D8

CiviCRM drush commands are incompatible with modern versions of drush.

I investigated this, and each command will need to be rewritten for drush 9/D8. I've created a framework and ported a couple of my most used commands (e.g. drush civicrm-sql-cli, drush civicrm-sql-dump) but there's a compelling argument to simply not rewriting drush and instead making sure that cv has feature parity.

For those who DO think we should continue to maintain the drush commands, I have a branch here: https://github.com/MegaphoneJon/civicrm-drupal-8

Klaas has also submitted a PR to add drush civicrm-api to this branch.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/drupal#76