Feature request:
With the ddev pull platform command prompt the user for the environment they wish to pull from, defaulting to the current checked out branch.
Reasoning:
Often when working with colleagues, we need to debug/troubleshoot a feature we're developing in a non-production branch. This often involves needing to sync that environment's database into the local development environment to further work on. The current implementation of ddev pull platform limits the user to the environment they choose during the initial ddev get platformsh/ddev-platformsh or manually updating the .ddev/config.yaml file.
Ideally, when initiating the ddev pull platform command, the user would be given a choice of currently active platform.sh environments, with the default selection matching the current locally checked out environment. This would allow for users to quickly and easily replicate platform.sh environments locally without having to manually update files.
Feature request: With the
ddev pull platform
command prompt the user for the environment they wish to pull from, defaulting to the current checked out branch.Reasoning: Often when working with colleagues, we need to debug/troubleshoot a feature we're developing in a non-production branch. This often involves needing to sync that environment's database into the local development environment to further work on. The current implementation of
ddev pull platform
limits the user to the environment they choose during the initialddev get platformsh/ddev-platformsh
or manually updating the.ddev/config.yaml
file.Ideally, when initiating the
ddev pull platform
command, the user would be given a choice of currently active platform.sh environments, with the default selection matching the current locally checked out environment. This would allow for users to quickly and easily replicate platform.sh environments locally without having to manually update files.