Not sure if this is the right channel - apologies (new), but wanted to ask about the preference/use of a local private key path vs supporting serialized private key for use against snowflake? I can see the env variable for a private key path (and can see the code in datahub that then serializes this for snowflake connection), but haven’t found support for just a serialized private key?

Hey @sparse-account-96468 - I’m not sure I understand your question. Are you asking if entering the private key directly into your recipe is supported?

Hey @green-football-43791 Thanks for answering. Apologies in advance as I’m still getting used to the way datahub is setup, but I think I see what you’re getting at with the way yaml config is used and deserializing is just creating the key again. But just to outline why it’s a little odd from our use if the client (without us overriding something or extending a class if that’s possible), atm if I’ve understood the basic doco, for our use case we would: • grab an ssh key from secure storage • persist it to something reachable by the datahub client • then use that persisted path to connect through to snowflake from datahub I’m really just asking if there’s any means to connect other than a local ssh key - maybe if only in future plans?

Ah - I see @sparse-account-96468. That makes sense! At the moment, I don’t know if there are any explicit plans to take this on. However, I don’t think this would be so difficult of a contribution. If you’d be interested, I’m sure the community would appreciate you enabling this functionality!

😅 hmm… ok once I find some time (after what learning I can do) here maybe I’ll ping you first @green-football-43791 with a draft of sorts within the month or so to see if I’m on the right track

that would be great! I’d be happy to jump on a call at some point to walk you through the code as well

cool thanks @green-football-43791 I’ll start to go through this as soon as I can particularly the developing guide…..