Add Labels to Sandbox Resources via API

Natti, It is possible to label resources in a sandbox via the UI. Can you explain why you need to label things via the API - what is the use case? How big of a problem is this? How many customers will this impact? We intentionally didn’t add an API for a sandbox because it would discourage proper resource modeling.

I can think of a couple of use cases. Simple configuration on a item - if it's configured to the current gold standard, it gets on label, if it is configured to a different file, then a different label - depending on the orchestration scripts or the command on the device itself.
In addition, if an item failed a health check during setup - we could flag that - specifically here is it's shard parent with reserved sub units. Think switch, where the parent unit is shared, but one of the ports in use failed a specific setup or healthcheck - we do have the resource status flag, but that only shows on the canvas for the parent's status, not any of the children. And if I flag it in error for the parent, then that status is set for the device in all instances, vs a sandbox label which is for just one instance.

Hi Terry, Kimo,

Thanks for the feedback.

I don't see the negatives to having an API for this. For large blueprints it can be tedious to label twenty of a particular app in the UI. Assuming they all have some kind of attribute tag it would be easy to do this with a script.

Another use case that was recently discussed with a customer is programmatically creating blueprints via packaging api, and wanting to add the labels as well.

Currently the labels also don't appear to be exported or managed with the XML, which is a different problem. We could either manage the labels through XML and allow packaging api to programaticaly manage them, or add the functionality through a different Api (Automation API / Quali API / Sandbox API)

Thanks,

Natti