Class: Google::Privacy::Dlp::V2::StorageConfig

Inherits:
Object
  • Object
show all
Defined in:
lib/google/cloud/dlp/v2/doc/google/privacy/dlp/v2/storage.rb

Overview

Shared message indicating Cloud storage type.

Defined Under Namespace

Classes: TimespanConfig

Instance Attribute Summary collapse

Instance Attribute Details

#big_query_options ⇒ Google::Privacy::Dlp::V2::BigQueryOptions

Returns BigQuery options.

Returns:



443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
 
# File 'lib/google/cloud/dlp/v2/doc/google/privacy/dlp/v2/storage.rb', line 443

class StorageConfig
  # Configuration of the timespan of the items to include in scanning.
  # Currently only supported when inspecting Google Cloud Storage and BigQuery.
  # @!attribute [rw] start_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows older than this value.
  # @!attribute [rw] end_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows newer than this value.
  #     If set to zero, no upper time limit is applied.
  # @!attribute [rw] timestamp_field
  #   @return [Google::Privacy::Dlp::V2::FieldId]
  #     Specification of the field containing the timestamp of scanned items.
  #     Used for data sources like Datastore and BigQuery.
  #
  #     For BigQuery:
  #     Required to filter out rows based on the given start and
  #     end times. If not specified and the table was modified between the given
  #     start and end times, the entire table will be scanned.
  #     The valid data types of the timestamp field are: `INTEGER`, `DATE`,
  #     `TIMESTAMP`, or `DATETIME` BigQuery column.
  #
  #     For Datastore.
  #     Valid data types of the timestamp field are: `TIMESTAMP`.
  #     Datastore entity will be scanned if the timestamp property does not
  #     exist or its value is empty or invalid.
  # @!attribute [rw] enable_auto_population_of_timespan_config
  #   @return [true, false]
  #     When the job is started by a JobTrigger we will automatically figure out
  #     a valid start_time to avoid scanning files that have not been modified
  #     since the last time the JobTrigger executed. This will be based on the
  #     time of the execution of the last run of the JobTrigger.
  class TimespanConfig; end
end

#cloud_storage_options ⇒ Google::Privacy::Dlp::V2::CloudStorageOptions

Returns Google Cloud Storage options.

Returns:



443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
 
# File 'lib/google/cloud/dlp/v2/doc/google/privacy/dlp/v2/storage.rb', line 443

class StorageConfig
  # Configuration of the timespan of the items to include in scanning.
  # Currently only supported when inspecting Google Cloud Storage and BigQuery.
  # @!attribute [rw] start_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows older than this value.
  # @!attribute [rw] end_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows newer than this value.
  #     If set to zero, no upper time limit is applied.
  # @!attribute [rw] timestamp_field
  #   @return [Google::Privacy::Dlp::V2::FieldId]
  #     Specification of the field containing the timestamp of scanned items.
  #     Used for data sources like Datastore and BigQuery.
  #
  #     For BigQuery:
  #     Required to filter out rows based on the given start and
  #     end times. If not specified and the table was modified between the given
  #     start and end times, the entire table will be scanned.
  #     The valid data types of the timestamp field are: `INTEGER`, `DATE`,
  #     `TIMESTAMP`, or `DATETIME` BigQuery column.
  #
  #     For Datastore.
  #     Valid data types of the timestamp field are: `TIMESTAMP`.
  #     Datastore entity will be scanned if the timestamp property does not
  #     exist or its value is empty or invalid.
  # @!attribute [rw] enable_auto_population_of_timespan_config
  #   @return [true, false]
  #     When the job is started by a JobTrigger we will automatically figure out
  #     a valid start_time to avoid scanning files that have not been modified
  #     since the last time the JobTrigger executed. This will be based on the
  #     time of the execution of the last run of the JobTrigger.
  class TimespanConfig; end
end

#datastore_options ⇒ Google::Privacy::Dlp::V2::DatastoreOptions

Returns Google Cloud Datastore options.

Returns:



443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
 
# File 'lib/google/cloud/dlp/v2/doc/google/privacy/dlp/v2/storage.rb', line 443

class StorageConfig
  # Configuration of the timespan of the items to include in scanning.
  # Currently only supported when inspecting Google Cloud Storage and BigQuery.
  # @!attribute [rw] start_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows older than this value.
  # @!attribute [rw] end_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows newer than this value.
  #     If set to zero, no upper time limit is applied.
  # @!attribute [rw] timestamp_field
  #   @return [Google::Privacy::Dlp::V2::FieldId]
  #     Specification of the field containing the timestamp of scanned items.
  #     Used for data sources like Datastore and BigQuery.
  #
  #     For BigQuery:
  #     Required to filter out rows based on the given start and
  #     end times. If not specified and the table was modified between the given
  #     start and end times, the entire table will be scanned.
  #     The valid data types of the timestamp field are: `INTEGER`, `DATE`,
  #     `TIMESTAMP`, or `DATETIME` BigQuery column.
  #
  #     For Datastore.
  #     Valid data types of the timestamp field are: `TIMESTAMP`.
  #     Datastore entity will be scanned if the timestamp property does not
  #     exist or its value is empty or invalid.
  # @!attribute [rw] enable_auto_population_of_timespan_config
  #   @return [true, false]
  #     When the job is started by a JobTrigger we will automatically figure out
  #     a valid start_time to avoid scanning files that have not been modified
  #     since the last time the JobTrigger executed. This will be based on the
  #     time of the execution of the last run of the JobTrigger.
  class TimespanConfig; end
end

#hybrid_options ⇒ Google::Privacy::Dlp::V2::HybridOptions

Returns Hybrid inspection options. Early access feature is in a pre-release state and might change or have limited support. For more information, see https://cloud.google.com/products#product-launch-stages.

Returns:



443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
 
# File 'lib/google/cloud/dlp/v2/doc/google/privacy/dlp/v2/storage.rb', line 443

class StorageConfig
  # Configuration of the timespan of the items to include in scanning.
  # Currently only supported when inspecting Google Cloud Storage and BigQuery.
  # @!attribute [rw] start_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows older than this value.
  # @!attribute [rw] end_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows newer than this value.
  #     If set to zero, no upper time limit is applied.
  # @!attribute [rw] timestamp_field
  #   @return [Google::Privacy::Dlp::V2::FieldId]
  #     Specification of the field containing the timestamp of scanned items.
  #     Used for data sources like Datastore and BigQuery.
  #
  #     For BigQuery:
  #     Required to filter out rows based on the given start and
  #     end times. If not specified and the table was modified between the given
  #     start and end times, the entire table will be scanned.
  #     The valid data types of the timestamp field are: `INTEGER`, `DATE`,
  #     `TIMESTAMP`, or `DATETIME` BigQuery column.
  #
  #     For Datastore.
  #     Valid data types of the timestamp field are: `TIMESTAMP`.
  #     Datastore entity will be scanned if the timestamp property does not
  #     exist or its value is empty or invalid.
  # @!attribute [rw] enable_auto_population_of_timespan_config
  #   @return [true, false]
  #     When the job is started by a JobTrigger we will automatically figure out
  #     a valid start_time to avoid scanning files that have not been modified
  #     since the last time the JobTrigger executed. This will be based on the
  #     time of the execution of the last run of the JobTrigger.
  class TimespanConfig; end
end

#timespan_config ⇒ Google::Privacy::Dlp::V2::StorageConfig::TimespanConfig

Returns:



443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
 
# File 'lib/google/cloud/dlp/v2/doc/google/privacy/dlp/v2/storage.rb', line 443

class StorageConfig
  # Configuration of the timespan of the items to include in scanning.
  # Currently only supported when inspecting Google Cloud Storage and BigQuery.
  # @!attribute [rw] start_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows older than this value.
  # @!attribute [rw] end_time
  #   @return [Google::Protobuf::Timestamp]
  #     Exclude files or rows newer than this value.
  #     If set to zero, no upper time limit is applied.
  # @!attribute [rw] timestamp_field
  #   @return [Google::Privacy::Dlp::V2::FieldId]
  #     Specification of the field containing the timestamp of scanned items.
  #     Used for data sources like Datastore and BigQuery.
  #
  #     For BigQuery:
  #     Required to filter out rows based on the given start and
  #     end times. If not specified and the table was modified between the given
  #     start and end times, the entire table will be scanned.
  #     The valid data types of the timestamp field are: `INTEGER`, `DATE`,
  #     `TIMESTAMP`, or `DATETIME` BigQuery column.
  #
  #     For Datastore.
  #     Valid data types of the timestamp field are: `TIMESTAMP`.
  #     Datastore entity will be scanned if the timestamp property does not
  #     exist or its value is empty or invalid.
  # @!attribute [rw] enable_auto_population_of_timespan_config
  #   @return [true, false]
  #     When the job is started by a JobTrigger we will automatically figure out
  #     a valid start_time to avoid scanning files that have not been modified
  #     since the last time the JobTrigger executed. This will be based on the
  #     time of the execution of the last run of the JobTrigger.
  class TimespanConfig; end
end