pBSrSSKJr SSKJr SSKJr SSKrSSKJr SrSr S R\\ 5r S R\5r "S S \R5r"S S\R5r"SS\R5r"SS\R5r"SS\R5r"SS\R5r"SS\R5r"SS\R5r"SS\R5r"SS\R5rSrS!S jrg)"z[Utils for managng the many transfer job flags. Tested more through command surface tests. )absolute_import)division)unicode_literalsN) arg_parsersaiPOSIX filesystem - Specify the `posix://` scheme followed by the absolute path to the desired directory, starting from the root of the host machine (denoted by a leading slash). For example: * posix:///path/directory/ A file transfer agent must be installed on the POSIX filesystem, and you need an agent pool flag on this `jobs` command to activate the agent.aHadoop Distributed File System (HDFS) - Specify the `hdfs://` scheme followed by the absolute path to the desired directory, starting from the root of the file system (denoted by a leading slash). For example: * hdfs:///path/directory/ Namenode details should not be included in the path specification, as they are required separately during the agent installation process. A file transfer agent must be installed, and you need an agent pool flag on this `jobs` command to activate the agent.aThe source of your data. Available sources and formatting information: Public clouds - * [Google Cloud Storage] gs://example-bucket/example-folder/ * [Amazon S3] s3://examplebucket/example-folder * [Azure Blob Storage or Data Lake Storage] http://examplestorageaccount.blob.core.windows.net/examplecontainer/examplefolder {} {} Publicly-accessible objects - Specify the URL of a TSV file containing a list of URLs of publicly-accessible objects. For example: * http://example.com/tsvfileaThe destination of your transferred data. Available destinations and formatting information: Google Cloud Storage - Specify the `gs://` scheme; name of the bucket; and, if transferring to a folder, the path to the folder. For example: * gs://example-bucket/example-folder/ {}c\rSrSrSrSrSrg) AuthMethodBAWS_SIGNATURE_V2AWS_SIGNATURE_V4N)__name__ __module__ __qualname____firstlineno__r r __static_attributes__r 9lib/googlecloudsdk/command_lib/transfer/jobs_flag_util.pyrrBs''rrc\rSrSrSrSrSrg) DeleteOptionGzdestination-if-uniquezsource-after-transferr N)r rrrDESTINATION_IF_UNIQUESOURCE_AFTER_TRANSFERrr rrrrGs11rrc \rSrSrSrSrSrSrg) JobStatusLdeleteddisabledenabledr N)r rrrDELETEDDISABLEDENABLEDrr rrrrLs ' ( 'rrc \rSrSrSrSrSrSrg) LogActionRcopydeletefindr N)r rrrCOPYDELETEFINDrr rrr#r#Rs $ & $rr#c \rSrSrSrSrSrSrg)LogActionStateXfailed succeededskippedr N)r rrrFAILED SUCCEEDEDSKIPPEDrr rrr,r,Xs &) 'rr,c8\rSrSrSrSrSrSrSrSr Sr S r S r S r g ) PreserveMetadataField^aclgidzkms-keymodez storage-classsymlinkztemporary-holdz time-createduidr N)r rrrACLGIDKMS_KEYMODE STORAGE_CLASSSYMLINKTEMPORARY_HOLD TIME_CREATEDUIDrr rrr5r5^s/ # # ' $!- '#., #rr5c\rSrSrSrSrSrg)ListApij LIST_OBJECTSLIST_OBJECTS_V2r N)r rrrrHrIrr rrrFrFjs ,%/rrFc\rSrSrSrSrSrg)NetworkProtocoloHTTPHTTPSr N)r rrrrMrNrr rrrKrKos $ %rrKc \rSrSrSrSrSrSrg)OverwriteOptiontalways differentneverr N)r rrrALWAYS DIFFERENTNEVERrr rrrPrPts &) %rrPc\rSrSrSrSrSrg) RequestModelz PATH_STYLEVIRTUAL_HOSTED_STYLEr N)r rrrr[r\rr rrrYrYzs */rrYc$URSSS9 g)Nz--source-creds-filea^Path to a local file on your machine that includes credentials for an Amazon S3 or Azure Blob Storage source (not required for Google Cloud Storage sources). If not specified for an S3 source, gcloud will check your system for an AWS config file. However, this flag must be specified to use AWS's "role_arn" auth service. For formatting, see: S3: https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#AwsAccessKey Note: Be sure to put quotations around the JSON value strings. Azure: https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials help) add_argument)parsers radd_source_creds_flagrbs - .rc TAURS5 U(aURSSS9 O(URS[S9 URS[S9 UR SSS9nU(aURS [ S [ 55S S 9 URS [S9 URS[S9 URSSSS9 URSSSS9 URSSSS9 URSSSS9 URSSSS9 URSSSS9 OURSSS9 URSS S9 [U5 URS!S"S9 URS#S$S9 URS%S&S9 URS'S(S9 U(d UR S)S9nURS*SS+S9 UR S,SS9nURS-S.S9 URS/S0S9 URS1S2S9 U(aURS3SS4S9 UR S5SS9nU(aURS6SS7S9 OURS8SS9S9 URS:[RRS;S<9 URS=[R"5S>S<9 URS?[RRS@S<9 UR SASS9nU(afURSBSSCS9 URSDSSES9 URSFSSGS9 URSHSSIS9 URSJSSKS9 URSLSSMS9 URSN[R"5SOSPSQ9 URSR[R"5SSSTSQ9 URSU[RRSVS<9 URSW[RRSXS<9 URSY[R"5SZS<9 URS[[R"5S\S<9 UR S]SS9nU(a3URS^SS_S9 URS`SSaS9 URSbSScS9 URSd[ Se[55SfS 9 URSg[ Sh[55SiS 9 URSj[R"[ Sk[55Sl9SmSnSQ9 URSoSpS9 UR SqSS9n U(a"U RSrSSsS9 U RStSSuS9 U RSvSwS9 U RSx[R"/SyQSl9SzS{SQ9 U RS|S}S~/SS 9 UR SSS9n U(aU RSSSS9 U RS[R SS9 U RS[R"[ S["55Sl9SSSQ9 U RS[R"[ S[$55Sl9SSSQ9 UR SSS9n U RSSS9 U RSSS9 U RS[ S[&55SS 9 U RS[ S[(55SS 9 U RS[ S[*55SS 9 U RS[ S[,55SS 9 U RSSS9 U(awU RSSSS9 U RSSSS9 U RSSSS9 U RSSSS9 U RSSSS9 U RSSSS9 U RSSSS9 U(d"UR SSS9n U RSSSS9 gg)z1Adds flags to job create and job update commands.Fnamez.Name of the transfer job you'd like to update.r^source destinationzJOB INFORMATION)r_ sort_argsz--statusc38# UHoRv M g7fNvalue).0statuss r setup_parser..s<)||)zdSpecify this flag to change the status of the job. Options include 'enabled', 'disabled', 'deleted'.)choicesr_z--sourcez --destinationz--clear-description store_truez-Remove the description from the transfer job.)actionr_z--clear-source-creds-filez3Remove the source creds file from the transfer job.z--clear-source-agent-poolz3Remove the source agent pool from the transfer job.z--clear-destination-agent-poolz8Remove the destination agent pool from the transfer job.z!--clear-intermediate-storage-pathz;Remove the intermediate storage path from the transfer job.z--clear-manifest-filez/Remove the manifest file from the transfer job.z--namezA unique identifier for the job. Referring to your source and destination is recommended. If left blank, the name is auto-generated upon submission of the job.z --descriptionzZAn optional description to help identify the job using details that don't fit in its name.z--source-agent-poolzgIf using a POSIX filesystem source, specify the ID of the agent pool associated with source filesystem.z--destination-agent-poolzqIf using a POSIX filesystem destination, specify the ID of the agent pool associated with destination filesystem.z--intermediate-storage-pathaAIf transferring between filesystems, specify the path to a folder in a Google Cloud Storage bucket (gs://example-bucket/example-folder) to use as intermediary storage. Recommended: Use an empty folder reserved for this transfer job to ensure transferred data doesn't interact with any of your existing Cloud Storage data.z--manifest-fileaPath to a .csv file containing a list of files to transfer from your source. For manifest files in Cloud Storage, specify the absolute path (e.g., `gs://mybucket/manifest.csv`). For manifest files stored in a source or destination POSIX file system, provide the relative path (e.g., `source://path/to/manfest.csv` or `destination://path/to/manifest.csv`). For manifest file formatting, see https://cloud.google.com/storage-transfer/docs/manifest.zREPLICATION OPTIONSz --replicationzEnable replication to automatically copy all new and existing objects from the source to the destination. Note: Objects deleted from the source bucket will not be deleted from the destination bucket. Please note that it is an event-driven transfer.ahEVENT STREAM Configure an event stream to transfer data whenever it is added or changed at your source, enabling you to act on the data in near real time. This event-driven transfer execution mode is available for transfers from Google Cloud Storage and Amazon S3. For formatting information, see https://cloud.google.com/sdk/gcloud/reference/topic/datetimes.z--event-stream-nameaSpecify an event stream that Storage Transfer Service can use to listen for when objects are created or updated. For Google Cloud Storage sources, specify a Cloud Pub/Sub subscription, using format "projects/yourproject/subscriptions/yoursubscription". For Amazon S3 sources, specify the Amazon Resource Name (ARN) of an Amazon Simple Queue Service (SQS) queue using format "arn:aws:sqs:region:account_id:queue_name".z--event-stream-startszSet when to start listening for events UTC using the %Y-%m-%dT%H:%M:%S%z datetime format (e.g., 2020-04-12T06:42:12+04:00). If not set, the job will start running and listening for events upon the successful submission of the create job command.z--event-stream-expireszSet when to stop listening for events UTC using the %Y-%m-%dT%H:%M:%S%z datetime format (e.g., 2020-04-12T06:42:12+04:00). If not set, the job will continue running and listening for events indefinitely.z--clear-event-streamzRemove the job's entire event stream configuration by clearing all scheduling all event stream flags. The job will no longer listen for events unless a new configuratin is specified.zSCHEDULE A job's schedule determines when and how often the job will run. For formatting information, see https://cloud.google.com/sdk/gcloud/reference/topic/datetimes.z--clear-schedulezRemove the job's entire schedule by clearing all scheduling flags. The job will no longer run unless an operation is manually started or a new schedule is specified.z --do-not-runzDisable default Transfer Service behavior of running job upon creation if no schedule is set. If this flag is specified, the job won't run until an operation is manually started or a schedule is added.z--schedule-startszSet when the job will start using the %Y-%m-%dT%H:%M:%S%z datetime format (e.g., 2020-04-12T06:42:12+04:00). If not set, the job will run upon the successful submission of the create job command unless the --do-not-run flag is included.)typer_z--schedule-repeats-everyzSet the frequency of the job using the absolute duration format (e.g., 1 month is p1m; 1 hour 30 minutes is 1h30m). If not set, the job will run once.z--schedule-repeats-untilabSet when the job will stop recurring using the %Y-%m-%dT%H:%M:%S%z datetime format (e.g., 2020-04-12T06:42:12+04:00). If specified, you must also include a value for the --schedule-repeats-every flag. If not specified, the job will continue to repeat as specified in its repeat-every field unless the job is manually disabled or you add this field later.aOBJECT CONDITIONS A set of conditions to determine which objects are transferred. For time-based object condition formatting tips, see https://cloud.google.com/sdk/gcloud/reference/topic/datetimes. Note: If you specify multiple conditions, objects must have at least one of the specified 'include' prefixes and all of the specified time conditions. If an object has an 'exclude' prefix, it will be excluded even if it matches other conditions.z--clear-include-prefixeszIRemove the list of object prefixes to include from the object conditions.z--clear-exclude-prefixeszIRemove the list of object prefixes to exclude from the object conditions.z(--clear-include-modified-before-absolutezDRemove the maximum modification datetime from the object conditions.z'--clear-include-modified-after-absolutezDRemove the minimum modification datetime from the object conditions.z(--clear-include-modified-before-relativezJRemove the maximum duration since modification from the object conditions.z'--clear-include-modified-after-relativezJRemove the minimum duration since modification from the object conditions.z--include-prefixesINCLUDED_PREFIXESzInclude only objects that start with the specified prefix(es). Separate multiple prefixes with commas, omitting spaces after the commas (e.g., --include-prefixes=foo,bar).)rtmetavarr_z--exclude-prefixesEXCLUDED_PREFIXESzExclude any objects that start with the prefix(es) entered. Separate multiple prefixes with commas, omitting spaces after the commas (e.g., --exclude-prefixes=foo,bar).z"--include-modified-before-absolutezInclude objects last modified before an absolute date/time. Ex. by specifying '2020-01-01', the transfer would include objects last modified before January 1, 2020. Use the %Y-%m-%dT%H:%M:%S%z datetime format.z!--include-modified-after-absolutezInclude objects last modified after an absolute date/time. Ex. by specifying '2020-01-01', the transfer would include objects last modified after January 1, 2020. Use the %Y-%m-%dT%H:%M:%S%z datetime format.z"--include-modified-before-relativea"Include objects that were modified before a relative date/time in the past. Ex. by specifying a duration of '10d', the transfer would include objects last modified *more than* 10 days before its start time. Use the absolute duration format (ex. 1m for 1 month; 1h30m for 1 hour 30 minutes).z!--include-modified-after-relativea!Include objects that were modified after a relative date/time in the past. Ex. by specifying a duration of '10d', the transfer would include objects last modified *less than* 10 days before its start time. Use the absolute duration format (ex. 1m for 1 month; 1h30m for 1 hour 30 minutes).zTRANSFER OPTIONSz--clear-delete-fromzRemove a specified deletion option from the transfer job. If this flag is specified, the transfer job won't delete any data from your source or destination.z--clear-preserve-metadatazGSkips preserving optional metadata fields of objects being transferred.z--clear-custom-storage-classz3Reverts to using destination default storage class.z--overwrite-whenc38# UHoRv M g7frirjrloptions rrnro@f\\rpaDetermine when destination objects are overwritten by source objects. Options include: - 'different' - Overwrites files with the same name if the contents are different (e.g., if etags or checksums don't match) - 'always' - Overwrite destination file whenever source file has the same name -- even if they're identical - 'never' - Never overwrite destination file when source file has the same namez --delete-fromc38# UHoRv M g7frirjrys rrnro= f\\ rpaBy default, transfer jobs won't delete any data from your source or destination. These options enable you to delete data if needed for your use case. Options include: - 'destination-if-unique' - Delete files from destination if they're not also at source. Use to sync destination to source (i.e., make destination match source exactly) - 'source-after-transfer' - Delete files from source after they're transferredz--preserve-metadatac38# UHoRv M g7frirj)rlfields rrnrosH2G2Grp)rqMETADATA_FIELDSzSpecify object metadata values that can optionally be preserved. Example: --preserve-metadata=storage-class,uid For more info, see: https://cloud.google.com/storage-transfer/docs/metadata-preservation z--custom-storage-classaSpecifies the storage class to set on objects being transferred to Cloud Storage buckets. If unspecified, the objects' storage class is set to the destination bucket default. Valid values are: - Any of the values listed in the Cloud Storage documentation: [Available storage classes](https://cloud.google.com/storage/docs/storage-classes#classes). - `preserve` - Preserves each object's original storage class. Only supported for transfers between Cloud Storage buckets. Custom storage class settings are ignored if the destination bucket is [Autoclass-enabled](https://cloud.google.com/storage/docs/autoclass). Objects transferred into Autoclass-enabled buckets are initially set to the `STANDARD` storage class.zwNOTIFICATION CONFIG A configuration for receiving notifications oftransfer operation status changes via Cloud Pub/Sub.z--clear-notification-configzfRemove the job's full notification configuration to no longer receive notifications via Cloud Pub/Sub.z --clear-notification-event-typesz4Remove the event types from the notification config.z--notification-pubsub-topicz%Pub/Sub topic used for notifications.z--notification-event-types)successr.aborted EVENT_TYPESa-Define which change of transfer operation status will trigger Pub/Sub notifications. Choices include 'success', 'failed', 'aborted'. To trigger notifications for all three status changes, you can leave this flag unspecified as long as you've specified a topic for the --notification-pubsub-topic flag.z--notification-payload-formatjsonnonezIf 'none', no transfer operation details are included with notifications. If 'json', a json representation of the relevant transfer operation is included in notification messages (e.g., to see errors after an operation fails).zLOGGING CONFIG Configure which transfer actions and action states are reported when logs are generated for this job. Logs can be viewed by running the following command: gcloud logging read "resource.type=storage_transfer_job"z--clear-log-configz%Remove the job's full logging config.z--enable-posix-transfer-logszSets whether to generate logs for transfers with a POSIX filesystem source. This setting will later be merged with other log configurations.z --log-actionsc38# UHoRv M g7frirjrys rrnros>I&Irp LOG_ACTIONSzDefine the transfer operation actions to report in logs. Separate multiple actions with commas, omitting spaces after the commas (e.g., --log-actions=find,copy).z--log-action-statesc38# UHoRv M g7frirjrys rrnrosCN&NrpLOG_ACTION_STATESzThe states in which the actions specified in --log-actions are logged. Separate multiple states with a comma, omitting the space after the comma (e.g., --log-action-states=succeeded,failed).zADDITIONAL OPTIONSz--source-endpointzFor transfers from S3-compatible sources, specify your storage system's endpoint. Check with your provider for formatting (ex. s3.us-east-1.amazonaws.com for Amazon S3).z--source-signing-regionzFor transfers from S3-compatible sources, specify a region for signing requests. You can leave this unspecified if your storage provider doesn't require a signing region.z--source-auth-methodc38# UHoRv M g7frirjrys rrnro,s; f\\ rpaIFor transfers from S3-compatible sources, choose a process for adding authentication information to S3 API requests. Refer to AWS's SigV4 (https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) and SigV2 (https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html) documentation for more information.z--source-list-apic38# UHoRv M g7frirjrys rrnro4s8f\\rpaZFor transfers from S3-compatible sources, choose the version of the S3 listing API for returning objects from the bucket. Refer to AWS's ListObjectsV2 (https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html) and ListObjects (https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html) documentation for more information.z--source-network-protocolc38# UHoRv M g7frirjrys rrnro=r{rpzeFor transfers from S3-compatible sources, choose the network protocol agents should use for this job.z--source-request-modelc38# UHoRv M g7frirjrys rrnroBr}rpa<For transfers from S3-compatible sources, choose which addressing style to use. Determines if the bucket name is in the hostname or part of the URL. For example, https://s3.region.amazonaws.com/bucket-name/key-name for path style and Ex. https://bucket-name.s3.region.amazonaws.com/key-name for virtual-hosted style.z--s3-cloudfront-domaina For transfers from S3, optionally route egress traffic through a CloudFront instance. Supply the endpoint of the CloudFront instance: https://example.cloudfront.net. See documentation (https://cloud.google.com/storage-transfer/docs/s3-cloudfront) for more information.z--clear-source-endpointzRemoves source endpoint.z--clear-source-signing-regionzRemoves source signing region.z--clear-source-auth-methodzRemoves source auth method.z--clear-source-list-apizRemoves source list API.z--clear-source-network-protocolz Removes source network protocol.z--clear-source-request-modelzRemoves source request model.z--clear-s3-cloudfront-domainzRemoves S3 CloudFront domain.zEXECUTION OPTIONSz --no-asynczFor jobs set to run upon creation, this flag blocks other tasks in your terminal until the job's initial, immediate transfer operation has completed. If not included, tasks will run asynchronously.N) SetSortArgsr`_SOURCE_HELP_TEXT_DESTINATION_HELP_TEXT add_groupsortedrrbrDatetimeParseDurationArgListrPrr5StoreTrueFalseActionr#r,rrFrKrY) ra is_update release_trackjob_informationreplication_group event_streamscheduleobject_conditionstransfer_optionsnotification_configlogging_configadditional_optionsexecution_optionss r setup_parserrs U EG '89  ,BC$$*;u$M/  <)<<5!6   2C D  7M N   <!>  # B!D  # B!D  ( G!I  + J!L   >!@   6!7  %& ( 12  <=# @A FG ((.C(D""  # !! N ", ;= *, >@  > @   N (  BD      % % ?@     ! )*      % % JK&& C' """# """# ""2# ""1# ""2# ""1#       ! 8 !9      ! 8 !9  *    % % .!/  )    % % .!/  *    ! .!/  )    ! .!/%%+=%O!!'"( !!#" !!& B"D @@@  = ==     H2GHH J "  # . / (( A ) $$%;%< $$* C%E""# 2#4"""   'G H ; #<""%v /#0## G $.  4 6$  - -     >I>> @ * +   CNCC E! A B'' 5(2!! 4"5 !! 4"5 !!; ;; F"G!!888 "!!!@@@ 2"3 !!= == 9":!! #" ##! '$)##' -$/##$ *$,##! '$)##) /$1##& ,$.##& ,$ (( E)3""# r)FN)__doc__ __future__rrrenumgooglecloudsdk.callioper&_POSIX_SOURCE_OR_DESTINATION_HELP_TEXT_HDFS_SOURCE_HELP_TEXTformatrrEnumrrrr#r,r5rFrKrPrYrbrr rrrs  '' /M'5 # & /1GH  & /0(( 24992     TYY DII &dii& dii dii 04990 . kr