Guidance on Terraform Secret ID Management for Airbyte Sources

Summary

User seeks clarification on whether a new secretId must be generated each time Terraform is run for creating Airbyte sources, and the implications of doing so on existing sources.


Question

Hi team,
Sub : I am looking for some guidance on if I need to get secretId generated every time I run my terraform for creating airbyte sources.

I am using Terraform to create my Airbyte sources (GA4 source, Google Ads Source), big query destinations and connections between both. I am wondering if I need to provide the Access Token, Refresh Token, secret Id every time/everyday during the source creation. I am generating the access token and refresh token required from the https://developers.google.com/oauthplayground while the secretId is generated from the Initiate OAuth API from this link : https://reference.airbyte.com/reference/initiateoauth.
The problem of generating the secretID every time is that it destroys my existing sources/rename them which I am not looking forward to. Can you please quickly help me in this regard.



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

['terraform', 'airbyte-sources', 'secret-id', 'access-token', 'refresh-token']