-
Notifications
You must be signed in to change notification settings - Fork 2
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
Start of the Extension: Making an SSH Connection #1
Comments
|
So is your goal to SSH to the remote host so that you can run |
For the time being, yes for the management hub. As for the future, I intend to include UI elements that translate into hzn commands. |
Yes @joewxboy , this would be to start the foundation of the extension. In the future, as Jeff mentioned, we would add more features regarding how it interacts with the Management Hub. If you think some commands or features should be prioritized, feel free to let us know! |
It sounds like a great start and the right direction. It's a lot less problematic than using the APIs directly. |
Direction of how we connect and use HZN commands changed. Will be closing this issue for now. See issue forum #2 |
As discussed today, the base of the extension will work off a connection between a docker container and a pre-existing Open Horizon Management Hub terminal. So far, we have decided to work with the default container that the template extension for Docker Desktop uses, which is an Arch image. To test with our most familiar and already installed instance of Open Horizon Management Hub, we will try to SSH connect to an Ubuntu instance of it. Thus our goals for the following 2 weeks:
We will work primarily with the backend for now. Leave some features from the front-end like being able to specify the specific Ubuntu image for later, as well as other information we might want to get from the Ubuntu instance to the Docker Desktop Extension.
The text was updated successfully, but these errors were encountered: