Skip to content
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

Improvement/bug: alert or warn when a masking policy specified does not exist #54

Open
food-spotter opened this issue Nov 24, 2022 · 0 comments

Comments

@food-spotter
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant