Storing Airbyte Connection Details as Code in EKS

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

User seeks advice on how to store Airbyte connection details as code for observability and version control while deploying Airbyte on EKS using helm charts.


Question

Hi All, we are deploying Airbyte’s latest version in EKS using helm charts. I would like to store each connection as code for observability and version control. Does anyone have any advice on storing connection details as code while using helm charts for Airbyte’s deployment?


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

['airbyte', 'eks', 'helm-charts', 'connection-as-code', 'observability', 'version-control']
2

I don’t think the Airbyte Helm chart supports this. You can achieve this with their Terraform provider. https://registry.terraform.io/providers/airbytehq/airbyte/latest/docs