Hi guys, i have a custom connector that was deployed and working, we made an update to its spec file and now its not showing in the UI. Any ideas how to refresh the UI after upgrading a custom connector?

did you already

docker build . -t airbyte/source-discord:dev

?

Hi Roberto, the destination is built and pushed to the repo and its actually working correctly (I updated the connection configuration via API) but its not showing at all in the UI

did you also Refresh Source Schema?

Yup i refreshed it in the 3 Connections that the destination is currently using. Are there any restrictions from the UI level on the length of the name of the property or its type that might not allow it to show?

not sure about restrictions, but I find myself often in the need to tweak data inside airbyte db using

docker exec -ti airbyte-db psql -U docker -d airbyte

the strange thing is that when I read the spec configuration of the destination definition from the airbyte db, its actually showing correctly

one issue I have with the UI is that I specify a database schema of my destination, but on the UI it keeps showing public all the time. Have not been able to solve this one unfortunately

I can't find a way around it, but since we're creating the connections programmatically through the API and its working and reflecting correctly so will just have to do without the UI for now :(

Yes Omar, I think we are far from having a full stable UI. Moreover, if you are able to use the APIs, take full advantage of it

Yes you are correct, the API has so far been excellent for us, and we even built a dashboard on Power BI to report on the statuses from the DB and we minimize the use of the UI