Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ddev list should not read .ddev/config.yaml (or at least not complain about its version) #957

Closed
rfay opened this issue Jun 29, 2018 · 0 comments
Assignees
Milestone

Comments

@rfay
Copy link
Member

rfay commented Jun 29, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant