Open willi-mueller opened 10 months ago
Try adding “ UTC” to your cron expression as a suffix? The API is a little more particular about the format of the expression.
Try adding “ UTC” to your cron expression as a suffix? The API is a little more particular about the format of the expression.
Thank you, @ThomasRooney, I overlooked that. I found one reference: https://github.com/airbytehq/terraform-provider-airbyte/blob/585436d1ba555088a194de89662330ea5e4c63b4/examples/pokeapi/example.tf#L87C4-L87C41
Can I contribute to clarify this in the API documentation as well as the docs of this provider?
Interestingly "UTC" works but "US/Eastern" does not, even if you can choose it from the UI and it's the value shown in a terraform plan
after changing a connection manually
Adding to what @codingtony-candid mentioned, it is indeed quite weird behaviour that the module only appears to allow UTC
as a timezone value, while you are able to change it manually to a different timezone in the UI.
Any chance to get proper support for all timezones that are available in the UI?
The issue seems to be with Airbyte API itself not just tf module. I am seeing similar problem airbyte api calls attempting to change the schedule type.
I expect the following code to create a connection with a CRON schedule. However, it creates a
disabled
connection with manual schedule:The connection in the Airbyte UI:
The terraform state:
Changing the CRON schedule to a different pattern does not change the schedule either. The Terraform state is unchanged.
Version: OSS Airbyte 0.50.34