Set image/icon per resource (optional)

Hi,

Can you please provide more details about this use case, are you using a single resource model to integrate different devices?

Here is my use case:

Sandbox is modified during the setup phase, by dynamically adding resources discovered in the remote lab. Those remote resources can be routers, switches, servers, VMs, etc.

From the perspective of sandbox automation, no differences between those resources. One resource model will be sufficient, except that we do not want all of them to be represented with the same icon.

Hi Dan,

About adding label (and color) to the resource icon

Short answer: Maybe. Once I see it implemented, I will be able to provide a better answer.

We do use the new color labeling feature, but our users are still very interested in having multiple unique resource icons for resources that have similar functionality and therefore share the same shell. Icons are still the primary way in user experience to provide clarity in functionality of the resource block, and when the icons are the same, users assume the resources are the same.

this is possible with deployed "app" resources to define unique images, but not for concrete resources. It could be useful in some cases, but also new model with dedicated image can be created in that case. If it is 1G style resource, then family level attribute inheritance can be used. If 2G shells, the attributes would have to be duplicated across the yaml files.

Reply to Gilat's message (on Sep/30)

Hi Gilat,

Yes, we tried. It is much better than before, it adds more clarity to the busy canvas.

My users still ask for resource-specific images and background images. I hope that in the future we will have those.

Thanks,

George