-
Notifications
You must be signed in to change notification settings - Fork 426
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
provider requiring password
var when private_key
is provided
#2169
Comments
This is preventing our production deployments as well, we are also using a Private Key instead of a password. Any update on this? |
@mvanzanten-infostrux ive been in contact with snowflake support directly, the terraform developers have been made aware of it, and ive been told they are working on it. Hopefully. |
@kalinon Thanks for letting me know! |
Is there any update on this? This bug is causing us to have to use version 0.72.0 as it doesn't seem to have these auth issues. But 0.72.0 doesn't have all the resources that we would ideally like to use. |
Bummer to see this! We are just starting to roll out snowflake got blocked straight off using their their guide with terraform. Thanks @putnam120 for pointing out a working version. @ |
this is also blocking an resource deployments/upgrades for us - having to go into every module and pin the provider is quite annoying... |
This is issue is a nightmare and when you look at the release notes it seems to be fixed in v0.75.0 and then in v0.76.0 but it is not fixed at all. Here are the tests I've made so far Terraform Version: Provider Version
|
I've been trying to upgrade the provider since 0.74.0 and I have also been bitten by the same issues described by @remi-f-artelia. It would be nice if Snowflake focused on stabilizing authentication/configuration portion of the provider for the next release instead of adding more changes. Maybe that way they could release a fix in a shorter timespan? If help is needed for debugging these changes I am more than willing to help. cc: @sfc-gh-swinkler |
@remi-f-artelia, @elventear I think I know where the problem lies: apparently, change #2126 broke the way we are setting the authentication type on the underlying gosnowflake driver, which defaults to user+password one, and that's were the Please temporarily set The configuration would look like this:
|
Hi @sfc-gh-asawicki , thank you for your reply Provider version:
|
Okay, thanks for the quick response @remi-f-artelia. This confirms my suspicions. There was a fix between v0.75.0 and v0.76.0 - #2170 which solved the panic which you attached above for v0.75.0. Please for now use the Ideally, we would release |
thank you very much this temp fix worked |
Since this fix is working, shouldn't it be mentioned in the documentation? It is quite a long time that this bug exists and it prevents people from using private keys when using the latest version. |
Hey @axthosarouris. Will be added in #2345. |
#2345) Adds setting `authenticator` to `JWT` explicitly to the docs and migration guide. Check: #2169 (comment) and #2169 (comment).
I was working on this for some practice and thought I would post what is working.
Provider version:
|
I will close this issue because the documentation was updated and the configuration works as expected. |
Provider Version
v0.75.0
Terraform Version
1.6.3
Describe the bug
password
is being required and checked even whenprivate_key
is being passed to the providerExpected behavior
password
should be optional whenprivate_key
is providedCode samples and commands
Terraform code:
Terraform error:
Additional context
This was previously working on
v0.72.0
The text was updated successfully, but these errors were encountered: