-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose cron scheduling in the Connections APIs #15253
Merged
Merged
Changes from 6 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
e5ce4c0
Expose cron scheduling in the Connections APIs
mfsiega-airbyte 72d8ca1
Update airbyte-api/src/main/openapi/config.yaml
mfsiega-airbyte 8b38982
Update airbyte-server/src/test/java/io/airbyte/server/helpers/Connect…
mfsiega-airbyte fdea0e4
Merge branch 'master' into msiega/cronstrings-api
mfsiega-airbyte 4218972
update octavia-cli tests for new schedule schema, and fix update API …
mfsiega-airbyte bca287b
Merge branch 'master' into msiega/cronstrings-api
mfsiega-airbyte 1266d36
Merge branch 'master' into msiega/cronstrings-api
mfsiega-airbyte f351d9f
check for null schedule data before updating
mfsiega-airbyte fe8ed8e
handle new schedule related fields in generate / apply / import
alafanechere 68ed28a
update octavia-cli changelog
alafanechere 59455e2
ensure that legacy manual schedule flag is consistent with schedule_type
mfsiega-airbyte 3274c0c
update octavia cli test coverage for new schedule schema
mfsiega-airbyte 9d0833a
fix failing octavia cli integration tests
mfsiega-airbyte 3a804e8
fix file diff check
mfsiega-airbyte 09b59e3
Merge branch 'master' into msiega/cronstrings-api
mfsiega-airbyte 4f8c78a
Update octavia-cli/unit_tests/test_apply/test_resources.py
mfsiega-airbyte File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it not encapsulated in one object?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion the deeper nesting would make it a bit more unwieldy without too much benefit - encapsulating it under an object doesn't really reduce the cognitive load since every user has to figure out what to do with schedule data anyway whether it's top-level or nested.
I did consider the approach you propose, and I'm not really opposed to it. It comes with the wrinkle that during the migration we have this schedule object that contains both the old and new schemas. (Or - we have some transition period where we have the new schema with some new name, remove the old schema, and then migrate again the new schema to the existing
Schedule
name.) All in all this felt simpler; but open to feedback here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No strong opinion on my end. However everything related to migration complexity is a non-issue to me since we are v0. I prefer to have something clean that we want than to make design tradoffs based on backward comp or migrations.