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
For maximum flexibility given the variety of management styles Snowflake supports for tags and masking policies, this could take the form of a new snowflake_tag_masking_policy_attachment resource. Another benefit of that approach is it neatly resolves an issue arising from this pair of rules from the documentation:
A tag cannot be dropped if it is assigned to a masking policy.
A masking policy cannot be dropped if it is assigned to a tag.
Having a separate attachment resource which depends on both the tag and masking policy objects means that terraform will destroy the attachment before destroying the tag or masking policy.
The structure of the resource would be something like:
Snowflake now has the ability to set a masking policy on a tag object. See Tag-based Masking Policies.
For maximum flexibility given the variety of management styles Snowflake supports for tags and masking policies, this could take the form of a new
snowflake_tag_masking_policy_attachment
resource. Another benefit of that approach is it neatly resolves an issue arising from this pair of rules from the documentation:Having a separate attachment resource which depends on both the tag and masking policy objects means that terraform will destroy the attachment before destroying the tag or masking policy.
The structure of the resource would be something like:
The text was updated successfully, but these errors were encountered: