Summary
User is encountering a 405 Not Allowed response when accessing the deprecated config API endpoint /v1/source_definitions/get in Airbyte version 0.63.19. The user seeks clarification on why this endpoint is not functioning and how to enable it during Kubernetes deployment.
Question
Hey, guys! When making a request to the config API /v1/source_definitions/get, I receive a 405 Not Allowed response.
It seems this is an old, deprecated API.
My Airbyte version is 0.63.19.
Why isn’t the old version of the config API working, and how can I enable it during deployment on Kubernetes?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['config-api', '405-not-allowed', 'deprecated-endpoint', 'airbyte-version-0.63.19', 'kubernetes-deployment']
Hey Vasily - Not sure how this can help, but I would try to run the API directly against the Airbyte server (e.g. From the airbyte worker pod against the server) and see if you get the same response to confirm, if it’s the server whose answering back not allowed.
I recall those APIs are meant to be deprecated at some point, but I am not sure from which version onwards.
Maybe to understand: What are you trying to achieve in here by using that API?
Hi Nikki <@U06KAV0H59U> thank you for the answer.
The new Airbyte API (/public/v1/) has a lot of limitations, for example, there are no ability to use different namespaces for source connector create method: https://github.com/airbytehq/airbyte/issues/47140
So, that is why I’m trying to fallback to the legacy one.
Another words the legacy Config API was deprecated before implementing some necessary features in the new Airbyte API and I’m looking a way is it possible to switch it on in the Airbyte >=0.63.9