I don't know if this is just feedback or an actual feature request but here goes. I have been trying to integrate this product into my workflow and have had mixed result. I like a lot of what is happening here but my particular workflow doesn't map well(That might just be a me problem but i wanted to provide feedback if you are interested).
My workflow is managing many many VMs across multiple VPCs. Currently i have something like 300 VMs. What drew me to this product was the desire to make this easier. I had a solution which was a python script wrapping RDP and SSH which was painful and only worked for me not my team. I have dug deep into xpipe setting up things like Password Manager and the REST API. I automated my XPipe management of my connections. However, i found that the underlying abstraction just really is painful for me at the high connection count. At the end of the day i don't really want to save 600 connections, that provides really little value. What i want is to save the like 20 connection templates i use and then just add in the small amount of extra info to finish the connection. Namely the ip or hostname.
Finding the connection I need in a list of 600 connections is painful even with groups. The list being sorted by date created is also not helpful. Also having that many connections is painful cause the ui is not really designed for it. If i were to sum up my issues with xpipe, I would say that its really static. You can only connect via a pre-created connection. You can't do a one off connection or temporary changes. You must clone a connection edit it and then save the connection and then you can launch the actual connection. Even if you never want to connect to that machine again.
So my feature request, would be to allow for dynamic connections. My ideal case would be to allow me to setup Dynamic Connections which would save an arbitrary amount of these settings into a connection and fill in the rest at connection time. For example, I use shared ssh keys and gateway hosts. If i could set everything(ssh gateway, username, password, ssh keys, etc) in a dynamic connection except the hostname/ip and enter that at connect time that would be way more flexible.
The problem i actually need to solve is I need to make connecting to Virtual Private Clouds easier. What i ideally need is to save a connection setup ssh gateway, username, password, ssh keys, etc and then provide a dynamic way to enter the rest. It i could even allow for a plugin or python script to fetch the current list of Hostnames/IPs for the user to pick from. VMs and VPCs can be dynamic and change everyday. Having no easy/quick connections or dynamically fetching of hosts makes it really not work for me.
I know this is not really what xpipe is trying to do but i though i would leave my experiences and thoughts at the very least before i moved on. As it stands i am planning on revamping my SSH/RDP wrapping scripts to solve this issue for my team but as you might imaging that isn't ideal.
I don't know if this is just feedback or an actual feature request but here goes. I have been trying to integrate this product into my workflow and have had mixed result. I like a lot of what is happening here but my particular workflow doesn't map well(That might just be a me problem but i wanted to provide feedback if you are interested).
My workflow is managing many many VMs across multiple VPCs. Currently i have something like 300 VMs. What drew me to this product was the desire to make this easier. I had a solution which was a python script wrapping RDP and SSH which was painful and only worked for me not my team. I have dug deep into xpipe setting up things like Password Manager and the REST API. I automated my XPipe management of my connections. However, i found that the underlying abstraction just really is painful for me at the high connection count. At the end of the day i don't really want to save 600 connections, that provides really little value. What i want is to save the like 20 connection templates i use and then just add in the small amount of extra info to finish the connection. Namely the ip or hostname.
Finding the connection I need in a list of 600 connections is painful even with groups. The list being sorted by date created is also not helpful. Also having that many connections is painful cause the ui is not really designed for it. If i were to sum up my issues with xpipe, I would say that its really static. You can only connect via a pre-created connection. You can't do a one off connection or temporary changes. You must clone a connection edit it and then save the connection and then you can launch the actual connection. Even if you never want to connect to that machine again.
So my feature request, would be to allow for dynamic connections. My ideal case would be to allow me to setup Dynamic Connections which would save an arbitrary amount of these settings into a connection and fill in the rest at connection time. For example, I use shared ssh keys and gateway hosts. If i could set everything(ssh gateway, username, password, ssh keys, etc) in a dynamic connection except the hostname/ip and enter that at connect time that would be way more flexible.
The problem i actually need to solve is I need to make connecting to Virtual Private Clouds easier. What i ideally need is to save a connection setup ssh gateway, username, password, ssh keys, etc and then provide a dynamic way to enter the rest. It i could even allow for a plugin or python script to fetch the current list of Hostnames/IPs for the user to pick from. VMs and VPCs can be dynamic and change everyday. Having no easy/quick connections or dynamically fetching of hosts makes it really not work for me.
I know this is not really what xpipe is trying to do but i though i would leave my experiences and thoughts at the very least before i moved on. As it stands i am planning on revamping my SSH/RDP wrapping scripts to solve this issue for my team but as you might imaging that isn't ideal.