-
Notifications
You must be signed in to change notification settings - Fork 414
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_object_parameter parsing error #2669
Comments
Hey @gdelia-pm |
Thanks Jan, no rush from my end I have a workaround I just put in place for it. |
…2675) When issuing `object_type = "USER"` via the `snowflake_object_parameter` resource the `ShowObjectParameter` function did not handle the `ObjectTypeUser` which led to invalid ObjectType errors. ## Test Plan * [x] acceptance tests ## References * ~~Fixes #2669~~ Actually, I re-reading this issue I don't think it fixes this error.
@sfc-gh-asawicki Hi Artur, I don't see this as having fixed the issue. Running the below version and still see the same improperly parsed email address being being passed into the query in the above example.
|
Hey @gdelia-pm. It was not released yet. I agree that this PR probably did not solve this issue, but because it was linked somewhere inside the PR, it was closed automatically by GH. Reopening now. |
Hey @gdelia-pm 👋 |
It doesn't work cleanly for how we setup users, since we do that completely outside of terraform, and this is a setting we'd only want a small number of users to have. |
Terraform CLI and Provider Versions
Terraform Configuration
Expected Behavior
Applies the query
ALTER User "[email protected]" SET ENABLE_UNREDACTED_QUERY_SYNTAX_ERROR = true
Actual Behavior
Improperly parses the email address used for the user causing the command to fail.
ALTER User "USERNAME@EMAIL"."COM" SET ENABLE_UNREDACTED_QUERY_SYNTAX_ERROR = true
Steps to Reproduce
How much impact is this issue causing?
Medium
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: