You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following #17909, which introduced the capability for the platform to update connector configuration during syncs, we also want to update configuration during the other commands (e.g. check, discover)
We can use the UpdateConnectorConfigHelper introduced in the previous PR to perform the updating, which already handles things like masking secrets.
This will involve initializing the AirbyteApiClient in airbyte-server, as well as updating inputs to the jobs as required to have the right information for calling the endpoints (e.g. source or destination id)
The text was updated successfully, but these errors were encountered:
In order to prevent weird side effects from updating configuration from control message while editing the connector config, we'll need to also update the API calls to perform check and save at the same time.
For context, currently the connector creation and update pages perform two calls:
check_connection
update / create
Because check_connection can now also update the config, this might introduce unexpected results. We should combine the calls into one so we perform the update as expected.
Following #17909, which introduced the capability for the platform to update connector configuration during syncs, we also want to update configuration during the other commands (e.g. check, discover)
We can use the UpdateConnectorConfigHelper introduced in the previous PR to perform the updating, which already handles things like masking secrets.
This will involve initializing the AirbyteApiClient in airbyte-server, as well as updating inputs to the jobs as required to have the right information for calling the endpoints (e.g. source or destination id)
The text was updated successfully, but these errors were encountered: