Describe the bug
This mostly matters for cmd tests that try to remove sites just to clean up, but it should be fixed in general.
The reason it doesn't work in the cmd tests is that ddev rm -RO <projectname> doesn't work if the project is not currently running or stopped.
To Reproduce
mkdir junk && cd junk
ddev config --project-type php
ddev rm -RO junk
You'll see the junk project (added by ddev config) is still in ~/.ddev/global_config.yaml
Also:
- Run the cmd tests. You'll see lots of crap in the global_config.yaml afterwards.
Expected behavior
- ddev rm -RO should work even if project has been rm'd or never even run.
- tests should not leave crap in global config
This issue should fix both issues
Describe the bug
This mostly matters for cmd tests that try to remove sites just to clean up, but it should be fixed in general.
The reason it doesn't work in the cmd tests is that
ddev rm -RO <projectname>doesn't work if the project is not currently running or stopped.To Reproduce
You'll see the junk project (added by ddev config) is still in ~/.ddev/global_config.yaml
Also:
Expected behavior
This issue should fix both issues