Troubleshooting 415 status error when using API to update source configuration


When trying to update the configuration of a source (Postgres) using the Airbyte API, encountering a 415 status error with no helpful logs. Seeking tips for debugging or alternative strategies. Mentioned success with Terraform provider.


~We have the OSS version installed and have secrets rollover on one of our sources, postgres. i’m trying to use the api PATCH localhost:8006/v1/sources/TOKEN with JSON {configuration: { password: $password }}, but keep getting status 415 (and no meaningful logs in airbyte-api-server i can see. any tips on debugging? or if there’s a better strategy here~

found that this works fine with the terraform provider, not quite as neat (since i’m responding to a secrets change event), but not the worst. leaving for posterity

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

["api", "patch", "source-configuration", "415-status-error", "debugging", "terraform-provider", "secrets-rollover"]