With ENTESB-10899 commited, a JDBC connection to the virtualization that is published is automatically created in the Syndesis connections panel. When Virtualization is unpublished this connection is deleted automatically too.

When this connection is available, it can be used further by any Integration in Syndesis. Once it is used in the Integration, the connections panel prohibits user from deleting the connection by a user. However, during the unpublish the auto-delete process also need to make sure and not delete the connection if it is in use by the Integration.

The syndeis-dv server-side already has code to prohibit this in the "delete" virtualization call, such when a user submits delete it will not delete and send a BuildStatus with "CANCEL" state with message saying it is currently being used in the Integration x. However, UI need to prohibit by disabling link for "unpublish".

To check if the Vitualization is used by a integration, UI can use the same backend method to check for Virtualization status call `/metadata/publish/virtualization-name` the returned BuildStatus object now has a new field called `usedBy`, which will have the integration name that this is being used in, if this is null or empty it is not currently in use by an Integration.

One thing I noticed is when the connection is deleted when it is in use, the whole system gets hosed.