Project/Environment context

I asked Amazee:

Say I want to do a bunch of commands with the same project/environment (things like lagoon list deployments -p vcat-website-drupal8-2020 -e deploy/lagoon/production and the like). Is there a way to specify the project/environment once?

• Ideal in a way would be if the Lagoon command actually dropped you into a special shell, and you could select a project/environment that would then appear in the prompt.
• Another good option would be the kubectl-style config where it's possible to set a default context/cluster
• Failing that, if there were at least an environment variable I could set, that'd be great.

Ben then commented:

We do support the cluster/context, but this is only really used for choosing a lagoon cluster to target. We could extend this to also support environment and project too. The biggest issue with this is that some commands like adding variables do different things if an environment is defined, so having it always defined could be tricky

We are working on an entire CLI overhaul to bring it more in line with how kubectl works though, but this is far off at the moment

No file, test, or specific entry point is named. Start by tracing the existing cluster/context handling and the commands whose behavior changes when a project or environment is defined. Done would require an agreed approach for persistent project/environment context and consistent behavior across affected commands.