Hi all,
TL;DR: we can achieve what we want with the existing $BRCLI_HOME
environment variable. Therefore suggest we defer this!
---
It turns out we already support the alternative suggestion of "custom
configuration file" by using the environment variable $BRCLI_HOME. We
discovered that our
Aled,
I think i prefer the idea of a profile as its the same pattern that kubectl
sorta follow with contexts.
I assume we would have a way to delete a profile maybe `br logout --profile
staging`
For use within build / test pipelines I can see the `.brooklyn_cli` being
supplied so to give
Aled,
I like the endpoint option but I think it would imply that the username and
password parameters of br login should be optional in the case that they
have already been stored.
Possibly an alternative would be an init command a bit like the gcloud init
command but non-interactive. br
Hi all,
TL;DR: I want to add `--endpoint` to the br command, because `br login`
has global scope.
We at Cloudsoft use `br` in our qa jenkins jobs. However, the `br login`
command has global scope. This means that two jobs run on the same
jenkins slave (both running as user `jenkins`) will
