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, if the user manually provides a URL (e.g. via --url) which is different from the URL encoded in the org auth token they are using, the CLI exits with an error stating that the provided URLs do not match. This provides a poor user experience (see #2089, for example).
The URL encoded in the auth token is likely the URL that the user actually wishes to use, so instead of erroring when there is a URL mismatch, we should simply raise a warning (or maybe just an info message) whenever a user manually provides a URL in addition to an org auth token, which encodes a URL, and we should proceed with using the URL in the org auth token.
This would make it clear to users that setting a URL is unnecessary when using an org auth token, and would generally provide a better user experience.
The text was updated successfully, but these errors were encountered:
Currently, if the user manually provides a URL (e.g. via
--url
) which is different from the URL encoded in the org auth token they are using, the CLI exits with an error stating that the provided URLs do not match. This provides a poor user experience (see #2089, for example).The URL encoded in the auth token is likely the URL that the user actually wishes to use, so instead of erroring when there is a URL mismatch, we should simply raise a warning (or maybe just an info message) whenever a user manually provides a URL in addition to an org auth token, which encodes a URL, and we should proceed with using the URL in the org auth token.
This would make it clear to users that setting a URL is unnecessary when using an org auth token, and would generally provide a better user experience.
The text was updated successfully, but these errors were encountered: