feat: source-monday move to the DeclarativeOAuthFlow
#48054
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
area/connectors
…ove-to-declarative-oauth-flow
octavia-squidington-iii
added
the
area/documentation
bazarnov
deleted the
baz/source/monday/move-to-declarative-oauth-flow
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Following up these changes:
DeclarativeOAuthFlowinput to protocol airbyte-protocol#96We need to update the
specwith theoauth_connector_input_specificationto switch to theDeclarativeOAuthFlowsupported by the platform.How
specwithoauth_connector_input_specificationand declared how theOAuthFlowshould be constructedUser Impact
No impact is expected. This is not a breaking change.
Can this PR be safely reverted and rolled back?