Support for table_grant and/or future table grants about terraform-provider-snowflake HOT 6 CLOSED

@pwnage101 I think that makes sense and is a simpler api. Let's see if it works?

from terraform-provider-snowflake.

Maybe this is a bit more complicated then I'm imagining because I also run the following:

GRANT SELECT ON ALL FUTURE TABLES IN SCHEMA <schema> TO ...

But to read those grants you would actually query the schema:

SHOW FUTURE GRANTS IN SCHEMA <schema>

from terraform-provider-snowflake.

Perhaps this would require some sort of schema_future_object_grant resource with the following parameters:

And a possible example:

resource "snowflake_schema_future_object_grant" "foo" {
  privilege = "SELECT"
  database_name = "PROD"
  schema_name = "MYSCHEMA"
  object_type = "TABLE"
  roles = [ "MYSCHEMA_READER" ]
}

# equivalent to: GRANT SELECT ON ALL FUTURE TABLES IN SCHEMA PROD.MYSCHEMA TO ROLE MYSCHEMA_READER

from terraform-provider-snowflake.

@pwnage101 I'm not sure that a separate resource makes sense vs adding a boolean on_future parameter to snowflake_view_grant, etc.

from terraform-provider-snowflake.

My reservation to modifying the existing view_grant was that it has a view_name parameter which would be irrelevant to future grants, so I would have to change it from required to optional.

from terraform-provider-snowflake.

But if that were the case, then it could look like:

resource "snowflake_view_grant" {
  privilege = "SELECT"
  future_views = true
  database_name = "PROD"
  schema_name = "MYSCHEMA"
  object_type = "TABLE"
  roles = [ "MYSCHEMA_READER" ]
  # setting view_name is invalid when future_views = true
  # setting shares is invalid when future_views = true
}

Setting view_name becomes required when future_views = false, and shares becomes valid but optional.

from terraform-provider-snowflake.