Skip to content
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

switch user with su or su - command in VSCode #9465

Closed
nasiryilmaz opened this issue Feb 1, 2024 · 3 comments
Closed

switch user with su or su - command in VSCode #9465

nasiryilmaz opened this issue Feb 1, 2024 · 3 comments
Labels
feature-request Request for new features or functionality remote Issues in the code server support

Comments

@nasiryilmaz
Copy link

"Hello, I frequently use Visual Studio Code for remote development.
However, in our development and testing workflows, we typically use service accounts or service users rather than our own login credentials.
To switch to these service accounts, we use commands like 'su' or 'su -' within the terminal.

The issue arises when I need to open a new terminal within VSCode and execute 'su' to switch users for editing purposes.
As a result, the VSCode Explorer displays files owned by my user, while the terminal contains files owned by the service user or development user.
This discrepancy creates complications, particularly when pushing and pulling from GitHub since it requires my user credentials.

This situation renders VSCode less practical for remote development.
I would greatly appreciate it if there were a simple switch or feature to change the user context within VSCode,
allowing us to seamlessly work with different users during remote development.
Alternatively, it would be helpful to have a solution for using different user accounts in remote development environments."

@bamurtaugh bamurtaugh added feature-request Request for new features or functionality remote Issues in the code server support labels Dec 12, 2024
@vs-code-engineering vs-code-engineering bot added this to the Backlog Candidates milestone Dec 12, 2024
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Copy link

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

Copy link

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality remote Issues in the code server support
Projects
None yet
Development

No branches or pull requests

2 participants