@kapa.ai What is the correct way in terraform to disable telemetry in our self hosted airbyte instance in aks?

To disable telemetry in a self-hosted Airbyte instance deployed in AKS using Terraform, you need to set the

TRACKING_STRATEGY

environment variable to

logging

. However, I don't have specific information about the exact Terraform configuration for this in the provided knowledge sources. Based on the general information about disabling telemetry, you would typically need to modify the

.env

file or set an environment variable in your deployment configuration. For a Kubernetes deployment like AKS, this would likely be done through your Helm chart values or Kubernetes manifests. The relevant information comes from the Airbyte documentation on telemetry: [Documentation > Operator-guides > Telemetry](https://docs.airbyte.com/operator-guides/telemetry)

To disable telemetry for your instance, modify the `.env` file and define the following environment variable:  TRACKING_STRATEGY=logging

Unfortunately, I don't have specific Terraform code examples for implementing this in an AKS environment. If you're using the official Airbyte Helm chart with Terraform, you might need to set this value in your Helm chart configuration within your Terraform code. For the most up-to-date and accurate information on implementing this with Terraform in AKS, I recommend checking the official Airbyte documentation or reaching out to Airbyte support for specific guidance.

@kapa.ai can you show me a example terraform file to deploy airbyte

A message from kapa.ai

I'm sorry, but the provided knowledge sources do not contain a specific example of a Terraform file for deploying Airbyte. However, they do mention that Terraform can be used to manage the infrastructure for Airbyte, and they provide some general guidance on the structure of the Terraform setup for Airbyte. Here's a general structure based on the information from the [discussion on GitHub](https://github.com/airbytehq/airbyte/discussions/34701):

hcl # <http://provider.tf|provider.tf> provider "airbyte" {   # Define the Airbyte provider, credentials, and the server URL here }  # <http://main.tf|main.tf> resource "airbyte_resource" "example" {   # Contains the main configuration for creating Airbyte resources }  # <http://variables.tf|variables.tf> variable "example_variable" {   # Holds various variables, including credentials }

In the

<http://provider.tf|provider.tf>

file, you define the Airbyte provider, credentials, and the server URL. The

<http://main.tf|main.tf>

file contains the main configuration for creating Airbyte resources. The

<http://variables.tf|variables.tf>

file holds various variables, including credentials. Please note that this is a very basic and general example. The actual Terraform configuration will depend on your specific use case and requirements. For more detailed information on how to use Terraform with Airbyte, I recommend checking out the [Airbyte Terraform Provider Page](https://registry.terraform.io/providers/airbytehq/airbyte/latest) and the [Airbyte Terraform Setup Guide](https://reference.airbyte.com/reference/using-the-terraform-provider).