You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context:
We currently use Terraform to manage/maintain our Snowflake account. This includes creating masking policies. Due to limitations in the current Terraform provider, it is not possible to apply masking policies to columns.
Problem:
We encountered an issue where we accidentally wrote the wrong masking policy name and run dbt. The result was a success from the output. We tried testing the column policy by running a SELECT query and it turns out the policy was not applied.
After we realised it was a typo and dbt was re-run, we couls see the dbt output showing the masking policies it has added. We confirmed by running a SELECT query and things were as expected 👍
Expectation:
We would have expected some sort of warning or error be raised when an incorrect masking policy name has been provided.
The rationale for this is that applying a masking policy is fundamentally about protecting visibility to sensitive data and ensuring the right governance rules are applied against it. For something this important, it should be important to raise awareness to when a policy could not be applied.
The text was updated successfully, but these errors were encountered:
Context:
We currently use Terraform to manage/maintain our Snowflake account. This includes creating masking policies. Due to limitations in the current Terraform provider, it is not possible to apply masking policies to columns.
Problem:
We encountered an issue where we accidentally wrote the wrong masking policy name and run dbt. The result was a success from the output. We tried testing the column policy by running a SELECT query and it turns out the policy was not applied.
After we realised it was a typo and dbt was re-run, we couls see the dbt output showing the masking policies it has added. We confirmed by running a SELECT query and things were as expected 👍
Expectation:
We would have expected some sort of warning or error be raised when an incorrect masking policy name has been provided.
The rationale for this is that applying a masking policy is fundamentally about protecting visibility to sensitive data and ensuring the right governance rules are applied against it. For something this important, it should be important to raise awareness to when a policy could not be applied.
The text was updated successfully, but these errors were encountered: