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

Cannot Create/Update Stage with File Format #1067

Closed
mhconradt opened this issue Jun 20, 2022 · 1 comment
Closed

Cannot Create/Update Stage with File Format #1067

mhconradt opened this issue Jun 20, 2022 · 1 comment
Labels
bug Used to mark issues with provider's incorrect behavior

Comments

@mhconradt
Copy link

Provider Version

Terraform v1.2.3
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v4.2.0
+ provider registry.terraform.io/snowflake-labs/snowflake v0.33.0

Describe the bug

I cannot create a stage object with a file format. This is optional but quite useful.

Expected behavior

I should be able to create a stage object with a file format.

Code samples and commands

resource "snowflake_file_format" "default" {
  name        = "EXAMPLE_FILE_FORMAT"
  database    = "EXAMPLE_DB"
  schema      =  "EXAMPLE_SCHEMA"
  format_type = "PARQUET"
  compression = "AUTO"
}

resource "snowflake_stage" "default" {
  name        = "EXAMPLE_STAGE"
  url         = "s3://EXAMPLE-BUCKET/"
  database    =  "EXAMPLE_DB"
  schema      =  "EXAMPLE_SCHEMA"
  file_format = snowflake_file_format.default.name
}

Additional context

This is actually fairly simple, the provider is just wrapping the file format name in parentheses and Snowflake interprets this as a list of length one, which is actually a syntax error.

CREATE STAGE "EXAMPLE_DB"."EXAMPLE_SCHEMA"."EXAMPLE_STAGE" URL = 's3://BUCKET/' FILE_FORMAT = (DEFAULT_FILE_FORMAT)
@mhconradt mhconradt added the bug Used to mark issues with provider's incorrect behavior label Jun 20, 2022
@sfc-gh-asawicki
Copy link
Collaborator

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.

@sfc-gh-asawicki sfc-gh-asawicki closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to mark issues with provider's incorrect behavior
Projects
None yet
Development

No branches or pull requests

2 participants