Louis Auneau
09/13/2023, 7:44 PMairbyte_source_postgres
and airbyte_source_zendesk_support
with provider in v0.3.4. I have some attributes that are ignored and sent as null
to the API, resulting in a fail during the terraform apply. Here are my two sources:
resource "airbyte_source_zendesk_support" "******_zendesk_support" {
name = "Zendesk Support"
workspace_id = var.workspace_id
configuration = {
credentials = {
source_zendesk_support_authentication_api_token = {
email = "******"
api_token = var.zendesk_api_token
credentials = "api_token"
}
}
ignore_pagination = false
source_type = "zendesk-support"
start_date = "2023-05-01T00:00:00Z"
subdomain = "******"
}
}
resource "airbyte_source_postgres" "******_postgres" {
workspace_id = var.workspace_id
name = "CloudSQL Production"
configuration = {
host = var.database_hostname
port = 5432
database = "******"
username = var.database_username
password = var.database_password
source_type = "postgres"
replication_method = {
source_postgres_update_method_read_changes_using_write_ahead_log_cdc = {
method = "CDC"
publication = "******"
replication_slot = "******"
}
}
schemas = [******]
}
}
When running the terraform apply, the airbyte_source_zendesk_support.configuration.credentials
and airbyte_source_postgres.configuration.replication_method
are set as null.
Do you have any idea why this happens to these specific blocks. They both seem to respect the schema.
Thank you by advance!
Louis