-
Notifications
You must be signed in to change notification settings - Fork 428
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
[Bug] SNOW-1865901: Error: 260000: account is empty with usage auth with profile. snowflake provider v1.0.0 #3308
Comments
hi - thanks for reporting this issue. reproduced it and it seems to happen because we seem to have removed the possibility of using account locators ( in this sense, your issue is the same as #3198 using this profile
seems to work for me, can you please test ? To get your organization name and account (alias) name to use in the config, please execute |
Thanks @sfc-gh-dszmolka @sfc-gh-asawicki for speedily answer. [myprofile] it's work |
sounds good ! we also extended the FAQ a little bit with this specific error message. closing this issue now. |
I am also getting the I previously had SNOWFLAKE_ACCOUNT and SNOWFLAKE_REGION set in my environment. I've tried setting SNOWFLAKE_ACCOUNT_NAME="xy12345" and SNOWFLAKE_ORGANIZATION_NAME="ASDFGHJ" but am getting a failure:
|
Ignore me! Resolved in another issue. #3369 |
Terraform CLI Version
1.8.2
Terraform Provider Version
1.0.0
Company Name
No response
Terraform Configuration
Category
category:provider_config
Object type(s)
No response
Expected Behavior
working "terraform apply" command
Actual Behavior
│ Error: 260000: account is empty
│
│ with provider["registry.terraform.io/snowflake-labs/snowflake"],
│ on versions.tf line 19, in provider "snowflake":
│ 19: provider "snowflake" {
│
Steps to Reproduce
How much impact is this issue causing?
Medium
Logs
No response
Additional Information
I also tried using the variables "account_name" and "accountname" in the profile.
In version 0.100.0 and oldest all work fine with this setup.
Would you like to implement a fix?
The text was updated successfully, but these errors were encountered: