v1.24.2: Preventing ddev config in parent directory has significant side-effects #6937
Description
Expected Behavior
See Drupal Slack @kevinquillen : https://drupal.slack.com/archives/C5TQRQZRR/p1737819544903659
ddev config should work even if a module of a Drupal project has a .ddev in it (which often happens when using the ddev/ddev-drupal-contrib add-on)
Actual Behavior
In v1.24.2, if you do a ddev composer install that happens to pull in a component (like a Drupal module) which had a .ddev directory, you can't ddev config the project.
The example in the Slack thread was:
Failed to get project(s): 'ddev config' is not allowed in /home/kevinquillen/Projects/cci because a project exists in the subdirectory /home/kevinquillen/Projects/cci/docroot/modules/contrib/svg_image_field
Run 'ddev stop --unlist' for all projects in subdirectories of the current directory first to reenable 'ddev config'
This is an unexpected result of the wonderful
Steps To Reproduce
In a Drupal 11 project:
ddev composer require --dev drupal/svg_image_field:dev-2.3.x
Then ddev config the project.
Anything else?
No response