google-cloud-dlp-v2 0.17.0 → 0.19.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/google/cloud/dlp/v2/dlp_service/client.rb +592 -46
- data/lib/google/cloud/dlp/v2/dlp_service/paths.rb +19 -0
- data/lib/google/cloud/dlp/v2/dlp_service/rest/client.rb +1205 -139
- data/lib/google/cloud/dlp/v2/dlp_service/rest/service_stub.rb +334 -0
- data/lib/google/cloud/dlp/v2/version.rb +1 -1
- data/lib/google/privacy/dlp/v2/dlp_pb.rb +42 -1
- data/lib/google/privacy/dlp/v2/dlp_services_pb.rb +10 -0
- data/lib/google/privacy/dlp/v2/storage_pb.rb +1 -1
- data/proto_docs/google/api/field_behavior.rb +14 -0
- data/proto_docs/google/privacy/dlp/v2/dlp.rb +930 -111
- data/proto_docs/google/privacy/dlp/v2/storage.rb +83 -35
- metadata +5 -5
@@ -66,6 +66,20 @@ module Google
|
|
66
66
|
# a non-empty value will be returned. The user will not be aware of what
|
67
67
|
# non-empty value to expect.
|
68
68
|
NON_EMPTY_DEFAULT = 7
|
69
|
+
|
70
|
+
# Denotes that the field in a resource (a message annotated with
|
71
|
+
# google.api.resource) is used in the resource name to uniquely identify the
|
72
|
+
# resource. For AIP-compliant APIs, this should only be applied to the
|
73
|
+
# `name` field on the resource.
|
74
|
+
#
|
75
|
+
# This behavior should not be applied to references to other resources within
|
76
|
+
# the message.
|
77
|
+
#
|
78
|
+
# The identifier field of resources often have different field behavior
|
79
|
+
# depending on the request it is embedded in (e.g. for Create methods name
|
80
|
+
# is optional and unused, while for Update methods it is required). Instead
|
81
|
+
# of method-specific annotations, only `IDENTIFIER` is required.
|
82
|
+
IDENTIFIER = 8
|
69
83
|
end
|
70
84
|
end
|
71
85
|
end
|