-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform provider fails with "key is not in PEM format" but snowsql works perfectly with same key #2646
Comments
$ openssl genrsa -out snowflake_carmas 4096 |
2024-03-23T00:22:33.524-0700 [ERROR] provider.terraform-provider-snowflake_v0.87.3-pre: Response contains error diagnostic: @caller=github.com/hashicorp/terraform-plugin-go@v0.20.0/tfprotov6/internal/diag/diagnostics.go:62 @module=sdk.proto diagnostic_detail="" tf_req_id=1cf7bab5-f93c-739c-9b0a-4b73b7769586 tf_rpc=ConfigureProvider diagnostic_severity=ERROR diagnostic_summary="could not retrieve private key: could not parse private key, key is not in PEM format" tf_proto_version=6.4 tf_provider_addr=registry.terraform.io/Snowflake-Labs/snowflake timestamp=2024-03-23T00:22:33.524-0700 |
Hey @carmas. Thanks for reaching out to us.
|
@sfc-gh-asawicki thank you! |
Terraform CLI and Provider Versions
Terraform v1.7.5
on darwin_arm64
Terraform Configuration
Expected Behavior
terraform plan
........
Actual Behavior
terraform plan
....
Error: could not retrieve private key: could not parse private key, key is not in PEM format
│
│ with provider["registry.terraform.io/snowflake-labs/snowflake"],
│ on provider.tf line 1, in provider "snowflake":
│ 1: provider "snowflake" {
Steps to Reproduce
https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs#example-provider-configuration
How much impact is this issue causing?
High
Logs
No response
Additional Information
https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs#example-provider-configuration
snowsql CLI works with the encrypted keys
The text was updated successfully, but these errors were encountered: