(SrSSKJr SSKJr SSKJr SSKJr SSKrSSKrSSKrSSK r SSK r SSK r SSK J r SSKJr SS KJr SS KJr SS KJr SS KJr SS KJr SSKJr SSKJr SSKJr SSKJr SSKJr SSK J!r! SSK J"r" SSK J#r# SSK$J%r& SSK'J(r( SSK'J)r) SSK'J*r* SSK+J,r, SSK-J.r. SSK-J/r/ SSK0J1r1 SSK0J2r2 SSK0J3r3 SS K0J4r4 SS!K0J5r5 SS"K0J6r6 SS#K7J8r8 SS$K7J9r9 SS%K7J:r: SS&K7J;r; SS'K7JJ?r? SS*K>J@r@ SS+KAJBrB SS,KAJCrC SS-KAJDrD SS.KEJFrF SS/KEJGrG SS0KHJIrI SS1KHJJrJ S2rKS3\K-rLS4rMS5rNS6rOS7rPS8rQS9rRS:rSS;rTSrWS?rXS@rYSAR\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y/5r[SBr\0SC\?"SD5_SE\?"SF5_SG\?"SH5_SI\?"SJ5_SK\?"SL5_SM\?"SN5_SO\?"SP5_SQ\?"SR5_SS\?"ST5_SU\?"SV5_SW\?"SX5_SY\?"SZ5_S[\?"S\5_S]\?"S^5_S_\?"S`5_Sa\?"Sb5_Sc\?"Sd5_r]\^"\]R55Se\?"Se54Sf\?"Se54/-VVs0sHupX_M snnr`SgraSmShjrbSircSjrd"SkSl\5regs snnf)nzCImplementation of Unix-like cp command for cloud storage providers.)absolute_import)print_function)division)unicode_literalsN)encoding) gcs_json_api)Command)CommandArgument) ApiSelector)CommandException)LogPerformanceSummaryParams)CopyObjectsIterator)DestinationInfo)NameExpansionIterator)%NameExpansionIteratorDestinationTuple)SeekAheadNameExpansionIterator)ContainsWildcard)IsCloudSubdirPlaceholder)StorageUrlFromString)storage_v1_messages) cat_helper) copy_helper)parallelism_framework_util)GetCloudApiInstance)DEBUGLEVEL_DUMP_REQUESTS)NO_MAX)CreateCopyHelperOpts)GetSourceFieldsNeededForCopy)GZIP_ALL_FILES)ItemExistsError)Manifest)SkipUnsupportedObjectError)ConvertModeToBase8)+DeserializeFileAttributesFromObjectMetadata)InitializePreservePosixData)POSIXAttributes)'SerializeFileAttributesToObjectMetadata)ValidateFilePermissionAccess)GcloudStorageFlag)GcloudStorageMap)GetStreamFromFileUrl) StdinIterator)StdinIteratorCls)NormalizeStorageClass)RemoveCRLFFromString)CalculateThroughput)MakeHumanReadablezw gsutil cp [OPTION]... src_url dst_url gsutil cp [OPTION]... src_url... dst_url gsutil cp [OPTION]... -I dst_url z SYNOPSIS an DESCRIPTION The ``gsutil cp`` command allows you to copy data between your local file system and the cloud, within the cloud, and between cloud storage providers. For example, to upload all text files from the local directory to a bucket, you can run: gsutil cp *.txt gs://my-bucket You can also download data from a bucket. The following command downloads all text files from the top-level of a bucket to your current directory: gsutil cp gs://my-bucket/*.txt . You can use the ``-n`` option to prevent overwriting the content of existing files. The following example downloads text files from a bucket without clobbering the data in your directory: gsutil cp -n gs://my-bucket/*.txt . Use the ``-r`` option to copy an entire directory tree. For example, to upload the directory tree ``dir``: gsutil cp -r dir gs://my-bucket If you have a large number of files to transfer, you can perform a parallel multi-threaded/multi-processing copy using the top-level gsutil ``-m`` option (see "gsutil help options"): gsutil -m cp -r dir gs://my-bucket You can use the ``-I`` option with ``stdin`` to specify a list of URLs to copy, one per line. This allows you to use gsutil in a pipeline to upload or download objects as generated by a program: cat filelist | gsutil -m cp -I gs://my-bucket or: cat filelist | gsutil -m cp -I ./download_dir where the output of ``cat filelist`` is a list of files, cloud URLs, and wildcards of files and cloud URLs. NOTE: Shells like ``bash`` and ``zsh`` sometimes attempt to expand wildcards in ways that can be surprising. You may also encounter issues when attempting to copy files whose names contain wildcard characters. For more details about these issues, see `Wildcard behavior considerations `_. ah HOW NAMES ARE CONSTRUCTED The ``gsutil cp`` command attempts to name objects in ways that are consistent with the Linux ``cp`` command. This means that names are constructed depending on whether you're performing a recursive directory copy or copying individually-named objects, or whether you're copying to an existing or non-existent directory. When you perform recursive directory copies, object names are constructed to mirror the source directory structure starting at the point of recursive processing. For example, if ``dir1/dir2`` contains the file ``a/b/c``, then the following command creates the object ``gs://my-bucket/dir2/a/b/c``: gsutil cp -r dir1/dir2 gs://my-bucket In contrast, copying individually-named files results in objects named by the final path component of the source files. For example, assuming again that ``dir1/dir2`` contains ``a/b/c``, the following command creates the object ``gs://my-bucket/c``: gsutil cp dir1/dir2/** gs://my-bucket Note that in the above example, the '**' wildcard matches all names anywhere under ``dir``. The wildcard '*' matches names just one level deep. For more details, see `URI wildcards `_. The same rules apply for uploads and downloads: recursive copies of buckets and bucket subdirectories produce a mirrored filename structure, while copying individually or wildcard-named objects produce flatly-named files. In addition, the resulting names depend on whether the destination subdirectory exists. For example, if ``gs://my-bucket/subdir`` exists as a subdirectory, the following command creates the object ``gs://my-bucket/subdir/dir2/a/b/c``: gsutil cp -r dir1/dir2 gs://my-bucket/subdir In contrast, if ``gs://my-bucket/subdir`` does not exist, this same ``gsutil cp`` command creates the object ``gs://my-bucket/subdir/a/b/c``. NOTE: The `Google Cloud Platform Console `_ creates folders by creating "placeholder" objects that end with a "/" character. gsutil skips these objects when downloading from the cloud to the local file system, because creating a file that ends with a "/" is not allowed on Linux and macOS. We recommend that you only create objects that end with "/" if you don't intend to download such objects using gsutil. a COPYING TO/FROM SUBDIRECTORIES; DISTRIBUTING TRANSFERS ACROSS MACHINES You can use gsutil to copy to and from subdirectories by using a command like this: gsutil cp -r dir gs://my-bucket/data This causes ``dir`` and all of its files and nested subdirectories to be copied under the specified destination, resulting in objects with names like ``gs://my-bucket/data/dir/a/b/c``. Similarly, you can download from bucket subdirectories using the following command: gsutil cp -r gs://my-bucket/data dir This causes everything nested under ``gs://my-bucket/data`` to be downloaded into ``dir``, resulting in files with names like ``dir/data/a/b/c``. Copying subdirectories is useful if you want to add data to an existing bucket directory structure over time. It's also useful if you want to parallelize uploads and downloads across multiple machines (potentially reducing overall transfer time compared with running ``gsutil -m cp`` on one machine). For example, if your bucket contains this structure: gs://my-bucket/data/result_set_01/ gs://my-bucket/data/result_set_02/ ... gs://my-bucket/data/result_set_99/ you can perform concurrent downloads across 3 machines by running these commands on each machine, respectively: gsutil -m cp -r gs://my-bucket/data/result_set_[0-3]* dir gsutil -m cp -r gs://my-bucket/data/result_set_[4-6]* dir gsutil -m cp -r gs://my-bucket/data/result_set_[7-9]* dir Note that ``dir`` could be a local directory on each machine, or a directory mounted off of a shared file server. The performance of the latter depends on several factors, so we recommend experimenting to find out what works best for your computing environment. a COPYING IN THE CLOUD AND METADATA PRESERVATION If both the source and destination URL are cloud URLs from the same provider, gsutil copies data "in the cloud" (without downloading to and uploading from the machine where you run gsutil). In addition to the performance and cost advantages of doing this, copying in the cloud preserves metadata such as ``Content-Type`` and ``Cache-Control``. In contrast, when you download data from the cloud, it ends up in a file with no associated metadata, unless you have some way to keep or re-create that metadata. Copies spanning locations and/or storage classes cause data to be rewritten in the cloud, which may take some time (but is still faster than downloading and re-uploading). Such operations can be resumed with the same command if they are interrupted, so long as the command parameters are identical. Note that by default, the gsutil ``cp`` command does not copy the object ACL to the new object, and instead uses the default bucket ACL (see "gsutil help defacl"). You can override this behavior with the ``-p`` option. When copying in the cloud, if the destination bucket has Object Versioning enabled, by default ``gsutil cp`` copies only live versions of the source object. For example, the following command causes only the single live version of ``gs://bucket1/obj`` to be copied to ``gs://bucket2``, even if there are noncurrent versions of ``gs://bucket1/obj``: gsutil cp gs://bucket1/obj gs://bucket2 To also copy noncurrent versions, use the ``-A`` flag: gsutil cp -A gs://bucket1/obj gs://bucket2 The top-level gsutil ``-m`` flag is not allowed when using the ``cp -A`` flag. z CHECKSUM VALIDATION gsutil automatically performs checksum validation for copies to and from Cloud Storage. For more information, see `Hashes and ETags `_. a RETRY HANDLING The ``cp`` command retries when failures occur, but if enough failures happen during a particular copy or delete operation, or if a failure isn't retryable, the ``cp`` command skips that object and moves on. If any failures were not successfully retried by the end of the copy run, the ``cp`` command reports the number of failures and exits with a non-zero status. For details about gsutil's overall retry handling, see `Retry strategy `_. a RESUMABLE TRANSFERS gsutil automatically resumes interrupted downloads and interrupted `resumable uploads `_, except when performing streaming transfers. In the case of an interrupted download, a partially downloaded temporary file is visible in the destination directory with the suffix ``_.gstmp`` in its name. Upon completion, the original file is deleted and replaced with the downloaded contents. Resumable transfers store state information in files under ~/.gsutil, named by the destination object or file. See "gsutil help prod" for details on using resumable transfers in production. a STREAMING TRANSFERS Use '-' in place of src_url or dst_url to perform a `streaming transfer `_. Streaming uploads using the `JSON API `_ are buffered in memory part-way back into the file and can thus sometimes resume in the event of network or service problems. gsutil does not support resuming streaming uploads using the XML API or resuming streaming downloads for either JSON or XML. If you have a large amount of data to transfer in these cases, we recommend that you write the data to a local file and copy that file rather than streaming it. a< SLICED OBJECT DOWNLOADS gsutil can automatically use ranged ``GET`` requests to perform downloads in parallel for large files being downloaded from Cloud Storage. See `sliced object download documentation `_ for a complete discussion. a PARALLEL COMPOSITE UPLOADS gsutil can automatically use `object composition `_ to perform uploads in parallel for large, local files being uploaded to Cloud Storage. See the `parallel composite uploads documentation `_ for a complete discussion. am CHANGING TEMP DIRECTORIES gsutil writes data to a temporary directory in several cases: - when compressing data to be uploaded (see the ``-z`` and ``-Z`` options) - when decompressing data being downloaded (for example, when the data has ``Content-Encoding:gzip`` as a result of being uploaded using gsutil cp -z or gsutil cp -Z) - when running integration tests using the gsutil test command In these cases, it's possible the temporary file location on your system that gsutil selects by default may not have enough space. If gsutil runs out of space during one of these operations (for example, raising "CommandException: Inadequate temp space available to compress " during a ``gsutil cp -z`` operation), you can change where it writes these temp files by setting the TMPDIR environment variable. On Linux and macOS, you can set the variable as follows: TMPDIR=/some/directory gsutil cp ... You can also add this line to your ~/.bashrc file and restart the shell before running gsutil: export TMPDIR=/some/directory On Windows 7, you can change the TMPDIR environment variable from Start -> Computer -> System -> Advanced System Settings -> Environment Variables. You need to reboot after making this change for it to take effect. Rebooting is not necessary after running the export command on Linux and macOS. a SYNCHRONIZING OVER OS-SPECIFIC FILE TYPES (SUCH AS SYMLINKS AND DEVICES) Please see the section about OS-specific file types in "gsutil help rsync". While that section refers to the ``rsync`` command, analogous points apply to the ``cp`` command. aT2 OPTIONS -a predef_acl Applies the specific predefined ACL to uploaded objects. See "gsutil help acls" for further details. -A Copy all source versions from a source bucket or folder. If not set, only the live version of each source object is copied. NOTE: This option is only useful when the destination bucket has Object Versioning enabled. Additionally, the generation numbers of copied versions do not necessarily match the order of the original generation numbers. -c If an error occurs, continue attempting to copy the remaining files. If any copies are unsuccessful, gsutil's exit status is non-zero, even if this flag is set. This option is implicitly set when running ``gsutil -m cp...``. NOTE: ``-c`` only applies to the actual copying operation. If an error, such as ``invalid Unicode file name``, occurs while iterating over the files in the local directory, gsutil prints an error message and aborts. -D Copy in "daisy chain" mode, which means copying between two buckets by first downloading to the machine where gsutil is run, then uploading to the destination bucket. The default mode is a "copy in the cloud," where data is copied between two buckets without uploading or downloading. During a "copy in the cloud," a source composite object remains composite at its destination. However, you can use "daisy chain" mode to change a composite object into a non-composite object. For example: gsutil cp -D gs://bucket/obj gs://bucket/obj_tmp gsutil mv gs://bucket/obj_tmp gs://bucket/obj NOTE: "Daisy chain" mode is automatically used when copying between providers: for example, when copying data from Cloud Storage to another provider. -e Exclude symlinks. When specified, symbolic links are not copied. -I Use ``stdin`` to specify a list of files or objects to copy. You can use gsutil in a pipeline to upload or download objects as generated by a program. For example: cat filelist | gsutil -m cp -I gs://my-bucket where the output of ``cat filelist`` is a one-per-line list of files, cloud URLs, and wildcards of files and cloud URLs. -j Applies gzip transport encoding to any file upload whose extension matches the ``-j`` extension list. This is useful when uploading files with compressible content such as .js, .css, or .html files. This also saves network bandwidth while leaving the data uncompressed in Cloud Storage. When you specify the ``-j`` option, files being uploaded are compressed in-memory and on-the-wire only. Both the local files and Cloud Storage objects remain uncompressed. The uploaded objects retain the ``Content-Type`` and name of the original files. Note that if you want to use the ``-m`` `top-level option `_ to parallelize copies along with the ``-j/-J`` options, your performance may be bottlenecked by the "max_upload_compression_buffer_size" boto config option, which is set to 2 GiB by default. You can change this compression buffer size to a higher limit. For example: gsutil -o "GSUtil:max_upload_compression_buffer_size=8G" \ -m cp -j html,txt -r /local/source/dir gs://bucket/path -J Applies gzip transport encoding to file uploads. This option works like the ``-j`` option described above, but it applies to all uploaded files, regardless of extension. CAUTION: If some of the source files don't compress well, such as binary data, using this option may result in longer uploads. -L Outputs a manifest log file with detailed information about each item that was copied. This manifest contains the following information for each item: - Source path. - Destination path. - Source size. - Bytes transferred. - MD5 hash. - Transfer start time and date in UTC and ISO 8601 format. - Transfer completion time and date in UTC and ISO 8601 format. - Upload id, if a resumable upload was performed. - Final result of the attempted transfer, either success or failure. - Failure details, if any. If the log file already exists, gsutil uses the file as an input to the copy process, and appends log items to the existing file. Objects that are marked in the existing log file as having been successfully copied or skipped are ignored. Objects without entries are copied and ones previously marked as unsuccessful are retried. This option can be used in conjunction with the ``-c`` option to build a script that copies a large number of objects reliably, using a bash script like the following: until gsutil cp -c -L cp.log -r ./dir gs://bucket; do sleep 1 done The -c option enables copying to continue after failures occur, and the -L option allows gsutil to pick up where it left off without duplicating work. The loop continues running as long as gsutil exits with a non-zero status. A non-zero status indicates there was at least one failure during the copy operation. NOTE: If you are synchronizing the contents of a directory and a bucket, or the contents of two buckets, see "gsutil help rsync". -n No-clobber. When specified, existing files or objects at the destination are not replaced. Any items that are skipped by this option are reported as skipped. gsutil performs an additional GET request to check if an item exists before attempting to upload the data. This saves gsutil from retransmitting data, but the additional HTTP requests may make small object transfers slower and more expensive. -p Preserves ACLs when copying in the cloud. Note that this option has performance and cost implications only when using the XML API, as the XML API requires separate HTTP calls for interacting with ACLs. You can mitigate this performance issue using ``gsutil -m cp`` to perform parallel copying. Note that this option only works if you have OWNER access to all objects that are copied. If you want all objects in the destination bucket to end up with the same ACL, you can avoid these performance issues by setting a default object ACL on that bucket instead of using ``cp -p``. See "gsutil help defacl". Note that it's not valid to specify both the ``-a`` and ``-p`` options together. -P Enables POSIX attributes to be preserved when objects are copied. ``gsutil cp`` copies fields provided by ``stat``. These fields are the user ID of the owner, the group ID of the owning group, the mode or permissions of the file, and the access and modification time of the file. For downloads, these attributes are only set if the source objects were uploaded with this flag enabled. On Windows, this flag only sets and restores access time and modification time. This is because Windows doesn't support POSIX uid/gid/mode. -R, -r The ``-R`` and ``-r`` options are synonymous. They enable directories, buckets, and bucket subdirectories to be copied recursively. If you don't use this option for an upload, gsutil copies objects it finds and skips directories. Similarly, if you don't specify this option for a download, gsutil copies objects at the current bucket directory level and skips subdirectories. -s Specifies the storage class of the destination object. If not specified, the default storage class of the destination bucket is used. This option is not valid for copying to non-cloud destinations. -U Skips objects with unsupported object types instead of failing. Unsupported object types include Amazon S3 objects in the GLACIER storage class. -v Prints the version-specific URL for each uploaded object. You can use these URLs to safely make concurrent upload requests, because Cloud Storage refuses to perform an update if the current object version doesn't match the version-specific URL. See `generation numbers `_ for more details. -z Applies gzip content-encoding to any file upload whose extension matches the ``-z`` extension list. This is useful when uploading files with compressible content such as .js, .css, or .html files, because it reduces network bandwidth and storage sizes. This can both improve performance and reduce costs. When you specify the ``-z`` option, the data from your files is compressed before it is uploaded, but your actual files are left uncompressed on the local disk. The uploaded objects retain the ``Content-Type`` and name of the original files, but have their ``Content-Encoding`` metadata set to ``gzip`` to indicate that the object data stored are compressed on the Cloud Storage servers and have their ``Cache-Control`` metadata set to ``no-transform``. For example, the following command: gsutil cp -z html \ cattypes.html tabby.jpeg gs://mycats does the following: - The ``cp`` command uploads the files ``cattypes.html`` and ``tabby.jpeg`` to the bucket ``gs://mycats``. - Based on the file extensions, gsutil sets the ``Content-Type`` of ``cattypes.html`` to ``text/html`` and ``tabby.jpeg`` to ``image/jpeg``. - The ``-z`` option compresses the data in the file ``cattypes.html``. - The ``-z`` option also sets the ``Content-Encoding`` for ``cattypes.html`` to ``gzip`` and the ``Cache-Control`` for ``cattypes.html`` to ``no-transform``. Because the ``-z/-Z`` options compress data prior to upload, they are not subject to the same compression buffer bottleneck that can affect the ``-j/-J`` options. Note that if you download an object with ``Content-Encoding:gzip``, gsutil decompresses the content before writing the local file. -Z Applies gzip content-encoding to file uploads. This option works like the ``-z`` option described above, but it applies to all uploaded files, regardless of extension. CAUTION: If some of the source files don't compress well, such as binary data, using this option may result in files taking up more space in the cloud than they would if left uncompressed. --stet If the STET binary can be found in boto or PATH, cp will use the split-trust encryption tool for end-to-end encryption. z za:AcDeIL:MNnpPrRs:tUvz:Zj:J-Az--all-versions-az--predefined-acl-cz--continue-on-error-Dz --daisy-chain-ez--ignore-symlinks-Iz--read-paths-from-stdin-Jz--gzip-in-flight-all-jz--gzip-in-flight-Lz--manifest-path-nz --no-clobber-Pz--preserve-posix-pz--preserve-acl-sz--storage-class-vz--print-created-message-Zz--gzip-local-all-zz --gzip-local-Uz--skip-unsupported-r-RcSn[U5Hunup4US:XdMUn O Ub1UWSnXS[RRXU54X'gg)aLGcloud uses camel-case predefined/canned ACLs, and gsutil uses snake-case. The camel-case-snake-case difference is related to gcloud primarily using JSON API rather than the XML API. Predefined ACLs are also called "canned ACLs". Args: sub_opts: List of pairs representing flag keys and values, e.g. [('a', 'public-read')] Nr3r) enumerater+FULL_PREDEFINED_ACL_XML_TO_JSON_TRANSLATIONget)sub_optspredefined_acl_idxik_old_predefined_acls $platform/gsutil/gslib/commands/cp.py'ShimTranslatePredefinedAclSubOptForCopyrQstX&ia!Dy '#!!Q;q>KKOO)?@HK$c:URUUURS9 g)N) thread_statepreserve_posix)CopyFuncpreserve_posix_attrs)clsargsrTs rP_CopyFuncWrapperrZs!,,t(!668rRcURR[U55 U=RS- slURR S[ R "55 g)9Simple exception handler to allow post-completion status.rFz* Encountered exception while copying: %s N)loggererrorstrop_failure_countdebug traceback format_excrXes rP_CopyExceptionHandlerrfsJ**3q6!**C'')+rRcLURR[U55 g)r\N)r]r^r_rds rP_RmExceptionHandlerrhs**3q6rRc^\rSrSrSr\R "SS/\S\\ SSS\ R\ R/\ RS S /\ R"5/S 9 r\R "SS/S S \0S9rU4SjrSSjrSrSrSrSrU=r$) CpCommandia2Implementation of gsutil cp command. Note that CpCommand is run for both gsutil cp and gsutil mv. The latter happens by MvCommand calling CpCommand and passing the hidden (undocumented) -M option. This allows the copy and remove needed for each mv to run together (rather than first running all the cp's and then all the rm's, as we originally had implemented), which in turn avoids the following problem with removing the wrong objects: starting with a bucket containing only the object gs://bucket/obj, say the user does: gsutil mv gs://bucket/* gs://bucket/d.txt If we ran all the cp's and then all the rm's and we didn't expand the wildcard first, the cp command would first copy gs://bucket/obj to gs://bucket/d.txt, and the rm command would then remove that object. In the implementation prior to gsutil release 3.12 we avoided this by building a list of objects to process and then running the copies and then the removes; but building the list up front limits scalability (compared with the current approach of processing the bucket listing iterator on the fly). cpcopyrFTFrstetztestcallbackfile=) command_name_aliasesusage_synopsismin_argsmax_argssupported_sub_args file_url_okprovider_url_okurls_start_arggs_api_supportgs_default_apisupported_private_argsargparse_arguments command_helpzCopy files and objects) help_namehelp_name_aliases help_typehelp_one_line_summary help_textsubcommand_help_textc>URRS5 [UR5 [ SS/[ S9n[ TU]U5$)NzUnlike pure gsutil, this shim won't run composite uploads and sliced downloads in parallel by default. Use the -m flag to enable parallelism (i.e. "gsutil -m cp ...").storagerk)gcloud_commandflag_map)r]warnrQrJr*CP_SHIM_FLAG_MAPsuperget_gcloud_storage_args)selfgcloud_storage_map __class__s rPr!CpCommand.get_gcloud_storage_argssQKK 23,DMM:)!4(! 7 *+= >>rRcj[XS9n[R"5nUR(aSnO URnUR nUR nURn URn UR5(a)UR5(a[SU<SU<S35eU(a5UR5(a UR5(a [S5eUR(a5UR5(a UR5(a [S5eU (a,[R"UR UR"U5 [%U5(agUR&(a+UR(R+UR,5(agUR(aUR(aS UlUR R5(aj[0R2R5UR R65(d2U (a+[0R8"UR R65 [R@"UUU U URBUR UR"UR.US 9 n [RD"X|5n [RF"X5 [RH"X5(a[U<S U<S U <S 35eU R5(a(U RK5(a[U<SU <S35eU R5(dURL(a[SU -5eSn URN(a/[PRR"[TRVURN5n UR5(aU(aU (d[TRV"5n [0RX"UR65u n nnnnnnn[[U5n[]UUUUUS9n[TRVR_/S9n[aUUUS 9 UU l1U (aU R5(a[eXR,5nURfRhn[kUR,URlURnUS9unnU(a6U(d/[pRr"5RuU5 [S5eSnUR&(a0UR(RwUR,U R,5 UR.(GaUR R6(GaU R5(a[0R2RyUR R65n[0R2R{U[0R2RyU R65/5R}U5(d^UR~RSU<SU<S35 UR&(a(UR(RUR,SSS5 g[R"UR~UU UU[U S URUR(URURUURS9unnnnUR&(aUU(a'UR(RUR,SU5 UR(RUR,US5 UR(aUR~RSU5 UR(aUR~RSU5 UR5(a;URURUR6URURS 9 O [0R"UR65 UR U=RU- sl]SSS5 g![:a*n U R<[<R>:waeSn A GNSn A ff=f![a\ S!U -nUR~RU5 UR&(a(UR(RUR,SSU5 N[a}n S"UR,<S#U R<3nUR~RU5 UR&(a(UR(RUR,SSU5 Sn A GNHSn A f[Ra/n UR~RSU<S$U <S%35 Sn A GNSn A f[Gaon UR(az[R"U 5(a_S&U -nUR~RU5 UR&(a(UR(RUR,SSU5 Sn A GN"UR(aS'U<S([U 5<3nU=RS)- slYUR~RU5 UR&(a1UR(RUR,SS*[U55 Sn A GNUR&(a1UR(RUR,SS*[U 55 eSn A ff=f!,(df  g=f)+z@Worker function for performing the actual copy (and rm, for mv).)rTmvzThe z3 command does not allow provider-only source URLs ()z/Cannot preserve POSIX attributes with a stream.z8Cannot upload from a stream when using gsutil -m option.NT)rUz: "z" and "z" are the same file - abort.z: a version-specific URL (z2) cannot be the destination for gsutil cp - abort.z>)AA 2 2 4 4  W  '++--'2B2B2D2D N OO G$5$5$7$7G>!?#o-k.==KM#2G--//? ..0k    ) )d/0B0B4?OO4?OO59;jeS $$S) CD Dc-  & &   !7!79K9KL  " " "  & & 2 2 2w7H7H7J7J GGOO$4$@$@$L$LM ww!! rwww':':;#  :i ! ++  I' ( * * MM # #&&6F H .9.E.E ++     +,,==((NN'==/"+a J  & &  --  K22E3 ?  6 68I4P  # #  3J  $ $ );7  ! ! # #  ! !+"9"9"-"9"9-8-C-C+6+=+= " ? ))K++ ,  ""&77" Q 77ell "  #t L,w6g kkw  & &  6 667K %L((!*<*<>g kkw  & &  6 667K  / / kk G    % %  0 0 3 3,w6 !  ( ( -- ! !+"8"8!VW M  ! ! !,3SV< " '"  ( ( -- ! !+"8"8!W"6w"? A  ( ( -- ! !+"8"8!Wc!f M #: ss7*aE0a=C9a='l$ a:a55a:=A#l!" l!+A2e##l!:$f$$l!2Bl=BlAll!$ l2c## [R"5n[X5GHupE[R"UURUR UR S9upg[[URURUR URUUR=(d URUR URURUR=(d UR [#UR%5UR&UR(UR*URUR,S9S9 [/Xg55nUR0=(d UR35UlUR4=(d UR%5UlUR6R9UR:5 [<R>"UR@U5Ul Uv GM g7f)N)r])rU delete_sourcefile_size_will_change) project_id all_versionsignore_symlinksrbucket_listing_fields)!rrzipExpandUrlToSingleBlrrrr]rrrrarrrexclude_symlinksrrrrskip_unsupported_objects preserve_aclrWrr has_file_dstr has_cloud_dstprovider_typesaddr itertoolschaincombined_src_urls) rsrc_url_strs_iter dst_url_strsr src_url_str dst_url_strrr!name_expansion_iterator_dst_tuples rP/_ConstructNameExpansionIteratorDstTupleIterator9CpCommand._ConstructNameExpansionIteratorDstTupleIterators"446$'(9$H 4  * *;+/??+/??26++ ?/k +P jjkkoo&&E*:*E*E,,"33!%!7!7":!%!9!9$@((*";;"//!%!:!: 0 ; ;(, %7 8& + C)+E',++F{/D/D/Fd--I1G1G1Id k001(t/E/E/: N>N " " 9: :~~'')t<-1  ! !$ ' 5 5diinAK6MM,, TYY1 OPP'()l TYY! LMMiin%lIIbM?LDDD%D2 <<  ($$ #'"@"@%)! #A##M >>-">@  0 0:    **  $ $ &   " " A&6&A&A((__// $  /1;;=DODJCL  JJ&$"&"8"88#6 8  KK3224yy{H&3D"5 $$d&=&=#?D&&((22 $ < <22))'33D//02 zz--  % % *  I  ( ($*A*A d99 : < //!33j 3396'+'<'<4:4M NN rRcSnSUlSnSUlSnSnSnSnSnSUlSnSUlSUlSUlSn Sn Sn Sn Sn SnSUlSUlUR(GaURGHunnUS:Xa UnSUlUS:XaSUlUS:Xa SUlM2US:XaSnM<US:Xa SUlMKUS:XaUn MUUS :XaSnM_US :Xa3Sn URS 5Vs/sHnUR5PM n nMUS :Xa Sn [n MUS :XaSn[U5UlMUS:XaSnMUS:XaSnMUS:XaSnMUS:XaSUl[5 MUS:XdUS:Xa SUlGMUS:Xa[U5nGM#US:Xa SUlGM3US:XaSnGM>US:Xa4Sn URS 5Vs/sHnUR5PM n nGMxUS:Xa Sn [n GMUS:XdGMSUlGM U(aU(a [!S5eUR(aUR"(a [!S5eU (aU (a [!S5eU (a$U (aU (a [!S5e[!S5eU =(d U UlXl[)UUUUUUUUUR U US9 $s snfs snf) NFr3Tr2r4r5r6z--testcallbackfiler7r9,r8r:z-Mr;r=r<rCrDr>rBr?rAr@z--stetz:Specifying both the -p and -a options together is invalid.zThe gsutil -m option is not supported with the cp -A flag, to ensure that object version ordering is preserved. Please re-run the command without the -m option.z@Specifying both the -j/-J and -z/-Z options together is invalid.z:Specifying both the -j and -J options together is invalid.z:Specifying both the -z and -Z options together is invalid.) rrr,r)rrr canned_aclrtest_callback_filer)rrrWcannedrrrrrJsplitstriprr!r%rr.r rrrr)rrrr,r)rrrr@r gzip_local gzip_arg_exts gzip_arg_allrAroaxs rPr%CpCommand._ParseOptssJ"DJ#DK ILL %DJDKD$)D!LJMLDMDM }}}--$!Q 9*$+ 9"$  9#'$ $Y+ $Y"&$  & & !  $Y!%  $Y,./ggcl;l1779l-;- $Y,', $Y,"1+$- $Y * $Y* $Y, $Y&*$ # % ' $Y!t)%)$ " $Y4Q7  $Y*.$ ' $Y) $Y*./ggcl;l1779l-;- $Y*', (]$-o r  F HH T55  / 00  L NN  HJ J HJ J"2lDN$ 1!!!%!>!>-- / /w<<rs; J&%'  %!2(,5406F?.62W"#2<:(8@23,>5N>2J?328147653  1f0d'R#J   !$ #>d Lkk!$##",  , - . / 1 2 O ,   / 0   5 6  2 3 . / - . N + . / , - - . 5 6 . /  N +!" 0 1#*1779: d #$t->t-D&EFGGTQADG @08 + f /f /csI,