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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
resource"google_bigquery_datapolicy_data_policy""data_policy" {
provider=google-beta
location="us-central1"data_policy_id="data_policy"policy_tag=google_data_catalog_policy_tag.policy_tag.namedata_policy_type="COLUMN_LEVEL_SECURITY_POLICY"data_masking_policy {
predefined_expression="DATE_YEAR_MASK"# support add all possible values for this that exist in v1
}
}
References
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Description
This resource https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/data_catalog_policy_tag which uses the v1beta1 API is missing some of the options that are currently available in v1, namely the options for the
data_masking_policy.predefined_expression
field. It's currently missingDATE_YEAR_MASK
which exists in the v1 API, but not in the v1beta1 API. Can we support the extra options that exist in v1? Link to v1 API. https://cloud.google.com/bigquery/docs/reference/bigquerydatapolicy/rest/v1/projects.locations.dataPoliciesNew or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: