Error: 260002: password is empty #2133
Comments
|
I tried to add back the authentication method that seemed to have been removed, hoping it would solve the issue: Unfortunately, it didn't work and I had the following error: |
|
Issue still present in 0.75.0. I see that MergeConfig and EnvConfig do not take profile config.PrivateKey into account for example: terraform-provider-snowflake/pkg/sdk/config.go Lines 50 to 73 in d33a41c terraform-provider-snowflake/pkg/sdk/config.go Lines 90 to 116 in d33a41c |
|
Can anyone fix this? I could try to contribute to this, but I will need some guidance |
|
Hello, sorry for the issue with provider configuration. We are working on a fix and will have this out ASAP. Thank you for your patience. |
|
Hi @sfc-gh-swinkler thanks for the fix. I am still seeing this issue in v0.75.0. Do you need to recreate the tag or release a new version? |
|
I seem to be getting this with and provider "snowflake" {
role = "ORGADMIN"
alias = "orgadmin"
account = "..."
}There is also a warning about the deprecation of the I can see in https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#v0730--v0740 that |
I did that, but: with: provider "snowflake" {
role = "ORGADMIN"
alias = "orgadmin"
private_key = file("~/.ssh/my.p8")
account = "..."
}
There is a in the above, but I wouldn't think that should stop it from connecting? |
|
In |
|
Even: provider "snowflake" {
role = "ORGADMIN"
alias = "orgadmin"
private_key = file("~/.ssh/my.p8")
private_key_passphrase = var.private_key_passphrase
account = "..."
}with the passphrase entered directly to make sure it's not an env issue, yields the same: |
|
Hey @joscha 👋 |
Yes, I saw, but adding that consistently yields: ^ this is with: provider "snowflake" {
role = "ORGADMIN"
alias = "orgadmin"
authenticator = "JWT"
private_key = file("~/.ssh/my.p8")
private_key_passphrase = var.private_key_passphrase
account = "..."
} |
|
Did you generate it with those instructions: https://quickstarts.snowflake.com/guide/terraforming_snowflake/index.html#2? It may be invalid because you used other options to generate it. |
|
This error is on the Snowflake side. Could you check if your key format is valid? Go to the official Snowflake documentation and search by error code (390144 in this case). |
Thank you for that. I did not create it after that exactly, I used: https://docs.snowflake.com/en/user-guide/key-pair-auth. I attached the private key (the same way as described) to an existing user. Will give creating a new user a try. |
Ah, this is good, thank you. After querying the error with the reference code on the snowflake side, I am now looking at |
Just for future reference. If you try to generate an encrypted private key with the options from the Quickstart above, you'll get: So you can only generate non-encrypted key that way - for encrypted keys and some more background, see here. |
|
I got it to work eventually. There seems to be some funkiness with the regeneration of I tried to reproduce it but wasn't able to in a consistent manner. It possibly seems to be related to newlines and/or leading or trailing whitespace in the key input key, but sometimes the fingerprint is different / the last value. |
|
Thank you, @joscha, for your input. @sfc-gh-jmichalak is currently working on improving the provider configuration. We will test those cases so they'll be handled better or documented clearly in the registry. |
Provider Version
0.74.0
Terraform Version
Terraform v1.6.1
on windows_amd64
Describe the bug
Snowflake provider error after update to 0.74.0 from 0.73.0. Using private key with no password, seems that the provider requires a password and is failing now.
│ Error: 260002: password is empty
│
│ with provider["registry.terraform.io/snowflake-labs/snowflake"],
│ on provider.tf line 29, in provider "snowflake":
│ 29: provider "snowflake" {
│
Expected behavior
No error
The text was updated successfully, but these errors were encountered: