If set, attaches the tags
provided to profiled resources. Tags support access
control. You can
conditionally grant or deny access to a resource based on whether the
resource has a specific tag.
Protobuf type google.privacy.dlp.v2.DataProfileAction.TagResources
Whether applying a tag to a resource should lower the risk of the profile
for that resource. For example, in conjunction with an IAM deny
policy, you can deny
all principals a permission if a tag value is present, mitigating the
risk of the resource. This also lowers the data risk of resources at the
lower levels of the resource hierarchy. For example, reducing the data
risk of a table data profile also reduces the data risk of the
constituent column data profiles.
The profile generations for which the tag should be attached to
resources. If you attach a tag to only new profiles, then if the
sensitivity score of a profile subsequently changes, its tag doesn't
change. By default, this field includes only new profiles. To include
both new and updated profiles for tagging, this field should explicitly
include both PROFILE_GENERATION_NEW and PROFILE_GENERATION_UPDATE.
The profile generations for which the tag should be attached to
resources. If you attach a tag to only new profiles, then if the
sensitivity score of a profile subsequently changes, its tag doesn't
change. By default, this field includes only new profiles. To include
both new and updated profiles for tagging, this field should explicitly
include both PROFILE_GENERATION_NEW and PROFILE_GENERATION_UPDATE.
The profile generations for which the tag should be attached to
resources. If you attach a tag to only new profiles, then if the
sensitivity score of a profile subsequently changes, its tag doesn't
change. By default, this field includes only new profiles. To include
both new and updated profiles for tagging, this field should explicitly
include both PROFILE_GENERATION_NEW and PROFILE_GENERATION_UPDATE.
The profile generations for which the tag should be attached to
resources. If you attach a tag to only new profiles, then if the
sensitivity score of a profile subsequently changes, its tag doesn't
change. By default, this field includes only new profiles. To include
both new and updated profiles for tagging, this field should explicitly
include both PROFILE_GENERATION_NEW and PROFILE_GENERATION_UPDATE.
The profile generations for which the tag should be attached to
resources. If you attach a tag to only new profiles, then if the
sensitivity score of a profile subsequently changes, its tag doesn't
change. By default, this field includes only new profiles. To include
both new and updated profiles for tagging, this field should explicitly
include both PROFILE_GENERATION_NEW and PROFILE_GENERATION_UPDATE.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]
