In Airbyte, the normalization process can be defined during the connection setup. When setting up your connection, you can enable or disable basic normalization in the "Normalization and Transformation" section. This is optional and can be toggled on or off based on your requirements [source](
https://docs.airbyte.com/understanding-airbyte/basic-normalization). However, please note that the normalization rules are not configurable. They are designed to pick a reasonable set of defaults to hit the 80/20 rule of data normalization. If the basic normalization feature does not meet your needs, you can parse the full json blob in the destination as per your use case. For more advanced normalization functionality, you might want to consider using dbt [source](
https://docs.airbyte.com/understanding-airbyte/basic-normalization#Rules). If you want to extend the basic normalization, you can build a custom SQL view with your own naming conventions, export, edit and run custom dbt normalization yourself, or configure the use of a custom dbt project within Airbyte [source](
https://docs.airbyte.com/understanding-airbyte/basic-normalization#Extending-Basic-Normalization). As for moving your Airbyte config to the Terraform provider, the tutorial you're referring to leverages Octavia CLI, which is an alpha unofficial CLI that won't be maintained. Since the publication of this tutorial, Airbyte has released an official Terraform Provider, which is advised to use instead of the CLI [source](
https://airbyte.com/tutorials/version-control-airbyte-configurations). Unfortunately, the extracts provided do not contain specific instructions on how to define the normalization process using the Terraform provider. For more detailed guidance, you might want to refer to the official documentation of the Terraform provider.