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

snowflake_stage errors don't bubble up (always shows generic error creating stage S3_STAGE instead) #2188

Open
ChannyClaus opened this issue Nov 11, 2023 · 1 comment
Labels
category:other feature-request Used to mark issues with provider's missing functionalities

Comments

@ChannyClaus
Copy link

Provider Version

$ terraform  providers

Providers required by configuration:
.
└── provider[registry.terraform.io/snowflake-labs/snowflake] 0.75.0

The provider version you are using.

Terraform Version

$ terraform  --version
Terraform v1.5.7
on darwin_arm64
+ provider registry.terraform.io/snowflake-labs/snowflake v0.75.0

Your version of Terraform is out of date! The latest version
is 1.6.3. You can update by downloading from https://www.terraform.io/downloads.html

The version of Terraform you were using when the bug was encountered.

Describe the bug

A clear and concise description of what the bug is.

Expected behavior
The errors returned by Snowflake server doesn't get bubbled up on the console - you just get the generic "error creating stage blah" instead. To be able to see the error, you'd have to set the env var TF_LOG=debug and run terraform apply again, which is suboptimal.

Code samples and commands

resource "snowflake_stage" "s3_stage" {
  name        = "S3_STAGE"
  url         = "s3://blahblah"
  database    = "DATABASE"
  schema      = "SCHEMA"
}
terraform {
  required_providers {
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "0.75.0"
    }
  }
}

provider "snowflake" {
  account  = # redacted
  user     = # redacted
  password = # redacted
}

Please add code examples and commands that were run to cause the problem.

Additional context

Add any other context about the problem here.

@ChannyClaus ChannyClaus added the bug Used to mark issues with provider's incorrect behavior label Nov 11, 2023
@sfc-gh-asawicki sfc-gh-asawicki added feature-request Used to mark issues with provider's missing functionalities and removed bug Used to mark issues with provider's incorrect behavior labels Nov 13, 2023
@sfc-gh-asawicki
Copy link
Collaborator

Hey @ChannyClaus. Thanks for creating the issue.

We know that error handling in all the old resources could be better. We pay attention to this topic while adding new resources/reworking the existing ones. We will update most of the resources in the upcoming months and address the error clarity topic then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:other feature-request Used to mark issues with provider's missing functionalities
Projects
None yet
Development

No branches or pull requests

3 participants