.SrSSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSK J r SS K J r S rSS jrS S SS.SSjjrg)z.Shared resource args for the Dataplex surface.)absolute_import) annotations)division)unicode_literals) arg_parsers)parser_arguments)parsers) labels_utilcURSS9nURS[RSS9 URS/[R"5SSS 9 URS /[R"5S S S 9 URS S9nURSSS9 URSS9nURSS9nURS[ SS9 URSSS9 URSSS9 URS[RSS9 URSS9nURSSS9 URS[RSS9 U$)zAdds Discovery Args to parser.z9Settings to manage the metadata discovery and publishing.helpz--discovery-enabledzWhether discovery is enabled.actionr z--discovery-include-patternsINCLUDE_PATTERNSaUThe list of patterns to apply for selecting data to include during discovery if only a subset of the data should considered. For Cloud Storage bucket assets, these are interpreted as glob patterns used to match object names. For BigQuery dataset assets, these are interpreted as patterns to match table names.)defaulttypemetavarr z--discovery-exclude-patternsEXCLUDE_PATTERNSaThe list of patterns to apply for selecting data to exclude during discovery. For Cloud Storage bucket assets, these are interpreted as glob patterns used to match object names. For BigQuery dataset assets, these are interpreted as patterns to match table names.z-Determines when discovery jobs are triggered.z--discovery-schedulez[Cron schedule](https://en.wikipedia.org/wiki/Cron) for running discovery jobs periodically. Discovery jobs must be scheduled at least 30 minutes apart.zDescribe data formats.z6Describe CSV and similar semi-structured data formats.z--csv-header-rowsz]The number of rows to interpret as header rows that should be skipped when reading data rows.)rr z--csv-delimiterzBThe delimiter being used to separate values. This defaults to ','.z--csv-encodingz9The character encoding of the data. The default is UTF-8.z--csv-disable-type-inferencezoWhether to disable the inference of data type for CSV data. If true, all columns will be registered as strings.zDescribe JSON data format.z--json-encodingz--json-disable-type-inferencez Whether to disable the inference of data type for Json data. If true, all columns will be registered as their primitive types (strings, number or boolean).) add_group add_argumentrStoreTrueFalseActionArgListint)parserdiscovery_spectriggerdiscovery_prefix csv_option json_options 0lib/googlecloudsdk/command_lib/dataplex/flags.pyAddDiscoveryArgsr!s## F$.  - - * $      9  $      K    $ $ : % '  + $--3K-L)) C**   -   O  F $  - - 8 !**0L*M+  F%  - - +  c^^URSS9mS$UU4SjjnU"SSSS9 U"SS S S9 U"S S S S9 U"SSSS9 U"SSSS9 U"SS[RSS9 TnT(a:TR5n[R "SS9R U5nSUl[R"SS9R U5 T(d$TRSS[R"SS9SS9 TRS S![RTSS"9 g#)%aCAdd entry source update args. Args: parser: The arg parser to add flags to. for_update: If True, then indicates that arguments are intended for Update command. In such case for each clearable argument there will be also `--clear-...` flag added in a mutually exclusive group to support clearing the field. zSource system related information for an entry. If any of the entry source fields are specified, then ``--entry-source-update-time` must be specified as well.r c >TnT(a8TR5nURSU-SSURSS5S3S9 UR"SU-40UD6 g) Nz--clear-entry-source- store_truezClear the value for the -_z field in the Entry Source.rz--entry-source-)add_mutually_exclusive_grouprreplace)namekwargs parser_to_add entry_source for_updates r AddArgument'AddEntrySourceArgs..AddArgumentsr M"??Am  !D ((c3)?(@A !047B6Br"resourcez.The name of the resource in the source system.RESOURCE)r rsystemzThe name of the source system. SYSTEM_NAMEplatformz*The platform containing the source system. PLATFORM_NAMEz display-namezUser friendly display name. DISPLAY_NAME descriptionzDescription of the Entry. DESCRIPTIONz create-timez@The creation date and time of the resource in the source system. DATE_TIME)r rrzentry-source-labels) labels_namez&Clear the labels for the Entry Source.z--entry-source-ancestorsz@Information about individual items in the hierarchy of an Entry.T) includes_json ANCESTORSz--entry-source-update-timez>The update date and time of the resource in the source system.)r rrequiredrN)r*str) rdataplex_parsers IsoDateTimer(r GetClearLabelsFlag AddToParserr GetCreateLabelsFlagrrr)rr.r/entry_source_labels_container clear_flagr-s ` @r AddEntrySourceArgsrGrs]!! (",CC$ ;  +  7  (  &  M  ' ' #/$0$M$M$O!//)k/0?JO !!'K-. " O  t 4 " K  ' ' r"zupdate-aspectszremove-aspectsF)update_aspects_nameremove_aspects_namer>cSnUbUb SUSUSUS3nUb'URSU3SU-[RS US 9 Ub-URSU3S U-[R"5S US 9 gg) asAdds flags for updating and removing Aspects. Args: parser: The arg parser to add flags to. update_aspects_name: Name of the flag to add for updating Aspects or None if no flag should be added. remove_aspects_name: Name of the flag to add for removing Aspects or None if no flag should be added. required: If True, then flags will be marked as required. Nz If both `--z ` and `--z^` flags are specified, and the same aspect key is used in both flags, then `--zT` takes precedence, and such an aspect will be updated and not removed. z--a% Path to a YAML or JSON file containing Aspects to add or update. When this flag is specified, only Aspects referenced in the file are going to be added or updated. Specifying this flag does not remove any Aspects from the entry. In other words, specifying this flag will not lead to a full replacement of Aspects with a contents of the provided file. Content of the file contains a map, where keys are in the format ``ASPECT_TYPE@PATH'', or just ``ASPECT_TYPE'', if the Aspect is attached to an entry itself rather than to a specific column defined in the schema. Values in the map represent Aspect's content, which must conform to a template defined for a given ``ASPECT_TYPE''. Each Aspect will be replaced fully by the provided content. That means data in the Aspect will be replaced and not merged with existing contents of that Aspect in the Entry. ``ASPECT_TYPE'' is expected to be in a format ``PROJECT_ID.LOCATION.ASPECT_TYPE_ID''. ``PATH'' can be either empty (which means a 'root' path, such that Aspect is attached to the entry itself) or point to a specific column defined in the schema. For example: `Schema.some_column`. Example YAML format: ``` project-id1.us-central1.my-aspect-type1: data: aspectField1: someValue aspectField2: someOtherValue project-id2.us-central1.my-aspect-type2@Schema.column1: data: aspectField3: someValue3 ``` Example JSON format: ``` { "project-id1.us-central1.my-aspect-type1": { "data": { "aspectField1": "someValue", "aspectField2": "someOtherValue" } }, "project-id2.us-central1.my-aspect-type2@Schema.column1": { "data": { "aspectField3": "someValue3" } } } ``` YAML_OR_JSON_FILE)r rrr>a  List of Aspect keys, identifying Aspects to remove from the entry. Keys are in the format ``ASPECT_TYPE@PATH'', or just ``ASPECT_TYPE'', if the Aspect is attached to an entry itself rather than to a specific column defined in the schema. ``ASPECT_TYPE'' is expected to be in a format ``PROJECT_ID.LOCATION.ASPECT_TYPE_ID'' or a wildcard `*`, which targets all aspect types. ``PATH'' can be either empty (which means a 'root' path, such that Aspect is attached to the entry itself), point to a specific column defined in the schema (for example: `Schema.some_column`) or a wildcard `*` (target all paths). ``ASPECT_TYPE'' and ``PATH'' cannot be both specified as wildcards `*`.zASPECT_TYPE@PATH)rr@ ParseAspectsrr)rrHrIr>combination_help_texts r AddAspectFlagsrOs"$)<)H!'( 2E1FG  ! $  !"7 n$o7$p * *#y=~$  !"S" # $ ""-%r"N)r$parser_arguments.ArgumentInterceptorr.bool)rrPrH str | NonerIrRr>rQ)__doc__ __future__rrrrgooglecloudsdk.callioperr#googlecloudsdk.command_lib.dataplexr r@$googlecloudsdk.command_lib.util.argsr r!rGrOr"r rYs}5&"'/4K<Rld 0d>BdT'7&6 s 0s$s$ s  sr"