ddev: Pantheon integration problems in 1.13.1, fixed with re-authorization

Describe the bug After updating to ddev 1.13.1 this morning I’m unable to successfully run ddev config pantheon on projects

To Reproduce

ddev poweroff
brew update && brew upgrade
ddev config pantheon

Screenshots Screen Shot 2020-03-10 at 9 45 31 AM Screen Shot 2020-03-10 at 9 41 32 AM

Version and configuration information (please complete the following information):

macOS 10.15.3
Docker 19.03.5
ddev 1.13.1 (previously 1.13.0)
project default config.yml
no custom configurations

Additional context

pantheon config in ~/.ddev/ was in tact, but re-authorizing seems to have fixed it.
wasn’t sure an issue was appropriate, but pantheon auth wasn’t mentioned in the release notes and figured I ought to make sure you’re aware of the problem

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 18 (14 by maintainers)

Most upvoted comments

No issues that I’ve noticed so far through the release candidates or 1.14.0

andy-blum on Apr 22, 2020

Your screenshots show you using terminus on the host. I guess that’s to demonstrate what’s out there on Pantheon? If you’re able to demonstrate the issue again (I doubt it) it would be better to show terminus usage inside the container and show the terminus config.

I don’t know of any reason for losing your terminus auth going from 1.3.0 to 1.3.1, unless some docker volumes were deleted.

rfay on Mar 10, 2020