@kapa.ai does the new greenhouse harvest v3 only work in airbyte cloud? Will there be support for self hosted?

Thinking completed Based on the knowledge sources, the situation is nuanced: OAuth authentication requires Airbyte Cloud. The Greenhouse Harvest v3 connector authenticates through Airbyte's registered Greenhouse partner application. Greenhouse issues Harvest v3 partner credentials only to integration partners — customers cannot register their own OAuth applications. Because the consent flow depends on Airbyte's partner credentials, it is only available in Airbyte Cloud. [Greenhouse docs] [Migration guide] The connector is registered for OSS, but auth is the blocker. The connector's metadata does show it enabled for both Cloud and OSS:

registryOverrides:
  cloud:
    enabled: true
  oss:
    enabled: true

[metadata.yaml] However, since self-hosted users cannot access Airbyte's partner OAuth credentials, they would be unable to complete the authentication flow in practice. Regarding future self-hosted support: The knowledge sources do not mention any planned path to enable self-hosted support. The

credentials

oneOf

shape in the connector is deliberately retained so a

ClientCredentials

branch could be added in a follow-up, but there is no committed timeline or announcement for this. [Contributing guide] In summary: as of now, the Greenhouse Harvest v3 connector effectively requires Airbyte Cloud for authentication. If self-hosted support is important to you, you may want to follow the GitHub issue or the connector's repository for updates. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.