Skip to content
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

Closed
1 task
Zarubenko opened this issue Dec 19, 2024 · 4 comments
Assignees
Labels
category:migration Issues connected with migration to v1.0.0. category:provider_config general-usage General help/usage questions status-triage_done Initial triage done, will be further handled by the dev team

Comments

@Zarubenko
Copy link

Zarubenko commented Dec 19, 2024

Terraform CLI Version

1.8.2

Terraform Provider Version

1.0.0

Company Name

No response

Terraform Configuration

terraform {
  required_providers {
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "1.0.0"
    }
  }
}
provider "snowflake" {
    profile = "myprofile"
}

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

  1. create config file ~/.snowflake/config
[myprofile]
account = 'accountname'
user = 'username'
password = 'password'
role = 'rolename'
  1. setup provider:
terraform {
  required_providers {
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "1.0.0"
    }
  }
}
provider "snowflake" {
    profile = "myprofile"
}

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?

  • Yeah, I'll take it 😎
@Zarubenko Zarubenko added the bug Used to mark issues with provider's incorrect behavior label Dec 19, 2024
@Zarubenko Zarubenko changed the title [Bug]: Error: 260000: account is empty with usage profile for auth [Bug]: Error: 260000: account is empty with usage auth with profile. snowflake provider v1.0.0 Dec 19, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka self-assigned this Dec 20, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage Issue is under initial triage label Dec 20, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka changed the title [Bug]: Error: 260000: account is empty with usage auth with profile. snowflake provider v1.0.0 [Bug] SNOW-1865901: Error: 260000: account is empty with usage auth with profile. snowflake provider v1.0.0 Dec 20, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka added category:provider_config status-triage_done Initial triage done, will be further handled by the dev team and removed status-triage Issue is under initial triage bug Used to mark issues with provider's incorrect behavior labels Dec 20, 2024
@sfc-gh-dszmolka
Copy link
Collaborator

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 (xy12345.eu-central-1) as an account identifier, and now exclusively allow only for the regionless notation (myorg-myaccount) .

in this sense, your issue is the same as #3198

using this profile

[myprofile]
organizationname = 'MYORG'
accountname = 'MYACCOUNT'
user = 'admin'
password = 'password'
role = 'role'

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 SELECT CURRENT_ORGANIZATION_NAME(), CURRENT_ACCOUNT_NAME(); in your Snowflake GUI.

@sfc-gh-asawicki sfc-gh-asawicki added general-usage General help/usage questions category:migration Issues connected with migration to v1.0.0. labels Dec 20, 2024
@sfc-gh-asawicki
Copy link
Collaborator

sfc-gh-asawicki commented Dec 20, 2024

Adding for visibility: deprecation and later removal were both included in the migration guide here and here.

@Zarubenko
Copy link
Author

Zarubenko commented Dec 23, 2024

Thanks @sfc-gh-dszmolka @sfc-gh-asawicki for speedily answer.

[myprofile]
organizationname = 'MYORG'
accountname = 'MYACCOUNT'
user = 'admin'
password = 'password'
role = 'role'

it's work

@sfc-gh-dszmolka
Copy link
Collaborator

sounds good ! we also extended the FAQ a little bit with this specific error message. closing this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:migration Issues connected with migration to v1.0.0. category:provider_config general-usage General help/usage questions status-triage_done Initial triage done, will be further handled by the dev team
Projects
None yet
Development

No branches or pull requests

3 participants