Terraform provider request to create faker source returning 404 Not Found

Summary

The user is trying to create a faker source via the Terraform provider to an Airbyte instance behind a VPN, but is receiving a 404 Not Found error. The request is going to /api/v1/sources which seems incomplete.


Question

Hi all,

I’m trying to create a simple faker source via the terraform provider to an oss kubernetes instance of airbyte that has no authentication set up (it’s behind a vpn)

Looking at the debug log I see this:

**Request POST /api/v1/sources HTTP/1.1
**Response HTTP/2.0 404 Not Found

Full log:

│ Error: unexpected response from API. Got an unexpected response code 404
│ 
│   with module.fake_thing.airbyte_source_faker.fake_thing_created_by_terraform_1,
│   on ../../sources/faker/fake/main.tf line 11, in resource "airbyte_source_faker" "fake_thing_created_by_terraform_1":
│   11: resource "airbyte_source_faker" "fake_thing_created_by_terraform_1" {
│ 
│ **Request**:
│ POST /api/v1/sources HTTP/1.1
│ Host: the.airbyte.url
│ Accept: application/json
│ Authorization: Basic Og==
│ Content-Type: application/json
│ User-Agent: speakeasy-sdk/go 0.3.5 2.210.3 1.0.0 airbyte
│ 
│ {"configuration":{"always_updated":false,"count":9,"parallelism":8,"records_per_slice":1,"seed":5,"sourceType":"faker"},"definitionId":"33c76bbd-55f5-466b-8ade-0498ec40fd8a","name":"fake_thing_from_terraform","workspaceId":"the-workspace-id"}
│ **Response**:
│ HTTP/2.0 404 Not Found
│ Content-Length: 17
│ Alt-Svc: h3=":443"; ma=86400
│ Cf-Cache-Status: DYNAMIC
│ Cf-Ray: 83fc5f0b4d93772c-LHR
│ Content-Type: application/json
│ Date: Wed, 03 Jan 2024 15:45:52 GMT
│ Server: cloudflare
│ Set-Cookie: _cfuvid=the.cookie; path=/; domain=.the.domain; HttpOnly; Secure; SameSite=None
│ Strict-Transport-Security: max-age=15724800; includeSubDomains
│ X-Content-Type-Options: nosniff
│ 
│ Object not found.
╵```
Querying the api with postman works fine. So I can get a json output for a `POST` to `{{airbyte_url}}/api/v1/connections/list` successfully.

My only observation is that the provider request goes to `/api/v1/sources` which feels incomplete

Any ideas anyone?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1704297372378589) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["terraform", "faker-source", "404-not-found", "api-request", "airbyte-instance", "vpn"]
</sub>