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
I want users to have local access to information about current sessions on their machine.
The extensions would be able to show current sessions, query information about it and also do some actions.
This issue is a milestone/tracker for ongoing additions/features related to it.
The design I propose is that mirrord internal proxy will start listening via Unix Socket on ~/.mirrord/mirrord_{pid}.sock.
This will make any API able to find existing mirrord sessions quite easily by ls-ing the ~/.mirrord/ and will also make the control API only available to current user (eliminating potential security boundary issues)
The MVP would be implementing the internal proxy webserver that listens over unix socket (might worth doing it after upgrading dependencies since we have axum/hyper compat issue right now). and serves one API - config that returns current config.
This way we'll be able to implement #2447 in a nice way for IDE extensions.
Task list:
Expose WebServer on int proxy using unix socket
Serve /info to give current configuration
Add logic to IntelliJ to show current mirrord sessions and able to get config of each
Add logic to VSCode to show current mirrord sessions and able to get config of each
Add ability to kill a session (X button?) using the IDE - maybe the IDE can just rm the file as a way of closing?
Add marker for sessions that are ran using operator
Add a section in IDEs for seeing sessions in the cluster (using the operator)
Add layer connections information to /info endpoint - show all processes under the session that mirrord is loaded to
Add listened ports
The text was updated successfully, but these errors were encountered:
I want users to have local access to information about current sessions on their machine.
The extensions would be able to show current sessions, query information about it and also do some actions.
This issue is a milestone/tracker for ongoing additions/features related to it.
The design I propose is that mirrord internal proxy will start listening via Unix Socket on
~/.mirrord/mirrord_{pid}.sock
.This will make any API able to find existing mirrord sessions quite easily by
ls
-ing the~/.mirrord/
and will also make the control API only available to current user (eliminating potential security boundary issues)The MVP would be implementing the internal proxy webserver that listens over unix socket (might worth doing it after upgrading dependencies since we have axum/hyper compat issue right now). and serves one API -
config
that returns current config.This way we'll be able to implement #2447 in a nice way for IDE extensions.
Task list:
/info
to give current configuration/info
endpoint - show all processes under the session that mirrord is loaded toThe text was updated successfully, but these errors were encountered: