Deleting a source connector not working using the Airbyte API

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Kubernetes
  • Memory / Disk: unlimited
  • Deployment: Kubernetes
  • Airbyte Version: 0.35.64-alpha
  • Source name/version: all sources
  • Destination name/version: not yet tested
  • Step: deleting source connectors using API
  • Description: we are using Airbyte api to create/update/delete source connectors . We noticed that when we call the route POST /v1/sources/delete to delete a source connector, it is still there when we do a get /v1/sources/get . What makes it weird is that when we do a list /v1/sources/list the deleted source is not in the list. I am wondering if this is a bug or design choice ?
2

Hey yeah by design we set a flag to true when you delete them which is not used while fetching them as a list. Is this causing some issue?

3

it is just causing some inconsistency issues, when doing a /get the source connector is there and when getting the list the connector is not there. I am struggling to see the reason why not to completely delete the connector if there is no way to recover it ?

4

Also the way to recover it is to change a variable in the database which is easy rather than it getting deleted. You can create an issue around it incase you feel change in the method

1 Like
5

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.