Hi @Artem Astapenko I submitted a PR and a question for you to wrap-up the work on the destination sync modes from last week: https://github.com/airbytehq/airbyte/pull/2668#issuecomment-810333765

left the comment. They way it is currently implemented - it is not possible to work with it on FE

The

AirbyteStream

and

AirbyteCatalog

are produced by some function call looking like:

discoverSchema(sourceId)

At this point, I don’t have any informations about the destination capabilities… I don’t think we would want to do something like:

discoverSchema(sourceId, destinationId)

Maybe we should add an additional API call so you can do something like:

configureCatalog(discoverSchema(sourceId), getDestinationSpecification(destinationId))

Is that what you would expect then? https://github.com/airbytehq/airbyte/pull/2668#issuecomment-810425465

ok then. If its not stream specific - lets have it from destinationSpecification entity

Alright, the PR is merged so it should be ready for you for this ticket! https://github.com/airbytehq/airbyte/issues/2625 Thanks

Awesome. Thank you!