@kapa.ai I'm not able to give s3_path_format ${STREAM_NAME}/year=${YEAR}/month=${MONTH}/day=${DAY}/hour=${HOUR}/ using terraform while creating airbtye destination. Any idea on this?

Based on the information provided in the knowledge sources, I can offer some insight into the S3 path format for Airbyte destinations. However, I don't have specific information about using Terraform to create an Airbyte destination with this particular path format. The S3 path format you're trying to use (

${STREAM_NAME}/year=${YEAR}/month=${MONTH}/day=${DAY}/hour=${HOUR}/

) is similar to the customizable format options available in Airbyte's S3 destination connector. According to the documentation, Airbyte supports various variables for customizing the S3 path format, including

${STREAM_NAME}

,

${YEAR}

,

${MONTH}

,

${DAY}

, and

${HOUR}

[S3 Destination Connector Setup](https://docs.airbyte.com/integrations/destinations/s3#step-2-set-up-the-s3-destination-connector-in-airbyte). The default S3 path format in Airbyte is

${NAMESPACE}/${STREAM_NAME}/${YEAR}_${MONTH}_${DAY}_${EPOCH}_

, but it can be customized using these variables. However, the documentation doesn't mention any specific limitations or issues when setting this up via Terraform. It's possible that the issue you're experiencing might be related to how Terraform is interpreting the path format string, rather than an Airbyte limitation. To troubleshoot this, you could try: 1. Escaping special characters in your Terraform configuration if needed. 2. Verifying that your Terraform version supports this kind of string interpolation for the Airbyte resource. 3. Checking if there are any specific requirements or limitations in the Terraform provider you're using for Airbyte. If the issue persists, you might want to consult the Terraform documentation or community forums for Airbyte-specific Terraform configurations.