Most DDEV commands shouldn't fiddle with the .ddev directory
Actual Behavior
Every time ddev describe or ddev list or even ddev version runs, it forces a mutagen re-scan of everything and refreshes enormous parts of the .ddev directory.
This matters mostly when people are using the PhpStorm plugin, which checks status every few seconds. So every time it does a ddev describe -j (I think) mutagen gets kicked off, does a full reconciliation, and has to re-copy every generated thing in the .ddev directory.
Steps To Reproduce
Enable mutagen
ddev mutagen logs (you may have to do this a couple times before it works
ddev version
See the files get re-scanned and recreated.
Alternately just watch ddev mutagen logs when Phpstorm with the plugin is running.
Anything else?
I really don't think we should have to update all those things on every command? Maybe just on start?
Expected Behavior
Most DDEV commands shouldn't fiddle with the .ddev directory
Actual Behavior
Every time
ddev describeorddev listor evenddev versionruns, it forces a mutagen re-scan of everything and refreshes enormous parts of the .ddev directory.This matters mostly when people are using the PhpStorm plugin, which checks status every few seconds. So every time it does a
ddev describe -j(I think) mutagen gets kicked off, does a full reconciliation, and has to re-copy every generated thing in the .ddev directory.Steps To Reproduce
ddev mutagen logs(you may have to do this a couple times before it worksddev versionAlternately just watch
ddev mutagen logswhen Phpstorm with the plugin is running.Anything else?
I really don't think we should have to update all those things on every command? Maybe just on start?