roeap commented on issue #4240: URL: https://github.com/apache/arrow-rs/issues/4240#issuecomment-1552825834
I played around a little bit with how robust config handling might look like. Guessing the users intent from the passed configuration remains challenging, but I did come up with a [rough draft](https://github.com/delta-io/delta-rs/pull/1378) of something that "might" eventually work. The main idea is to provide a priority of credentials and the required configuration keys to construct a specific credential. Then so far doing several passes through the priority list. - If the passed options contain a full credential we use that one. - If the passed options contain some config for a credential, and we can augment the rest from the environment, we choose that. - If we can parse a full credential from then env, we choose it. - Else we fall back to config free credentials (i.e. metadata endpoints) I was also thinking about having some notions of "tells" - e.g. for azure if a client secret is provided, we assume the user intents to use client secret auth, and error if we cannot find client and authority id ... As mentioned, this is so far just a rough draft, but if you think this might lead somewhere I'd be happy to move the PR over here... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
