Replies: 1 comment
-
I'll come back to this in a few days when I have a bit more time, please stay tuned. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, the CLI interface supports excluding or filtering for only specific object types during resolution via the
--exclude-object-types
and--include-object-types
CLI flags, respectively. This is pretty useful, but if this functionality were extended to handle arbitrary selection of specific named objects, I think it could be really powerful.For example, instead of using
--include-object-types DATABASE
to resolve only database objects, suppose a more granular selection method was available for just a single database that already exists in Snowflake. For instance,--include-objects DATABASE:MY_RAW_DATABASE
. This way, if one wanted to execute a more targeted invocation, there's no risk of altering other objects which might contain diffs between the resource config and Snowflake stateThis idea could be extended even further to target objects which are referenced in any DDL expressions which appear in the plan, even if those objects are not the direct targets of the resolution. For example, suppose the plan is outputting the following change to a pre-existing role:
A user may want to target or exclude this expression explicitly via specification of the individual objects referenced in the expression. For example, suppose one wanted to target grants which affect a specific database or specific schema:
or
^^ Even though the resolved object for this expression would be
ROLE
, since it is referencing both aDATABASE
andSCHEMA
in the expression, it might still be useful to target indirectly via those object referencesBeta Was this translation helpful? Give feedback.
All reactions