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
Is your feature request related to a problem? Please describe.
Currently when a project uses active/standby deployments, it is up to the user to know or look up which environment is active before running commands.
Describe the solution you'd like
For all commands that accept the --environment flag, add a new optional --production flag to target the active/standby environment for a project. eg
lagoon ssh \
--project=foo \
--production=active
# Opens a ssh session on foo-prod-left
Describe alternatives you've considered
If there was another lagoon command which showed the active/standby status you could potentially subshell output from that command into the --environment flag. eg
# Hypothetical active/standby output from list environments command
$ lagoon list environments --project foo
ID NAME DEPLOYTYPE ENVIRONMENT OPENSHIFTPROJECTNAME ROUTE STATUS
xxxxx prod-left branch production foo-prod-left https://www.foo.com active
xxxxx prod-right branch production foo-prod-right https://standby.foo.com standby
# Hypothetically use subshell to inject that into another command
lagoon ssh \
--project foo \
--environment $(lagoon list environments --project foo | grep active | awk '{print $2}')
alas this feature does not exist yet.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently when a project uses active/standby deployments, it is up to the user to know or look up which environment is active before running commands.
Describe the solution you'd like
For all commands that accept the
--environment
flag, add a new optional--production
flag to target the active/standby environment for a project. egDescribe alternatives you've considered
If there was another lagoon command which showed the active/standby status you could potentially subshell output from that command into the
--environment
flag. egalas this feature does not exist yet.
The text was updated successfully, but these errors were encountered: