Airbyte resources re-created when using Terraform

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

Summary

When using Terraform to create Airbyte resources, replacing the secret_id in Terraform code and running it is destroying the existing Airbyte resource and re-creating one due to short-lived tokens. Seeking guidance on how to avoid this issue.


Question

Hi team, Would be great if someone can re-direct me to a place where we have discussions exclusively on using Airbyte with Terraform,
• Problem Statement: Airbyte resources gets re-created when using Terraform.
• Explanation : I am using Terraform to create my GA4 sources, Google Ads sources, Facebook Sources, BigQuery Destinations. I am authenticating with Google OAuth for which we need to provide:

  1. access_token and refresh token generated from the google Oauth playground (https://developers.google.com/oauthplayground/)
  2. secret_id generated from (https://reference.airbyte.com/reference/initiateoauth)

As these are short lived tokens (not more than 24h is their expiry time), replacing the secret_id in Terraform code and running it is destroying the existing Airbyte resource and re-creating one. This is a serious trouble when there is an existing connection running. Can anyone from the community/ airbyte team guide me here. Thanks in advance


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-resources", "terraform", "google-oauth", "secret-id", "re-creating", "short-lived-tokens"]