Hi all, I would like to open up for discussion a new FLIP-529 [1].
Motivation: Currently, Flink SQL handles external connectivity by defining endpoints and credentials in table configuration. This approach prevents reusability of these connections and makes table definition less secure by exposing sensitive information. We propose the introduction of a new "connection" resource in Flink. This will be a pluggable resource configured with a remote endpoint and associated access key. Once defined, connections can be reused across table definitions, and eventually for model definition (as discussed in FLIP-437) for inference, enabling seamless and secure integration with external systems. The connection resource will provide a new, optional way to manage external connectivity in Flink. Existing methods for table definitions will remain unchanged. [1] https://cwiki.apache.org/confluence/x/cYroF Best Regards, Mayank Juneja
