)!VSrSSKJr SSKJr SSKJr SSKJr SSKJr SSKJ r SSKJ r SS K J r SSK J r SSKJ r SS KJr SS KJr SS KJr /S Qr\R."\R0R25\R4"SSSS9\R6"SS\R85555r\R."\R0R<5"SS\55r\R."\R0R@5"SS\55r!SSSS.\l"g)zR@5SS9 [2RB"U5 [RD"US SS[RF-S9 [2RH"US 5 URRK[LRN5 [2RP"USSS9 [2RR"US[2RT5 [2RV"US[2RX5 [(RZ"US SSS S9 URSSSSS9 g)NT)no_httpimport)operation_typez --descriptionz2Specifies a text description of the machine image.)helpzmachine image'sz machine imagez an import) operationz--osFz5Specifies the OS of the machine image being imported.)requiredchoicesrz>The zone in which to perform the import of the machine image. ) explanationzmachine image importzyhttps://cloud.google.com/nat/docs/gce-example#create-nat and https://cloud.google.com/vpc/docs/private-access-options#pga)docs_urlayHowever, if neither `--scopes` nor `--no-scopes` are specified and the project has no default service account, then the machine image is imported with no scopes. Note that the level of access that a service account has is determined by a combination of access scopes and IAM roles so you must configure both access scopes and IAM roles for the service account to work properly.r)extra_scopes_helprresourcez--cmd-deprecated store_trueaE The command you're using is deprecated and will be removed by December 31, 2025. We recommend using `gcloud compute migration image-imports` instead. See our official documentation for more information. https://cloud.google.com/migrate/virtual-machines/docs/5.0/migrate/image_import. )actionrr)._GetComputeApiHolderclientmessages display_info AddFormatmachine_image_flagsDEFAULT_LIST_FORMATMakeMachineImageArgrMACHINE_IMAGE_ARG AddArgument add_argumentr AddStorageLocationFlagAddGuestFlushFlagAddNoRestartOnFailureArgs AddTagsArgsAddCanIpForwardArgsAddNetworkArgsAddNetworkTierArgsinstances_flagsAddMachineTypeArgsAddCustomMachineTypeArgsr AddCreateLabelsFlagsrAddCommonDaisyArgsAddOVFSourceUriArgrAddGuestOsFeaturesArgForImportsortedr OS_CHOICES_INSTANCE_IMPORT_BETA AddByolArg AddZoneFlagZONE_PROPERTY_EXPLANATIONAddGuestEnvironmentArgAddCacheUpdaterrInstancesCompleterAddNoAddressArgAddComputeServiceAccountArg(IMPORT_ROLES_FOR_COMPUTE_SERVICE_ACCOUNTAddCloudBuildServiceAccountArg+IMPORT_ROLES_FOR_CLOUDBUILD_SERVICE_ACCOUNTAddServiceAccountAndScopeArgs)clsparsercompute_holderr%s ,lib/surface/compute/machine_images/import.pyArgs Import.Args5sr--d-;N$$--H !!"5"I"IJ2FFHF (((I  AC   ):; FO411&9##F+++F3&&v.**62&&v.,,V4$$V,""6[A""6*..v@ zAAB D F 6" T  ) )* + &&v? '' (E(EF O Q ++&<<>..?? 11    "   cL[R"UR5U5$N)rComputeApiHolder ReleaseTrack)rJrs rMr#Import._GetComputeApiHolders  ( ()9)9);W EErPc^[R"U5 [R"U5 [R"X5 [R "U5 [R "UR5Ulg![Ra [R"SS5ef=f)Nz source-uriz;must be a path to an object or a directory in Cloud Storage) r5ValidateNicFlagsValidateNetworkTierArgsr ValidateZone"ValidateServiceAccountAndScopeArgs MakeGcsUri source_urir UnknownCollectionExceptionrInvalidArgumentException)selfargscompute_clients rM _ValidateArgsImport._ValidateArgss$$T*++D1T266t<I#..t?do  / /I  / /  G IIIs %B,B,cLUR5nURnURX5 [R"S5 [ R "U[UR5(a(UR5RR5OSURS9$)NzeImporting OVF. This may take 40 minutes for smaller OVFs and up to a couple of hours for larger OVFs.)r` output_filter release_trackr%) r#r$rbr rrRunMachineImageOVFImportBuild_OUTPUT_FILTERrTidlowerr%)r_r`rLras rMRun Import.Runs..0N#**Nt,KK?@  4 4 $++--((*--33537((  **rPN)F) __name__ __module__ __qualname____firstlineno____doc__ classmethodrNr#rbrk__static_attributes__rmrPrMrr#s= =PPdFF I*rPrc6^\rSrSrSr\U4Sj5rSrU=r$) ImportBetaz=Import a machine image into Compute Engine from OVF for Beta.cX>[[U] U5 [R"U5 grR)superrvrNrAddExtraCommonDaisyArgsrJrK __class__s rMrNImportBeta.Argss  *c'''/rPrm rnrorprqrrrsrNrt __classcell__r|s@rMrvrvsE00rPrvc6^\rSrSrSr\U4Sj5rSrU=r$) ImportAlphaz>Import a machine image into Compute Engine from OVF for Alpha.cX>[[U] U5 [R"U5 grR)ryrrNrrzr{s rMrNImportAlpha.Argss  +s (''/rPrmr~rs@rMrrsF00rPrzOCreate a Compute Engine machine image from virtual appliance in OVA/OVF format.a *{command}* creates Compute Engine machine image from virtual appliance in OVA/OVF format. Importing OVF involves: * Unpacking OVF package (if in OVA format) to Cloud Storage. * Import disks from OVF to Compute Engine. * Translate the boot disk to make it bootable in Compute Engine. * Create a machine image using OVF metadata and imported disks. Virtual instances, images, machine images, and disks in Compute engine and files stored on Cloud Storage incur charges. See [](https://cloud.google.com/compute/docs/images/importing-virtual-disks#resource_cleanup). z To import an OVF package from Cloud Storage into a machine image named `my-machine-image`, run: $ {command} my-machine-image --source-uri=gs://my-bucket/my-dir )brief DESCRIPTIONEXAMPLESN)#rrgooglecloudsdk.api_lib.computerrrgooglecloudsdk.callioperr"googlecloudsdk.command_lib.computerr )googlecloudsdk.command_lib.compute.imagesr ,googlecloudsdk.command_lib.compute.instancesr51googlecloudsdk.command_lib.compute.machine_imagesr($googlecloudsdk.command_lib.util.argsr googlecloudsdk.corer r rh ReleaseTracksrTGA DeprecateDefaultUniverseOnly CreateCommandrBETArvALPHAr detailed_helprmrPrMrs C866(.94@QZ<#)ND%%(() >  > t*T  t* *t*nD%%**+00,0D%%++,0&0-0   'rP