use new scheduling schema for new connection tracking #16690
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Support cron strings for new connection tracking.
How
Consume the new scheduling format if it's available, otherwise keep using the old format.
This duplicates the logic from #16590. Ideally this would be pulled into a common implementation, which will be revisited in https://github.com/airbytehq/airbyte-internal-issues/issues/502, but this will unblock adding cron scheduling to the frontend so I'd like to go ahead in the meantime.