New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform provider bug - unexpected response from API. Got an unexpected response code 400 - Primary key for stream: Account is already pre-defined #89
Comments
Zendesk ticket #5512 has been linked to this issue. |
Can you please try upgrading to Airbyte version https://github.com/airbytehq/airbyte-platform/releases/tag/v0.57.3 and try again? |
Hey @JonsSpaghetti , looks like it works. Thank you very much for the fix, Best regards Thibaut |
when i update my
|
Hello All I am too getting same issue: │ {"type":"https://reference.airbyte.com/reference/errors","title":"bad-request","status":400,"detail":"The Difficult to progress, please advise. Resolution (Dirty): |
In another github issue, cannot find related link, i found the temporary solution above which works for me, add an empty primaryKey attribute, it doesnt delete primarykey |
Hello, In fact the bug is not solved indeed :-( We just tried our prod migration this migration from Octavia to TF, but are completely blocked by this bug. The workarounds can't work:
This is a huge blocker for our Terraform migration, we hope it can get fix soon, Thanks much in advance, |
In fact bug is fixed on the airbyte-server, not airbyte-server-api So switching to terraform provider to this url:
fixed it :-) 🎉 |
Hello All I'm still geting this error with the airbyte latest version (v0.58.1) and terraform version 0.4.2. Thanks much in advance, |
Dear Airbyte team
unexpected response from API. Got an unexpected response code 40
I created a connection in TF like this:
But when I want to update it. I got:
As you can see, I never provided primaryKey.
Airbyte automatically has added it when creating the source.
I tried to remove it manually in the TF state, but even that don't work, because it re-fetch all the source config before re-applying.
And therefore the PATCH doesn't work,
I guess there is a bug in the Terraform provider.
This prevents us from migrating to Terraform which has impact on us. We want to migrate ASAP to TF otherwise we'll accumulate legacy code.
Thanks
Best regards
The text was updated successfully, but these errors were encountered: