Fivetran adapter
The Fivetran source adapter calls the Fivetran REST API to list connectors and their tables. It reads metadata only. Rocky never moves data through this adapter.
Fields
Section titled “Fields”| Field | Type | Required | Description |
|---|---|---|---|
kind |
string | Yes | Must be "discovery". Fivetran lists tables and moves no data, so Rocky refuses the block without it (V032). |
destination_id |
string | Yes | Fivetran destination ID. |
api_key |
string | Yes | Fivetran API key (Basic Auth). |
api_secret |
string | Yes | Fivetran API secret (Basic Auth). |
[adapter.fivetran]type = "fivetran"kind = "discovery"destination_id = "${FIVETRAN_DESTINATION_ID}"api_key = "${FIVETRAN_API_KEY}"api_secret = "${FIVETRAN_API_SECRET}"A pipeline names this adapter in source.discovery, not in source.adapter. The warehouse that Fivetran writes to reads the rows (V033 refuses a discovery-only source.adapter):
[pipeline.bronze.source]adapter = "prod" # the warehouse Fivetran lands tables in
[pipeline.bronze.source.discovery]adapter = "fivetran"Authentication
Section titled “Authentication”HTTP Basic Auth using api_key and api_secret. Source-adapter authentication is separate from warehouse authentication — see Authentication.
See also
Section titled “See also”[adapter.NAME]— fields shared by every adapter type, including the retry policy.- Fivetran state cache — sharing the resolved state envelope across processes.
rocky discover --emit-fivetran-state-to— write the state envelope to a file.