Add rtk ddev / drush support (top unhandled command in rtk discover)

Open
#3,288 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
php, rust
Domain
cli, tooling

Research direction

Start at the rtk discover entry point and inspect the existing rtk docker, rtk kubectl, composer-style, and test filters. Trace how wrapped commands are routed, then define the ddev and fin delegation behavior and the new Drush compact-output handling. Done means the listed ddev/fin command forms route to the matching filters and verbose Drush output is condensed as described.

Written by the indexing model from the issue text.

Description

area:cli enhancement help wanted priority:medium

rtk discover on our project flags ddev drush as the top unhandled command:

Command        Count    Example
ddev drush       62     ddev drush pml --status=enabled 2>&1

Also seeing lower-volume unhandled ddev/related commands in the same report:
ddev exec 15 ddev exec vendor/bin/phpunit --version...
ddev composer 3 ddev composer show drupal/paragraphs 2...
fin status 2 fin status 2>&1
ddev describe 2 ddev describe 2>&1
fin drush 1 fin drush status 2>&1

Drush output (pml, status, php:eval, etc.) is verbose and would benefit from
the same compact-output treatment as rtk docker/rtk kubectl — strip
boilerplate/padding, truncate long module lists, group by status.

ddev/fin are just wrappers around drush/composer/phpunit inside a
container, so a generic rtk ddev <subcommand> that detects the wrapped
command and delegates to the matching existing filter (drush → new filter,
composer → existing rtk composer-style output, phpunit → existing test
filter) would cover most of this in one pass.

Environment: rtk 0.42.4, macOS, Drupal 9/10 project via ddev.

Dominant language
Rust
Stars
81.1k
Forks
5.1k
Avg merge
4d 11h
Merged PRs (30d)
40

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rtk-ai/rtk

All issues in rtk-ai/rtk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.