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 the cli assumes that it can open a browser on the user's behalf when running cloud login which almost always not available in CI environments. Unless I'm missing some configuration option, it seems a --open-browser=false flag would be desirable to facilitate CI workflows or other use cases where access to xdg-open or other ways of opening a user's browser is not available.
The text was updated successfully, but these errors were encountered:
@rio you can set MCC_CLIENT_ID and MCC_CLIENT_SECRET to override this logic entirely. If those are set it will authenticate on its own. We run the CLI in the pipeline in the same way.
Still, it would be healthy to just print the URL and wait for the auth code if it was unable to open the browser.
I might whip up something but I'm a bit swamped currently.
That is fair, if we have no creds set and don't open a browser we should just error out instead. That way at least the user knows what is going on. If you want to take a look feel free, I will otherwise set it on the backlog
Currently the cli assumes that it can open a browser on the user's behalf when running
cloud login
which almost always not available in CI environments. Unless I'm missing some configuration option, it seems a--open-browser=false
flag would be desirable to facilitate CI workflows or other use cases where access to xdg-open or other ways of opening a user's browser is not available.The text was updated successfully, but these errors were encountered: