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
Currently lando pull uses branch names to select the environment to pull from however environment aren't always directly linked to branches so using environment names would be best in this situation.
Can we update the lando pull command for lagoon recipes to select the environment name to pull from for database and files?
For extra points it would be great to support the environment global unique name [lagoon-project]-[environment-name] as well as just providing the environment name as the project would be known in the context of the command. The following examples should ideally all be possible for the best UX:
1. lando pull --database [environment-name]
2. lando pull --database [lagoon-project]-[environment-name]
3. lando pull --database @lagoon.[lagoon-project]-[environment-name]
The text was updated successfully, but these errors were encountered:
3 was a little more complicated and the @ sign is more of a dush execution symbol rather than the alias. Let's discuss, and if that format is still required, we can spend more time on it.
Currently
lando pull
uses branch names to select the environment to pull from however environment aren't always directly linked to branches so using environment names would be best in this situation.Can we update the
lando pull
command for lagoon recipes to select the environment name to pull from for database and files?For extra points it would be great to support the environment global unique name [lagoon-project]-[environment-name] as well as just providing the environment name as the project would be known in the context of the command. The following examples should ideally all be possible for the best UX:
The text was updated successfully, but these errors were encountered: