Question: do we have a way eventually to integrate UI connection through Okta?

Hi everyone,
We've opened a GitHub Discussion on a proposed approach to improve Apache Iceberg interoperability in OLake Go.
Discussion: https://github.com/datazip-inc/olake/discussions/1003
The proposal introduces support for writing upsert workloads using different Iceberg delete mechanisms (Equality Deletes, Position Deletes, and Deletion Vectors) while keeping a common ingestion workflow. The objective is to make OLake Go compatible with a broader set of Iceberg catalogs and query engines.
The discussion covers:
** The interoperability problem we're trying to solve.
** The proposed changelog → main table architecture.
** Whether users should configure the delete type directly or whether OLake Go should derive it based on the selected query engine.
** The proposed UI and user experience.
We'd appreciate your thoughts on the overall approach, potential edge cases, implementation concerns, or any alternative ideas that could make this design better. Any feedback from your experience building or operating Iceberg workloads would be valuable.