You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A user in Drupal's #ddev pointed out after an upgrade that loads of warnings like this were emitted after they upgraded to v0.20.0:
$ ddev list
Your .ddev/config.yaml version is v0.20.0, but ddev is version v0.20.0-1-g1995aac2-dirty.
Please run 'ddev config' to update your config.yaml.
ddev may not operate correctly until you do.
Your .ddev/config.yaml version is v0.19.0-17-g6bb97eda, but ddev is version v0.20.0-1-g1995aac2-dirty.
Please run 'ddev config' to update your config.yaml.
ddev may not operate correctly until you do.
NAME TYPE LOCATION URL(s) STATUS
d7git drupal7 ~/workspace/d7git http://d7git.ddev.local running
https://d7git.ddev.local
d8git drupal8 ~/workspace/d8git http://d8git.ddev.local running
https://d8git.ddev.local
To Reproduce
In a couple of running projects, set the config.yaml version key to something other than the current ddev version, then ddev list. You'll get lots of warnings like above, but with no context about which project the problem exists in.
Expected behavior
There's no reason for ddev list to emit this warning
The warning should identify the project that it's associated with anyway.
Version and configuration information (please complete the following information):
This happens with any recent version of ddev that checks the config.yaml version.
The text was updated successfully, but these errors were encountered:
Describe the bug
A user in Drupal's #ddev pointed out after an upgrade that loads of warnings like this were emitted after they upgraded to v0.20.0:
To Reproduce
In a couple of running projects, set the config.yaml version key to something other than the current ddev version, then
ddev list
. You'll get lots of warnings like above, but with no context about which project the problem exists in.Expected behavior
Version and configuration information (please complete the following information):
This happens with any recent version of ddev that checks the config.yaml version.
The text was updated successfully, but these errors were encountered: