Enable/Disable Guacamole links on a Resource Level

HTTPS/RDP should not be a valid option in the above example, and arguably ssh/telnet could be disabled because the device has to be put into a certain configuration for that to work. Sometimes we want telnet & ssh to be there, sometimes we don't depending on the Blueprint. That is why this feature is important

Joe

Hi, thank you Joe for submitting this idea. In CloudShell 8.3 we added the ability to enable/disable QualiX links per resource via the resources Inventory (all of the links, not specific ones).

To control specific links in the resource level you can use attributes and modify the links accordingly. This way you can define a link that will appear only for a resource which has specific attributes. For more information see this article in Quali's online help.

We will definitely consider adding a more straightforward way of configuring the links per resource.

That workaround is not a good solution unfortunately. We don't want to make multiple Resource Models as well as attributes for the same type of device just make the guacamole links enable or disable.

Please consider the approach to enable/disable links per resource

Thanks,

Joe

Hi @Joe Auby , I'm happy to announce that this idea will be part of our CloudShell 9.3 release. You'll be able to edit the resource available links from the current existing lists

Hi,

I'm happy to announce that with CloudShell 9.3 release you can now assign remote links per resource.

You can read more about this capability along with many other great additions here:

https://help.quali.com/Online%20Help/0.0/Portal/Content/CSP/CSP-Whats-New.htm