auth:renew should respect set alternative AccountManager url about sfcc-ci HOT 6 CLOSED

I think respecting the alternative Account Manager host passed to sfcc-ci client:auth via -a flag, is not trivial. The setting is only visible to the current Node process running the command, this includes playing with process.env.SFCC_LOGIN_URL and setting the host. One option would be to persist the setting into the CLIs local configuration. That however, has the downside that it would be visible across shells and sessions.

I'd personally favor to deprecate the flag -a for command sfcc-ci client:auth and rely on env var SFCC_LOGIN_URL.

from sfcc-ci.

@wundrian is this still relevant?

from sfcc-ci.

I'll need to retest, but the need hasn't gone away.

from sfcc-ci.

@wundrian Do you make use of the env var SFCC_LOGIN_URL? This is respected by obtainToken. I did a quick test, see below:

$ export SFCC_LOGIN_URL=<your-alt-am-host>
$ sfcc-ci client:auth '<client-id>'' '<client-secret>' --renew
Authentication succeeded Auto-renewal enabled.
$ sfcc-ci client:auth:renew
Authentication renewal succeeded

Feedback?

from sfcc-ci.

Good point. Our invocations go via the -a <am-host>, but I think we can work with environment variables.

from sfcc-ci.

I've created #129 for the removal of flag -a,--authserver and closing this one.

from sfcc-ci.