Resource: DataAccessScope
A DataAccessScope is a boolean expression of data access labels used to restrict access to data for users.
JSON representation |
---|
{ "name": string, "allowed_data_access_labels": [ { object ( |
Fields | |
---|---|
name |
Required. The unique full name of the data access scope. The name should comply with https://google.aip.dev/122 standards. |
allowed_ |
Optional. The allowed labels for the scope. Either allow_all or allowed_data_access_labels needs to be provided. When provided, there has to be at least one label allowed for the scope to be valid. The logical operator for evaluation of the allowed labels is OR. E.g.: A customer with scope with allowed labels A and B will be able to see data with labeled with A or B or (A and B). |
denied_ |
Optional. The denied labels for the scope. The logical operator for evaluation of the denied labels is AND. E.g.: A customer with scope with denied labels A and B won't be able to see data labeled with A and data labeled with B and data with labels A and B. |
display_ |
Output only. The name to be used for display to customers of the data access scope. |
create_ |
Output only. The time at which the data access scope was created. Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted.Examples: |
update_ |
Output only. The time at which the data access scope was last updated. Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted.Examples: |
author |
Output only. The user who created the data access scope. |
last_ |
Output only. The user who last updated the data access scope. |
description |
Optional. A description of the data access scope for a human reader. |
allow_ |
Optional. Whether or not the scope allows all labels, allow_all and allowed_data_access_labels are mutually exclusive and one of them must be present. denied_data_access_labels can still be used along with allow_all. When combined with denied_data_access_labels, access will be granted to all data that doesn't have labels mentioned in denied_data_access_labels. E.g.: A customer with scope with denied labels A and B and allow_all will be able to see all data except data labeled with A and data labeled with B and data with labels A and B. |
DataAccessLabelReference
Reference object to a data access label.
JSON representation |
---|
{ "display_name": string, // Union field |
Fields | |
---|---|
display_ |
Output only. The display name of the label. Data access label and log types's name will match the display name of the resource. The asset namespace will match the namespace itself. The ingestion key value pair will match the key of the tuple. |
Union field label . The unique identifier for the label. label can be only one of the following: |
|
data_ |
The name of the data access label. |
log_ |
The name of the log type. |
asset_ |
The asset namespace configured in the forwarder of the customer's events. |
ingestion_ |
The ingestion label configured in the forwarder of the customer's events. |
IngestionLabel
Representation of an ingestion label type.
JSON representation |
---|
{ "ingestion_label_key": string, "ingestion_label_value": string } |
Fields | |
---|---|
ingestion_ |
Required. The key of the ingestion label. Always required. |
ingestion_ |
Optional. The value of the ingestion label. Optional. An object with no provided value and some key provided would match against the given key and ANY value. |
Methods |
|
---|---|
|
Creates a data access scope. |
|
Deletes a data access scope. |
|
Retrieves an existing data access scope. |
|
Lists all existing data access scopes for the customer. |
|
Updates a data access scope. |