Ian OLeary
03/10/2025, 8:44 PMEdgar Ramírez (Arch.dev)
03/10/2025, 8:54 PMprivate_key_path
and private_key_passphrase
, you'd need to update your profiles.yml
.
If you're already using password auth, you could similarly reference settings in profiles.yml
, e.g. private_key_path: "{{ env_var('DBT_SNOWFLAKE_PRIVATE_KEY_PATH') }}"
after https://github.com/meltano/hub/pull/1962 merges and you do meltano lock --update --all
.Ian OLeary
03/10/2025, 9:07 PMEdgar Ramírez (Arch.dev)
03/11/2025, 4:17 AMIan OLeary
03/11/2025, 4:23 PMprivate_key: "{{ env_var('TARGET_SNOWFLAKE_PRIVATE_KEY') }}"
meltano.yml:
settings:
- name: private_key
instead of having name: password
set
Then ran meltano lock --update --all
Then set that TARGET_SNOWFLAKE_PRIVATE_KEY to the private key and created a new user in snowflake and did some role adjustments and granting. I had been using the ACCOUNTADMIN role with user/pass auth, now using KeyPair auth with a much more restricted role.Ian OLeary
03/11/2025, 4:27 PMEdgar Ramírez (Arch.dev)
03/11/2025, 4:28 PMIan OLeary
03/14/2025, 1:27 PM36 -----BEGIN PRIVATE KEY-----
37 MIIE...
38 ...
with line breaks. I'm setting it as a secret in Azure Key Vault. I've tried it with just using the key string with no line breaks and it doesn't seem to be working properly. Should I be formatting it in any specific way to account for the line breaks or would you expect the string on one line to work correctly? I'm encountering another issue (a dagster one) which is causing me other failures simultaneously so this might actually be fine (and that might be what is causing my revision start failure), but wanted to know if you had any ideas.Edgar Ramírez (Arch.dev)
03/14/2025, 3:02 PMIan OLeary
03/14/2025, 3:11 PMIan OLeary
03/18/2025, 5:56 PMIan OLeary
03/18/2025, 5:57 PMaz keyvault secret set --vault-name "<your-unique-keyvault-name>" --name "MultilineSecret" --file "secretfile.txt"
commandEdgar Ramírez (Arch.dev)
03/18/2025, 10:43 PM