-
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
fix: inject oauth params when generating sync input #22635
Conversation
Airbyte Code Coverage
|
(Left a comment along these lines in Slack, but for visibility) What testing have we done to make sure this is safe? |
@mfsiega-airbyte I've added tests here to verify that we're injecting oauth params, but currently deploying this to dev-2 to check it out in cloud. Will merge once I confirm there. |
Did we not do this for the original PR? |
I did not test in cloud with an OAuth connector for the original PR. |
@@ -225,6 +239,8 @@ void testGetResetSyncWorkflowInput() throws IOException, ApiException { | |||
.withDestinationConfiguration(DESTINATION_CONFIGURATION) | |||
.withState(STATE); | |||
|
|||
verify(oAuthConfigSupplier).injectDestinationOAuthParameters(DESTINATION_DEFINITION_ID, WORKSPACE_ID, DESTINATION_CONFIGURATION); |
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.
nit: could this test ensure that a secret was decrypted?
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.
Updated the test to actually check that we're using the config returned by the injection method in 716fe1c. Internals of how the injection works left up to unit tests for the OAuthConfigSupplier.
* fix: inject oauth params when generating sync inpt * make it final * rm oauth injection from job creator factory * keep it * keep it 2 * test that we're actually using the oauth values * fmt
What
When moving the configuration fetching to happen at the attempt level in #21629 we stopped injecting OAuth parameters into the configuration. This led to errors due to not having the right params during syncs.
How