Skip to content

Commit

Permalink
docs: SNOW-1865901 add faq for account is empty (#3312)
Browse files Browse the repository at this point in the history
This is a documentation-only change, no code was changed.
Added FAQ entry for `Error: 260000: account is empty` people seem to be
hitting after v1.0.0
  • Loading branch information
sfc-gh-dszmolka authored Dec 20, 2024
1 parent 39a0cb7 commit 3d7ba37
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions CREATING_ISSUES.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,14 @@ Please refer to [this document](https://github.com/Snowflake-Labs/terraform-prov

[GitHub issue reference](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2432#issuecomment-1915074774)

**Problem**: Getting `Error: 260000: account is empty` error with non-empty `account` configuration after upgrading to v1, with the same provider configuration which worked up to v0.100.0

**Solution**: `account` configuration [has been removed in v1.0.0](https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#removed-deprecated-objects). Please specify your organization name and account name separately as mentioned in the [migration guide](https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#removed-deprecated-objects):
* `account_name` (`accountname` if you're sourcing it from `config` TOML)
* `organization_name` (`organizationname` if you're sourcing it from `config` TOML)

GitHub issue reference: [#3198](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/3198), [#3308](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/3308)

### How to set up the connection with the private key?
**Problem:** From the version v0.78.0, we introduced a lot of provider configuration changes. One of them was deprecating `private_key_path` in favor of `private_key`.

Expand Down

0 comments on commit 3d7ba37

Please sign in to comment.