Move family properties to the resource level

Serious shortcoming having a family level attribute like this!

Hi! few questions regarding the use cases you described:

1. If there are some resources used for connectivity and some as DUTs maybe it makes more sense to have to separate Shell standards? or maybe a resource can be sometimes used for connectivity and sometimes as a DUT?

2. What is the use case for using deployed apps outside of the Sandobx they are deployed in (and therefore having them shared and searchable)? Just reminding that the apps will get deleted on Teardown.

Besides pushing these flags down to the resource level, we'd also like to see an additional flag for "Shareable". The default True would yield the current system behavior, while setting it to False would let users reserve ports on the resource, but not the entire resource. We would use this for some devices like external-facing switches where users need ports but should never be able to reserve the entire device.

Also, the flag "Locked by default" isn't as clear as if it was "Shared by default" (preferred, but reverses the meaning of the flag) or "Unshared by default". Using the word "shared" aligns the name with the resource menu item in the Portal.

I'm happy to update that this idea is planned for CloudShell 8.2. We will have the ability to define resource visibility ("admin only" or "everyone") on the resource level and not just the family level.

We are considering exposing other family properties (such as remote connections etc.) on the resource level in the future, according to priority and use cases.

Hi, just updating about this idea - in CloudShell 8.3 we added the ability to enable/disable remote connections on the resource level. In CloudShell 9.2 we will add the ability to define the default share level (shared/unshared) on the resource level.

Hi,

Here's the 9.1 help article: https://help.quali.com/Online%20Help/9.1/CloudShell/Content/CSP/INVN/Edit-Rsrc-in-Invnt.htm