;RSrSSKrSSKJr SSKJr SrS-SjrS-SjrS-SjrS-S jr S-S jr S-S jr S-S jr S-S jr S-SjrS.SjrS/SjrSrSrSrSrSrSrSrSrSrSrSrSrSrSrSrS r S!r!S"r"S#r#S$r$S%r%S&r&S'r'S(r(S-S)jr)S0S*jr*S-S+jr+S-S,jr,g)1z#Flags for the deploy command group.N) arg_parsers)baseaw The location of the source that contains skaffold.yaml. The location can be a directory on a local disk or a gzipped archive file (.tar.gz) in Google Cloud Storage. If the source is a local directory, this command skips the files specified in the --ignore-file. If --ignore-file is not specified, use.gcloudignore file. If a .gcloudignore file is absent and a .gitignore file is present in the local source directory, gcloud will use a generated Git-compatible .gcloudignore file that respects your .gitignored files. The global .gitignore is not respected. For more information on .gcloudignore, see gcloud topic gcloudignore. c&URSUSS9 g)zAAdds a Google Cloud Storage directory flag for staging the build.z--gcs-source-staging-dirzA directory in Google Cloud Storage to copy the source used for staging the build. If the specified bucket does not exist, Cloud Deploy will create one. If you don't set this field, ```gs://[DELIVERY_PIPELINE_ID]_clouddeploy/source``` is used.hiddenhelpN add_argumentparserrs .lib/googlecloudsdk/command_lib/deploy/flags.pyAddGcsSourceStagingDirFlagrs!  J  c&URSUSS9 g)zAdds an ignore file flag.z --ignore-filezEOverride the `.gcloudignore` file and use the specified file instead.rNr r s r AddIgnoreFileFlagr,s    rc&URSUSS9 g)Adds to-target flag. --to-targetz8Specifies a target to deliver into upon release creationrNr r s r AddToTargetFlagr8s  Erc UR5nURSS[R"5U[R "S5S9 URSUSS9 g) zAdds Images flag.z--imageszNAME=TAGz Reference to a collection of individual image name to image full path replacements. For example: $ gcloud deploy releases create foo \ --images image1=path/to/image1:v1@sha256:45db24 metavartyperrz--build-artifactszReference to a Skaffold build artifacts output file from skaffold build --file-output=BUILD_ARTIFACTS. If you aren't using Skaffold, use the --images flag below to specify the image-names-to-tagged-image references.rN)add_mutually_exclusive_groupr rArgDicttextwrapdedent)r r images_groups r AddImagesGrouprAsi446,     ??     5  rc(URSUSSS9 g)zAdds config flag.z--fileTzUPath to yaml file containing Delivery Pipeline(s), Target(s) declarative definitions.)rrequiredrNr r s r AddConfigFiler"^s#  & rc&URSUSS9 g)rrz#Destination target to promote into.rNr r s r AddToTargetr$ksF)Nrc&URSUSS9 g)zAdds rollout-id flag.z --rollout-idz4ID to assign to the generated rollout for promotion.rNr r s r AddRolloutIDr&rs  Arc$URSX!S9 g)zAdds release flag.z --releaserNr r help_textrs r AddReleaser*{sk&Arc(URSUSUS9 g)zAdds force flag.z--force store_true)ractionrNr r(s r AddForcer.s!    rc$URUUS9 g)zAdds description related flag.rNr )r r)names r AddDescriptionr2s rc&URSSUS9 g)zAdds delivery pipeline flag.z--delivery-pipelinez.The name of the Cloud Deploy delivery pipeline)rr!Nr )r r!s r AddDeliveryPipeliner4s ;rc[R"S5U-nURSS[R"5US9 g)zAdds --annotations flag.z Annotations to apply to the %s. Annotations take the form of key/value string pairs. Examples: Add annotations: $ {command} --annotations="from_target=test,status=stable" z --annotations KEY=VALUErrrNrrr rrr resource_typer)s r AddAnnotationsFlagr;sIoo    )      rc[R"S5U-nURSS[R"5US9 g)zAdd --labels flag.z Labels to apply to the %s. Labels take the form of key/value string pairs. Examples: Add labels: $ {command} --labels="commit=abc123,author=foo" z--labelsr6r7Nr8r9s r AddLabelsFlagr=sIoo    )      rc.URSS[S9 g)zAdds docker version flag.z--docker-versionzVersion of the Docker binary.rrNr strr s r AddDockerVersionrCs * rc.URSS[S9 g)zAdds helm version flag.z--helm-versionzVersion of the Helm binary.r?Nr@rBs r AddHelmVersionrEs ( rc.URSS[S9 g)zAdds kpt version flag.z --kpt-versionzVersion of the Kpt binary.r?Nr@rBs r AddKptVersionrGs ' rc.URSS[S9 g)zAdds kubectl version flag.z--kubectl-versionzVersion of the Kubectl binary.r?Nr@rBs r AddKubectlVersionrIs + rc.URSS[S9 g)zAdds kustomize version flag.z--kustomize-versionz Version of the Kustomize binary.r?Nr@rBs r AddKustomizeVersionrKs - rc.URSS[S9 g)zAdds skaffold version flag.z--skaffold-versionzVersion of the Skaffold binary.r?Nr@rBs r AddSkaffoldVersionrMs!BrcX[R"S5n[R"SUS9$)zAdd --skaffold-file flag.a Path of the skaffold file absolute or relative to the source directory. Examples: Use Skaffold file with relative path: The current working directory is expected to be some part of the skaffold path (e.g. the current working directory could be /home/user) $ {command} --source=/home/user/source --skaffold-file=config/skaffold.yaml The skaffold file absolute file path is expected to be: /home/user/source/config/skaffold.yaml Use Skaffold file with absolute path and with or without source argument: $ {command} --source=/home/user/source --skaffold-file=/home/user/source/config/skaffold.yaml $ {command} --skaffold-file=/home/user/source/config/skaffold.yaml z--skaffold-filer0rrrArgumentr)s r AddSkaffoldFileFlagrRs)oo), (y 99rc6[R"S[SS9$)zAdds source flag.z--source.)rdefault)rrP_SOURCE_HELP_TEXTrr AddSourceFlagrXs (# rc,[R"SSS9$)Nz--from-k8s-manifesta-The path to a Kubernetes manifest, which Cloud Deploy will use to generate a skaffold.yaml file for you (for example, foo/bar/k8.yaml). The generated Skaffold file will be available in the Google Cloud Storage source staging directory (see --gcs-source-staging-dir flag) after the release is complete.r0rrPrWrr AddKubernetesFileFlagr[s  J  rc,[R"SSS9$)Nz--from-run-manifesta1The path to a Cloud Run manifest, which Cloud Deploy will use to generate a skaffold.yaml file for you (for example, foo/bar/service.yaml). The generated Skaffold file will be available in the Google Cloud Storage source staging directory (see --gcs-source-staging-dir flag) after the release is complete.r0rZrWrr AddCloudRunFileFlagr](s  K  rc UR5n[5RU5 [5RU5 UR SS9n[ 5RU5 [ 5RU5 g)zAdd Skaffold sources.FmutexN)rr[ AddToParserr] add_grouprXrR)r config_group source_groups r AddSkaffoldSourcesre5sf446,%%l3##L1''e'4,/l+##L1rc*URSSSSSS9 g)zAdd --description flag. --descriptionz1Description of rollout created during a rollback.FNrrrUr!r rBs r AddDescriptionFlagri@s$ >  rcT[R"S5nURSSSUS9 g)zAdd --list-all-pipelines flag.zi List all Delivery Pipelines associated with a target. Usage: $ {command} --list-all-pipelines z--list-all-pipelinesr,Nr-rUrrrr r r)s r AddListAllPipelinesrnKs3oo) \4ircT[R"S5nURSSSUS9 g)z Add --skip-pipeline-lookup flag.z If set, skip fetching details of associated pipelines when describing a target. Usage: $ {command} --skip-pipeline-lookup z--skip-pipeline-lookupr,FrkNrlrms r AddSkipPipelineLookuprp[s6oo)    rcV[R"S5nURSUSSSS9 g)zAdd --rollback-of-rollout flag.af If set, this validates whether the rollout name specified by the flag matches the rollout on the target. Examples: Validate that `test-rollout` is the rollout to rollback on the target. $ {command} --rollback-of-rollout=projects/test-project/locations/us-central1/deliveryPipelines/test-pipeline/releases/test-release/rollouts/test-rollout z--rollback-of-rolloutFNrhrlrms r AddRollbackOfRolloutrrns9oo  )    rcV[R"S5nURSUSSSS9 g)zAdd --starting-phase-id flag.z If set, starts the created rollout at the specified phase. Start rollout at `stable` phase: $ {command} --starting-phase-id=stable z--starting-phase-idFNrhrlrms r AddStartingPhaseIdrts9oo)    rc[R"S5n[R"SUS[R "5S9$)z"Add --initial-rollout-labels flag.z Labels to apply to the initial rollout when creating the release. Labels take the form of key/value string pairs. Examples: Add labels: $ {command} initial-rollout-labels="commit=abc123,author=foo" z--initial-rollout-labelsr6rrrrrrrPrrrQs r AddInitialRolloutLabelsFlagrxs=oo  )       rc[R"S5n[R"SUS[R "5S9$)z(Adds --initial-rollout-annotations flag.z Annotations to apply to the initial rollout when creating the release. Annotations take the form of key/value string pairs. Examples: Add annotations: $ {command} --initial-rollout-annotations="from_target=test,status=stable" z--initial-rollout-annotationsr6rvrwrQs r AddInitialRolloutAnnotationsFlagrzs=oo  ) %      rc^[R"S5n[R"SUSSSS9$)z%Adds --initial-rollout-phase-id flag.a' The phase to start the initial rollout at when creating the release. The phase ID must be a valid phase on the rollout. If not specified, then the rollout will start at the first phase. Examples: Start rollout at `stable` phase: $ {command} --initial-rollout-phase-id=stable z--initial-rollout-phase-idFNrhrOrQs r AddInitialRolloutPhaseIDFlagr|s7oo  ) "    rc0[R"SSSSS9$)z#Adds --enable-initial-rollout flag.z--enable-initial-rollout store_constzeCreates a rollout in the first target defined in the delivery pipeline. This is the default behavior.Tr-rconstrZrWrr AddEnableInitialRolloutFlagrs%   5  rc0[R"SSSSS9$)z$Adds --disable-initial-rollout flag.z--disable-initial-rolloutr~zNSkips creating a rollout in the first target defined in the delivery pipeline.TrrZrWrr AddDisableInitialRolloutFlagrs% !    rc<UR5nURSS9n[5RU5 [ 5RU5 [ 5RU5 [ 5RU5 [5RU5 g)z Adds initial-rollout flag group.Fr_N)rrbrxrarzr|rr)r groupenable_initial_rollout_groups r AddInitialRolloutGrouprs|  - - /%"'u!=++,HI"$001MN ,,-IJ++,HI ,,U3rc(URSUSSS9 g)zAdds job-id flag.z--job-idzJob ID on a rollout resourceTrrr!Nr r s r AddJobIdr s!  ) rc(URSUSUS9 g)zAdds phase-id flag.z --phase-idzPhase ID on a rollout resourcerNr )r r!rs r AddPhaseIdrs!  + rc|[R"S5nURSS[R"5UUS9 g)zAdd --deploy-parameters flag.z Deployment parameters to apply to the release. Deployment parameters take the form of key/value string pairs. Examples: Add deployment parameters: $ {command} --deploy-parameters="key1=value1,key2=value2" z--deploy-parametersr6rNr8)r rr)s r AddDeployParametersFlagrsBoo  )       rcPURSSU[R"5SS9 g)z#Adds override-deploy-policies flag.z--override-deploy-policiesPOLICYzDeploy policies to override)rrrrN)r rArgListr s r AddOverrideDeployPoliciesr4s-"     ( r)F)rg)T)TF)-__doc__rgooglecloudsdk.callioperrrVrrrrr"r$r&r*r.r2r4r;r=rCrErGrIrKrMrRrXr[r]rerirnrprrrtrxrzr|rrrrrrrrWrr rs*/(  : B **:6  2  &0**,2   4,r