-
Notifications
You must be signed in to change notification settings - Fork 427
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
Indices resolution crashing on foreach snowflake_grant_privileges_to_role #2102
Comments
Encountered same error when using
Error log:
|
Also on |
Happens in 0.76.0 as well:
|
The error is gone for |
Hey @matheus-fractal-river @kalinon @hieu-cc resource "snowflake_grant_privileges_to_role" "demo_schema" {
privileges = ["USAGE", "CREATE TABLE", "CREATE STAGE", "CREATE PIPE"]
role_name = snowflake_role.demo_connector_role.name
on_schema {
schema_name = snowflake_schema.demo_schema.name -- this is not correct
schema_name = "\"${snowflake_database.demo_database.name}\".\"${snowflake_schema.demo_schema.name}\"" -- it should be like this
}
} @matheus-fractal-river you must've provided the wrong configuration because it seems you have the same error, but none of your configurations have |
Hey @matheus-fractal-river |
Closing due to long inactivity. If the issue still persists open another gh issue. Thank You. |
Provider Version
0.72.0
Terraform Version
v1.6.0
Describe the bug
I'm trying to run a terraform apply using a module that references a
snowflake_grant_privileges_to_role
with afor_each
command targeting a role created in the same module and a role provided via an external variable, which is resulting on this stack trace:Expected behavior
I expect the terraform apply to correctly manage the permissions for each role I included on my
for_each
block.Code samples and commands
This is the problem code:
Additional context
The reference found on the for_each session is both the snowflake_role.dbt_role resource created with:
And the external variable provided upon the module call like this:
The text was updated successfully, but these errors were encountered: