Bug: Can link a connector that has been deleted elsewhere

[jpople]

Bug Description

Linking a connector from the orphaned connection modal after it's been deleted from the "connections management" page results in a "successful" link and sets the system's connection on the backend, but doesn't show the connection configuration form for it.

You can see that the connector is set in the backend by:

• inspecting it using a console log
• noting that the "Link integration" button no longer shows up in the integrations tab even when another connector should be eligible
• attempting to add a new connector from the connections management page with the same key as the "deleted" connector-- it will throw an error and say that a connector with that key already exists

Steps to Reproduce

1. Create a system
2. From the connection manager page, create a connector
3. Navigate to your system's integrations tab
4. In another tab/window, go to the connection manager page and delete the connection
5. Return to the system integration tab and add the connector you just deleted

Expected behavior

Not sure. Either throw an error when trying to link a connector that doesn't exist anymore, or set the connector anyway and bring up the connector configuration form as expected.

[Roger-Ethyca]

When deleting a service that has an integration, that integration shows up as a dataset when adding a DB integration like big query.

[rsilvery]

@jpople , @Roger-Ethyca can we confirm if this is still an issue?