Dear Airbyte team, Thank you for the awesome product. For the sake of continuous improvement, I'd like to share some points that are IMO worth sharing as feedback • An important breaking change in

redshift-destination

(however much justified), came a bit out-of the blue which is the removal of standard

INSERT

strategy as mean of syncing. This felt a bit rushed since there is a lack of both deprecation announcement & documentation (standard INSERTs are still mentioned as an option to this day!), more importantly there is a security concern IMO, where

COPY

strategy S3 is now mandatory since it's the only option, the only AWS auth mean are through AWS Access keys (unlike

s3-destination

that allows passing an IAM Role's ARN, which is not super consistent) but they're not meant to be used that way in production. Issue #41031 • Promoting low-code connector, goes against IMO the (quick) discarding of

DeclarativeCursors

as explained here. There would be many use cases where one would need to define incremental syncing without having a field in the data source to do so like mentioned in this discussion. It leaves one with not much option to define a custom connector through config. This can easily be replaced by

AddField

transformation airbyte rocket octavia loves

We'll update the redshift docs here. Thanks for letting us know they are out of date!