-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support $BROWSER envar #8596
Comments
the featured issue in still missing in the file folio for long timr please try to settle the periodic info on it for betterment of the study. |
Thanks for the sso login feature request. Have you tried setting |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
@tim-finnigan thanks! sorry, I missed. it is supported already. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the feature
I want the BROWSER variable to be referenced when opening the browser with a command such as
aws sso login
.Use Case
We use wslview to open our browser in WSL.
However, there are many packages that easily install xdg-open as a dependency even though it is not available in WSL.
I don't want such xdg-open which does not work, to be called, so I set the BROWSER environment variable to "wslview" for various tools, but the AWS CLI ignores this.
Proposed Solution
I would like the following solution.
Other Information
No response
Acknowledgements
CLI version used
aws-cli/2.15.19 Python/3.11.8 Linux/5.15.146.1-microsoft-standard-WSL2 source/x86_64.arch prompt/off
Environment details (OS name and version, etc.)
Arch Linux 5.15.146.1-microsoft-standard-WSL2 x86_64
The text was updated successfully, but these errors were encountered: