7SrSSKJr SSKJr SSKJr SSKrSSKJr SSKJ r SSK J r SS KJr SS KJr SS KJr SS KJr SS KJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJ r SSKJ!r! SSK"J#r# SSK$r$Sr%Sr&\%S-r'/SQr(/SQr)SS/r*/SQr+SS /r,S!S"S#S$.r-S%S!S&.r.S%S!S'.r/S(S)S*.r0S+r1S,r2S-r3S.r4S/Rk\3\45r6S0r7S1S2S3.r8S4S5S6.r9S7r:S8r;S9rS<r?S=r@S>rAS?rBS@rCSArDSBrESCrFSzSDjrGSErHSFrISGrJSHrKSIrLSJrMSKrNSLrOSMrPSNrQSOrRSPrSSQrTSRrUSSrVSTrWSUrXSVrYSWrZSXr[SYr\SZr]S[r^"S\S]\R5r`"S^S_\R5rbS`rcSardSbreScrfSdrgSerhS{SfjriSgrjShrkSirlSjrmSkrnSlroSmrpSnrqSorrSprsSqrtSrruSsrvStrwSurxSvrySwrzSxr{Syr|g)|zBHelpers for flags in commands working with Google Cloud Functions.)absolute_import)division)unicode_literalsN)DirectoriesCompleter)util)client)actions) arg_parsers)base) exceptions)concepts)deps)flags) completers)concept_parsers)presentation_specs)log) properties) resources) console_iocloudfunctionsv1z.projects.locations)httpevent cloudevent)DEBUGINFOERRORzPRIVATE-RANGES-ONLYALL)rz INTERNAL-ONLYzINTERNAL-AND-GCLBz SECURE-ALWAYSzSECURE-OPTIONALallz internal-onlyzinternal-and-gclb) ALLOW_ALLALLOW_INTERNAL_ONLYALLOW_INTERNAL_AND_GCLBzprivate-ranges-only)PRIVATE_RANGES_ONLY ALL_TRAFFIC)VPC_EGRESS_PRIVATE_RANGES_ONLYVPC_EGRESS_ALL_TRAFFIC secure-alwayszsecure-optional) SECURE_ALWAYSSECURE_OPTIONALzR^projects/[^/]+/locations/[^/]+/keyRings/[a-zA-Z0-9_-]+/cryptoKeys/[a-zA-Z0-9_-]+$zKMS key name should match projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{cryptokey} and only contain characters from the valid character set for a KMS key.zH^projects/[^/]+/locations/[^/]+/repositories/[a-z]([a-z0-9-]*[a-z0-9])?$zG^(?P.*)-docker.pkg.dev\/(?P[^\/]+)\/(?P[^\/]+)z({}|{})zDocker repository name should match `projects/{project}/locations/{location}/repositories/{repository}` or `{location}-docker.pkg.dev/{project}/{repository}` and only contain characters from the valid character set for a repository.zcontainer-registryzartifact-registry)CONTAINER_REGISTRYARTIFACT_REGISTRY automaticz on-deploy) AUTOMATIC ON_DEPLOYc[R"S[Vs/sHoR5PM snSS9nUR U5 gs snf)Nz--min-log-levelz$Minimum level of logs to be fetched.choiceshelp_str)r ChoiceArgument SEVERITIESlower AddToParser)parserx min_log_args 1lib/googlecloudsdk/command_lib/functions/flags.pyAddMinLogLevelFlagr<lsC##",-*Qwwy*-5+ &!.A c[R"S[Vs/sHoR5PM snSS9nUR U5 gs snf)Nz--ingress-settingsz]Ingress settings controls what traffic can reach the function. By default `all` will be used.r1)r r4INGRESS_SETTINGSr6r7)r8r9ingress_settings_args r;AddIngressSettingsFlagrAusH,,"23"2Qwwy"23 5 ""6* 4r=c[R"S[Vs/sHoR5PM snSS9nUR U5 gs snf)Nz--egress-settingszEgress settings controls what traffic is diverted through the VPC Access Connector resource. By default `private-ranges-only` will be used.r1r r4EGRESS_SETTINGSr6r7)r8r9egress_settings_args r;AddEgressSettingsFlagrFsF++"12/Qwwy/2 ; !!&)3r=c [R"SS[Vs/sHoR5PM snSS9nUR U5 gs snf)Nz--security-levelr(zSecurity level controls whether a function's URL supports HTTPS only or both HTTP and HTTPS. By default, `secure-always` will be used, meaning only HTTPS is supported.)defaultr2r3)r r4SECURITY_LEVELr6r7)r8r9security_level_args r;AddSecurityLevelFlagrKsI**"01.Qwwy.1 7   (2sA c,[RR5nUR[[ 5 UR URS[RRRR0[S9nUR5$)N projectsId)params collection)rREGISTRYCloneRegisterApiByNameAPI API_VERSIONParsenamerVALUEScoreproject GetOrFailLOCATIONS_COLLECTIONSelfLink)resourceregistryrefs r;GetLocationsUrir`sq    % % '( S+.mmJ--22::DD E%  # cvSnURSS9nSnURS[USS9 URSUS 9 g ) z?Add flags for specifying function memory and cpu to the parser.aZ Limit on the amount of memory the function can use. Allowed values for v1 are: 128MB, 256MB, 512MB, 1024MB, 2048MB, 4096MB, and 8192MB. Allowed values for GCF 2nd gen are in the format: with allowed units of "k", "M", "G", "Ki", "Mi", "Gi". Ending 'b' or 'B' is allowed, but both are interpreted as bytes as opposed to bits. Examples: 1000000K, 1000000Ki, 256Mb, 512M, 1024Mi, 2G, 4Gi. By default, a new function is limited to 256MB of memory. When deploying an update to an existing function, the function keeps its old memory limit unless you specify this flag.Frequiredar The number of available CPUs to set. Only valid when `--memory=MEMORY` is specified. Examples: .5, 2, 2.0, 2000m. By default, a new function's available CPUs is determined based on its memory value. When deploying an update that includes memory changes to an existing function, the function's available CPUs will be recalculated based on the new memory unless this flag is specified. When deploying an update that does not include memory changes to an existing function, the function's "available CPUs" setting will keep its old value unless you use this flag to change the setting. z--memoryT)typehelprdz--cpurfN) add_group add_argumentstr)r8memory_help_textgroup cpu_help_texts r;AddFunctionMemoryAndCpuFlagsrnsS0   E  *% -Zc0@4PW=1rac@[R"/SQSS9nU"U5$)zParse binary size to number of bytes. Args: binary_size: str, memory with size suffix Returns: num_bytes: int, the number of bytes )KBMBMiBGBGiBrq)suggested_binary_size_scales default_unit)r BinarySize) binary_sizebinary_size_parsers r;ParseMemoryStrToNumBytesrzs(#--#C K ((racUR(a@URS:a/[R"SRUR55egg)NizB--timeout: value must be less than or equal to 540s; received: {}s)timeoutr ArgumentTypeErrorformatargss r;ValidateV1TimeoutFlagrs? \\dllS(  ' 'L   )\racNSnURSU[R"SS9S9 g)zAdd flag for specifying function timeout to the parser. Args: parser: the argparse parser for the command. Returns: None aX The function execution timeout, e.g. 30s for 30 seconds. Defaults to original value for existing function or 60 seconds for new functions. For GCF 1st gen functions, cannot be more than 540s. For GCF 2nd gen functions, cannot be more than 3600s. See $ gcloud topic datetimes for information on duration formats. --timeout1s lower_boundrfreNrir Durationr8 help_texts r;AddFunctionTimeoutFlagrs1K)  (<(<(Nrac&URSSSS9 g)z>Add flag for specifying function retry behavior to the parser.z--retryzEIf specified, then the function will be retried in case of a failure. store_true)rfactionNrir8s r;AddFunctionRetryFlagrs"  racBURS[RSS9 g)z%Add the --allow-unauthenticated flag.z--allow-unauthenticatedzcIf set, makes this a public function. This will allow all callers, without checking authentication.rrfN)rir StoreTrueFalseActionrs r;AddAllowUnauthenticatedFlagr s&  - - 6 rac,SnURSSSUS9 g)NzBIf specified, latest function revision will be served all traffic.z#--serve-all-traffic-latest-revisionrFrrHrfrrs r;$AddServeAllTrafficLatestRevisionFlagrs+J  +   rac2SnURS[US9 g)z6Add flag for specifying function memory to the parser.z; Specifies one of the Google provided buildpack stacks. z--buildpack-stackrerfN)rirjrs r;AddBuildpackStackFlagr"s!) ))DracSnU(aUS- nU(aUS- nURSS[R"[RR R 5UUS9 g)zAdd the --gen2 flag.zIf enabled, this command will use Cloud Functions (Second generation). If disabled with `--no-gen2`, Cloud Functions (First generation) will be used. If not specified, the value of this flag will be taken from the `functions/gen2` configuration property.z If the `functions/gen2` configuration property is not set, defaults to looking up the given function and using its generation.z This command could conflict with `--v2`. If specified `--gen2` with `--no-v2`, or `--no-gen2` with `--v2`, Second generation will be used.z--gen2F)rHrrfhiddenN)rir StoreBooleanPropertyrrW functionsgen2)r8operates_on_existing_functionrallow_v2rs r; AddGen2Flagr+sv 6 #  FI  I    ) )**;*;*E*E*J*J K   racx[[RRRR 55$)z;Returns whether 2nd gen should be used for Cloud Functions.)boolrrWrrGetBoolrar; ShouldUseGen2rIs( j))..668 99rac[RRRR 5=(a [ 5(+$)z;Returns whether 1st gen should be used for Cloud Functions.)rrWrrIsExplicitlySetrrrar; ShouldUseGen1rNs1!!&&668P=PracUR$N)allow_unauthenticatedrs r;ShouldEnsureAllUsersInvokerUs # ##racTURS5=(a UR(+$)Nr) IsSpecifiedrrs r;ShouldDenyAllUsersInvokerYs' ./)(( (rac,SnURSSSUS9 g)zAdd the --v2 flag.a8If specified, this command will use Cloud Functions v2 APIs and return the result in the v2 format (See https://cloud.google.com/functions/docs/reference/rest/v2/projects.locations.functions#Function). If not specified, 1st gen and 2nd gen functions will use v1 and v2 APIs respectively and return the result in the corresponding format (For v1 format, see https://cloud.google.com/functions/docs/reference/rest/v1/projects.locations.functions#resource:-cloudfunction). This command conflicts with `--no-gen2`. If specified with this combination, v2 APIs will be used.z--v2rNrrrs r; AddV2Flagr`s-,     rac.URS[SS9 g)z;Add flag for specifying function source code to the parser.z--sourceaB Location of source code to deploy. Location of the source can be one of the following three options: * Source code in Google Cloud Storage (must be a `.zip` archive), * Reference to source repository or, * Local filesystem path (root directory of function source). Note that, depending on your runtime type, Cloud Functions will look for files with specific names for deployable functions. For Node.js, these filenames are `index.js` or `function.js`. For Python, this is `main.py`. If you do not specify the `--source` flag: * The current directory will be used for new function deployments. * If the function was previously deployed using a local filesystem path, then the function's source code will be updated using the current directory. * If the function was previously deployed using a Google Cloud Storage location or a source repository, then the function's source code will not be updated. The value of the flag will be interpreted as a Cloud Storage location, if it starts with `gs://`. The value will be interpreted as a reference to a source repository, if it starts with `https://`. Otherwise, it will be interpreted as the local filesystem path. When deploying source from the local filesystem, this command skips files specified in the `.gcloudignore` file (see `gcloud topic gcloudignore` for more information). If the `.gcloudignore` file doesn't exist, the command will try to create it. The minimal source repository URL is: `https://source.developers.google.com/projects/${PROJECT}/repos/${REPO}` By using the URL above, sources from the root directory of the repository on the revision tagged `master` will be used. If you want to deploy from a revision different from `master`, append one of the following three sources to the URL: * `/revisions/${REVISION}`, * `/moveable-aliases/${MOVEABLE_ALIAS}`, * `/fixed-aliases/${FIXED_ALIAS}`. If you'd like to deploy sources from a directory different from the root, you must specify a revision, a moveable alias, or a fixed alias, as above, and append `/paths/${PATH_TO_SOURCES_DIRECTORY}` to the URL. Overall, the URL should match the following regular expression: ``` ^https://source\.developers\.google\.com/projects/ (?[^/]+)/repos/(?[^/]+) (((/revisions/(?[^/]+))|(/moveable-aliases/(?[^/]+))| (/fixed-aliases/(?[^/]+)))(/paths/(?.*))?)?$ ``` An example of a validly formatted source repository URL is: ``` https://source.developers.google.com/projects/123456789/repos/testrepo/ moveable-aliases/alternate-branch/paths/path-to=source ``` ) completerrfN)rirrs r; AddSourceFlagrus"$E IracBURSS[RS9 g)z3Add flag for specifying stage bucket to the parser.z--stage-bucketaWhen deploying a function from a local directory, this flag's value is the name of the Google Cloud Storage bucket in which source code will be stored. Note that if you set the `--stage-bucket` flag when deploying a function, you will need to specify `--source` or `--stage-bucket` in subsequent deployments to update your source code. To use this flag successfully, the account in use must have permissions to write to this bucket. For help granting access, refer to this guide: https://cloud.google.com/storage/docs/access-control/rN)riapi_util%ValidateAndStandarizeBucketUriOrRaisers r;AddStageBucketFlagrs) B  9 9rac$URSSS9 g)Nz --runtimez Runtime in which to run the function. Required when deploying a new function; optional when updating an existing function. For a list of available runtimes, run `gcloud functions runtimes list`. rgrrs r;AddRuntimeFlagrs  rac p[R"SSS[R[5[ 5S9$)Nz'vpcaccess.projects.locations.connectors connectorF) resource_namedisable_auto_completersrM locationsId connectorsId)r ResourceSpec DEFAULT_PROJECT_ATTRIBUTE_CONFIGRegionAttributeConfigVpcConnectorAttributeConfigrrar;GetVpcConnectorResourceSpecrs3   /#::').0  racURSS9n[R"S[5SUSS0S9n[R "U/SS /0S 9R U5 URS S S S9 g)z4Add flag for specifying VPC connector to the parser.Tmutexz--vpc-connectora The VPC Access connector that the function can connect to. It can be either the fully-qualified URI, or the short name of the VPC Access connector resource. If the short name is used, the connector must belong to the same project. The format of this field is either `projects/${PROJECT}/locations/${LOCATION}/connectors/${CONNECTOR}` or `${CONNECTOR}`, where `${CONNECTOR}` is the short name of the VPC Access connector. region)rlflag_name_overridesz--vpc-connector.region--regioncommand_level_fallthroughsz--clear-vpc-connectorrz. Clears the VPC connector field. rN)rhrResourcePresentationSpecrr ConceptParserr7ri)r8 mutex_groupr]s r;AddVPCConnectorMutexGrouprs  t ,+  8 8!#  #R.("j#;ZL!I  K   rac&URSSSS9 g)z"Add flags for setting VPC network.z --networkzThe VPC network that the Cloud Function will be able to send traffic to. If --subnet is also specified, subnet must be a subnetwork of the network specified by this --network flag. To clear existing VPC network settings, use --clear-network.TrfrNrrs r;_AddVpcNetworkFlagrs# G  rac&URSSSS9 g)z%Add flags for setting VPC subnetwork.z--subneta]The VPC subnetwork that the Cloud Function will get IPs from. The subnetwork must be `/26` or larger. If --network is also specified, subnet must be a subnetwork of the network specified by the --network flag. If --network is not specified, network will be looked up from this subnetwork. To clear existing VPC network settings, use --clear-network.TrNrrs r;_AddVpcSubnetFlagr!s" , racPURS[R"5SSSS9 g)z'Add flags for setting VPC network tags.z--network-tagsTAGSzyApplies the given network tags (comma separated) to the Cloud Function. To clear existing tags, use --clear-network-tags.T)remetavarrfrN)rir ArgListrs r;_AddVpcNetworkTagsFlagr1s1     > rac(URSSSSS9 g)z(Add flags for clearing VPC network tags.z--clear-network-tagsrz9Clears all existing network tags from the Cloud Function.TrrfrNrrs r;_AddClearVpcNetworkTagsFlagr@s!  E  rac[R"S[Vs/sHoR5PM snSSS9nUR U5 gs snf)z1Add flags for setting Direct VPC egress settings.z--direct-vpc-egresszSpecify which of the outbound traffic to send through Direct VPC egress. Configuring DirectVPC network is required to use this flag.T)r2r3rNrC)r8r9direct_vpc_egress_args r;_AddDirectVpcEgressFlagrLsL--"12/Qwwy/2 Q##F+3sA cURSSS9n[U5 [U5 URSSS9n[ U5 [ U5 g)zCAdd flag for specifying Direct VPC network interface to the parser.z&Direct VPC egress setting flags group.T)rrrN)add_argument_grouprrrhrr)r8rl tags_groups r;_AddNetworkInterfaceGroupFlagsrZsP  # #.t $ %UET$7*$j)rac(URSSSSS9 g)z#Add flags for clearing VPC network.z--clear-networkrzNDisconnect this Cloud Function from the Direct VPC network it is connected to.TrNrrs r;_AddClearVpcNetworkFlagrgs%  racfURSSS9n[U5 [U5 [U5 g)z6Add flags for all Direct VPC network related settings.TrN)rhrrr)r8ni_groups r;AddAllDirectVpcFlagsrts/   D  6( *(#&!racdURSS9nURSSS9 URSSSS 9 g ) z8Add flag for specifying Build Worker Pool to the parser.Trz--build-worker-poola Name of the Cloud Build Custom Worker Pool that should be used to build the function. The format of this field is `projects/${PROJECT}/locations/${LOCATION}/workerPools/${WORKERPOOL}` where ${PROJECT} is the project id and ${LOCATION} is the location where the worker pool is defined and ${WORKERPOOL} is the short name of the worker pool. rgz--clear-build-worker-poolrz? Clears the Cloud Build Custom Worker Pool field. rNrhrir8rs r;AddBuildWorkerPoolMutexGroupr}sP  t ,+   !  rac$URSSS9 g)z2Add flag for specifying entry point to the parser.z --entry-pointz Name of a Google Cloud Function (as defined in source code) that will be executed. Defaults to the resource name suffix (ID of the function), if not specified. rgNrrs r;AddEntryPointFlagrs racURSS9nURS[R"SS9SS9 URSS S S 9 g ) z9Add flag for specifying the max instances for a function.Trz--max-instancesrz Sets the maximum number of instances for the function. A function execution that would exceed max-instances times out. rz--clear-max-instancesra Clears the maximum instances setting for the function. If it's any 2nd gen function or a 1st gen HTTP function, this flag sets maximum instances to 0, which means there is no limit to maximum instances. If it's an event-driven 1st gen function, this flag sets maximum instances to 3000, which is the default value for 1st gen functions. rNrhrir BoundedIntrs r;AddMaxInstancesFlagrs^  t ,+   ! !a 0    racURSS9nURS[R"SS9SS9 URSS S S 9 g ) z9Add flag for specifying the min instances for a function.Trz--min-instancesrrz Sets the minimum number of instances for the function. This is helpful for reducing cold start times. Defaults to zero. rz--clear-min-instancesrzE Clears the minimum instances setting for the function. rNrrs r;AddMinInstancesFlagrs^  t ,+   ! !a 0   rac URSS9nURSS[RS9 URSS[RS9 URSS S S 9 UR 5n[ R"[R"S [R"5S SS0USS9/SS/0S9RU5 URS[R"5[RSSS9 URS[R"5[RSSS9 UR 5nURSSSS9 URS S!S"S9 g#)$zpAdd arguments specifying functions trigger to the parser. Args: parser: the argparse parser for the command. a If you don't specify a trigger when deploying an update to an existing function it will keep its current trigger. You must specify one of the following when deploying a new function: - `--trigger-topic`, - `--trigger-bucket`, - `--trigger-http`, - `--trigger-event` AND `--trigger-resource`, - `--trigger-event-filters` and optionally `--trigger-event-filters-path-pattern`. rgz--trigger-topicaOName of Pub/Sub topic. Every message published in this topic will trigger function execution with message contents passed as input data. Note that this flag does not accept the format of projects/PROJECT_ID/topics/TOPIC_ID. Use this flag to specify the final element TOPIC_ID. The PROJECT_ID will be read from the active configuration.rz--trigger-bucketzGoogle Cloud Storage bucket name. Trigger the function when an object is created or overwritten in the specified Cloud Storage bucket.z--trigger-httpra Function will be assigned an endpoint, which you can view by using the `describe` command. Any HTTP request (of a supported type) to the endpoint will trigger function execution. Supported HTTP request types are: POST, PUT, GET, DELETE, and OPTIONS.rz--trigger-channelz] The channel to use in the trigger for third-party event sources. locationrT)rrlrz--trigger-channel.location--trigger-locationrz--trigger-event-filterszATTRIBUTE=VALUEa* The Eventarc matching criteria for the trigger. The criteria can be specified either as a single comma-separated argument or as multiple arguments. The filters must include the ``type'' attribute, as well as any other attributes that are expected for the chosen type. )rerrrfz$--trigger-event-filters-path-patternzATTRIBUTE=PATH_PATTERNa The Eventarc matching criteria for the trigger in path pattern format. The criteria can be specified as a single comma-separated argument or as multiple arguments. The provided attribute/value pair will be used with the `match-path-pattern` operator to configure the trigger, see https://cloud.google.com/eventarc/docs/reference/rest/v1/projects.locations.triggers#eventfilter and https://cloud.google.com/eventarc/docs/path-patterns for more details about on how to construct path patterns. For example, to filter on events for Compute Engine VMs in a given zone: `--trigger-event-filters-path-pattern=resourceName='/projects/*/zones/us-central1-a/instances/*'z--trigger-event EVENT_TYPEz~Specifies which action should trigger the function. For a list of acceptable values, call `gcloud functions event-types list`.rrfz--trigger-resourceRESOURCEa Specifies which resource from `--trigger-event` is being observed. E.g. if `--trigger-event` is `providers/cloud.storage/eventTypes/object.change`, `--trigger-resource` must be a bucket name. For a list of expected resources, call `gcloud functions event-types list`.N)add_mutually_exclusive_grouprirValidatePubsubTopicNameOrRaiserrrrrreventarc_flagsChannelResourceSpecr7r ArgDict UpdateAction)r8 trigger_groupeventarc_trigger_grouptrigger_provider_spec_groups r;AddTriggerFlagGroupr s 55 < 5  - "  2 2    9 9  9);;=  5 5!002$.r"2*   ')=(>" K%%     % % & %%,     % %& j &(!. @ @ B** 1 +** 1 + rac(^\rSrSrU4SjrSrU=r$)LocationsCompleteriGc <>[[U] "S[SS.UD6 g)Nz"alpha functions regions list --uri)rO list_commandr)superr__init__r[)selfkwargs __class__s r;rLocationsCompleter.__init__Is( d,'9 rar)__name__ __module__ __qualname____firstlineno__r__static_attributes__ __classcell__rs@r;rrGs rarcf^\rSrSrSr\R R4U4SjjrU4Sjr Sr U=r $)RegionFallthroughiQzCustom fallthrough for region dependent on GCF generation. For GCF gen1 this falls back to the functions/region property. For GCF gen2 the property fallback is only used if it is explicitly set. Otherwise the region is prompted for. c|>[[U] [RR R 5 Xlgr)rr rrrWrr release_track)rr"rs r;rRegionFallthrough.__init__Zs+ T+J,=,=,G,G,N,NO&rac$>[5(+nU(dURR5(a[[U]U5$[ R"5(d[R"SS5e[R"UR5nUR5Vs/sHoDRPM nn[ R"USS9nXVn[ R"R%SR'U55 U$s snf)Nrz_You must specify a region. Either use the flag `--region` or set the functions/region property.zPlease specify a region: )messagezNTo make this the default region, run `gcloud config set functions/region {}`. )rpropertyrrr _Callr CanPromptr RequiredArgumentException client_v2FunctionsClientr" ListRegions locationId PromptChoicerstatusPrintr~) r parsed_argsuse_gen1rlregionsidxrrs r;r'RegionFallthrough._Call^s ?"H4==0022 $d 1+ >>    ! !  0 0 0  & &t'9'9 :F%+%7%7%9:%9||%9G:  ! !'3O PC \FJJ 55;VF^ M;s-D )r") rrrr__doc__r ReleaseTrackALPHArr'rrrs@r;r r Qs($(#4#4#:#:'rar cURSU[[R"[R R R5S9 g)Nr)rfrr)rirr StorePropertyrrWrrrs r; AddRegionFlagr<xs> "  " ":#4#4#>#>#E#E F racJ[R"SS[[5/S9$)NrzyThe Cloud region for the {resource}. Overrides the default `functions/region` property value for this command invocation.)rVrr fallthroughs)r ResourceParameterAttributeConfigrr rrar;rrs,  2 2  K#%'( rac.URSS[S9 g)z7Add flag for specifying trigger location to the parser.rzhThe location of the trigger, which must be a region or multi-region where the relevant events originate.)rfrN)rirrs r;AddTriggerLocationFlagrAs" 8# racJ[R"SS[RS9$)NfunctionThe name of the {resource}.)rVr value_type)r r?rValidateFunctionNameOrRaiserrar;FunctionAttributeConfigrGs$  2 2 -55 rac,[R"SSS9$)NrrD)rVr)r r?rrar;rrs  2 2 - rac p[R"SSS[R[5[ 5S9$)Nz+cloudfunctions.projects.locations.functionsrCF)rrrMr functionsId)r rrrrGrrar;GetFunctionResourceSpecrKs3   3#::'))+  racU=(d SRU5n[RRS[ 5UUS9R U5 g)aAdds a Cloud Function resource argument. NOTE: May be used only if it's the only resource arg in the command. Args: parser: the argparse parser for the command. verb: (Optional) str, the verb to describe the resource, such as 'to update'. help_text_override: (Optional)str, the help text to use for the resource argument. If override is providded, verb will be ignored. required: bool, whether the argument is required. zThe Cloud Function name {}.NAMErcN)r~rr ForResourcerKr7)r8verbhelp_text_overriderdrs r;AddFunctionResourceArgrQsN!N$A$H$H$N)++  , Krac$URSSS9 g)Nz--service-accountaS The email address of the IAM service account associated with the function at runtime. The service account represents the identity of the running function, and determines what permissions the function has. If not provided, the function will use the project's default service account for Compute Engine. rgrrs r;AddServiceAccountFlagrSs  rac$URSSS9 g)Nz--run-service-accountah The email address of the IAM service account associated with the Cloud Run service for the function. The service account represents the identity of the running function, and determines what permissions the function has. If not provided, the function will use the project's default service account for Compute Engine. rgrrs r;AddRunServiceAccountFlagrUs  rac$URSSS9 g)Nz--trigger-service-accounta The email address of the IAM service account associated with the Eventarc trigger for the function. This is used for authenticated invocation. If not provided, the function will use the project's default service account for Compute Engine. rgrrs r;AddTriggerServiceAccountFlagrWs!  rac.URSS[S9 g)N--dataz:JSON string with data that will be passed to the function.r)ri_ValidateJsonOrRaiseDataErrorrs r; AddDataFlagr[s K (rac.URSS[S9 g)N --cloud-eventa JSON encoded string with a CloudEvent in structured content mode. Mutually exclusive with --data flag. Use for Cloud Functions 2nd Gen CloudEvent functions. The CloudEvent object will be sent to your function as a binary content mode message with the top-level 'data' field set as the HTTP body and all other JSON fields sent as HTTP headers. r)ri#_ValidateJsonOrRaiseCloudEventErrorrs r;AddCloudEventsFlagr_s"  / racPSnURSU[R"SS9SS9 g)z5Add flag for specifying gcloud timeout to the parser.z The gcloud command timeout, e.g. 30s for 30 seconds. Defaults to the function execution timeout duration of the function. See $ gcloud topic datetimes for information on duration formats.rrrT)rfrerNrrs r;AddGcloudHttpTimeoutFlagra s6K)      D 1  rac&URSSSS9 g)N policy_file POLICY_FILEzFPath to a local JSON or YAML formatted file containing a valid policy.rrrs r;AddIAMPolicyFileArgres  ' rac$URSSS9 g)Nz --ignore-fileaOverride the .gcloudignore file in the source directory and use the specified file instead. By default, the source directory is your current directory. Note that it could be changed by the --source flag, in which case your .gcloudignore file will be searched in the overridden directory. For example, `--ignore-file=.mygcloudignore` combined with `--source=./mydir` would point to `./mydir/.mygcloudignore`rgrrs r;AddIgnoreFileFlagrg(s ' racU[RR[RR[RR4;a$UR S[ R5SS9 gg)z3Adds flags for selecting the runtime update policy.z--runtime-update-policyzx Runtime update policy for the function being deployed. The option `automatic` is used by default. )r2rfN)r r8r9BETAGAriRUNTIME_UPDATE_POLICY_MAPPINGvalues)r8tracks r;AddRuntimeUpdatePolicyrn8sj      !-446  rac [R"S[[R 55S[ R "SSS9S9nURU5 g)zEAdds flags for selecting the Docker registry type for Cloud Function.z--docker-registryz Docker Registry to use for storing the function's Docker images. The option `artifact-registry` is used by default. av With the general transition from Container Registry to Artifact Registry, the option to specify docker registry is deprecated. All container image storage and management will automatically transition to Artifact Registry. For more information, see https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr)warn)r2r3rN)r r4sortedDOCKER_REGISTRY_MAPPINGrlr DeprecationActionr7)r8docker_registry_args r;AddDockerRegistryFlagsruJsX++,3356  & &':BZ[!!&)racURSS9nURS[R"[[ 5SS9 URSSSS 9 g ) z(Adds flags for configuring the CMEK key.Trz --kms-keya Sets the user managed KMS crypto key used to encrypt the Cloud Function and its resources. The KMS crypto key name should match the pattern `projects/${PROJECT}/locations/${LOCATION}/keyRings/${KEYRING}/cryptoKeys/${CRYPTOKEY}` where ${PROJECT} is the project, ${LOCATION} is the location of the key ring, and ${KEYRING} is the key ring that contains the ${CRYPTOKEY} crypto key. If this flag is set, then a Docker repository created in Artifact Registry must be specified using the `--docker-repository` flag and the repository must be encrypted using the `same` KMS key. rz--clear-kms-keyrzF Clears the KMS crypto key used to encrypt the function. rN)rhrir RegexpValidator_KMS_KEY_NAME_PATTERN_KMS_KEY_NAME_ERRORr8 kmskey_groups r;AddKMSKeyFlagsr|_sd!!!-,  & & !4  (  racURSS9nURS[R"[[ 5SS9 URSSSS 9 g ) zDAdds flags for configuring the Docker repository for Cloud Function.Trz--docker-repositorya Sets the Docker repository to be used for storing the Cloud Function's Docker images while the function is being deployed. `DOCKER_REPOSITORY` must be an Artifact Registry Docker repository present in the `same` project and location as the Cloud Function. **Preview:** for 2nd gen functions, a Docker Artifact registry repository in a different project and/or location may be used. Additional requirements apply, see https://cloud.google.com/functions/docs/building#image_registry The repository name should match one of these patterns: * `projects/${PROJECT}/locations/${LOCATION}/repositories/${REPOSITORY}`, * `{LOCATION}-docker.pkg.dev/{PROJECT}/{REPOSITORY}`. where `${PROJECT}` is the project, `${LOCATION}` is the location of the repository and `${REPOSITORY}` is a valid repository ID. rz--clear-docker-repositoryrzJ Clears the Docker repository configuration of the function. rN)rhrir rw_DOCKER_REPOSITORY_NAME_PATTERN_DOCKER_REPOSITORY_NAME_ERRORrzs r;AddDockerRepositoryFlagsrsd!!!-,  & & )+H  2!  racLURS[R"SSS9SS9 g)Nz --concurrencyri)r upper_boundzSet the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified to receive the server default value.r)rir rrs r;AddConcurrencyFlagrs-  ! !aT B # racURSSS9nUR5nURSSSS9 [U5 URSSS S9 URS SS S9 URS SS S9 URSSSS9 g)z$Adds upgrade related function flags.Ta  Upgrade a 1st gen Cloud Function to the 2nd gen environment. You must specify one of the following flags: - `--setup-config` and optionally `--trigger-service-account`, - `--redirect-traffic`, - `--rollback-traffic`, - `--commit`, - `--abort`. )rrfz--setup-configrzhSets up the function upgrade config by creating a 2nd gen copy of the function's code and configuration.rz--redirect-trafficzARedirects production traffic to the 2nd gen copy of the function.z--rollback-trafficzRolls back production traffic to the original 1st gen copy of the function. The 2nd gen copy will still be available for testing.z--commitz_Finishes the upgrade process and permanently deletes the original 1st gen copy of the function.z--abortzUndoes all steps of the upgrade process done so far. All traffic will point to the original 1st gen function copy and the 2nd gen function copy will be deleted.N)rhrrirW)r8 upgrade_groupsetup_config_groups r;AddUpgradeFlagsrs""  # -%779!!  4 "12  N   M   +   , rac[US5$)NrY_ValidateJsonOrRaiseErrordatas r;rZrZs "4 22rac[US5$)Nr]rrs r;r^r^s "4 99rac[R"U5 U$![a3n[R"US[ R "U5-5eSnAff=f)zEChecks validity of json string or raises an InvalidArgumentException.zIs not a valid JSON: N)jsonloads ValueErrorr InvalidArgumentExceptionsix text_type)rarg_namees r;rrsOJJt K   - -)CMM!,<< s A.AAcdURSS9nURSSS9 URSSSS 9 g ) zHAdds flags for configuring the build service account for Cloud Function.Trz--build-service-accounta+ IAM service account whose credentials will be used for the build step. Must be of the format projects/${PROJECT_ID}/serviceAccounts/${ACCOUNT_EMAIL_ADDRESS}. If not provided, the function will use the project's default service account for Cloud Build. rgz--clear-build-service-accountrz8 Clears the build service account field. rNrrs r;AddBuildServiceAccountFlagrsP  t ,+   %  racdURSS9nURSSS9 URSSSS 9 g ) zBAdd flag for specifying Binary Authorization Policy to the parser.Trz--binary-authorizationz Name of the Binary Authorization policy that the function image should be checked against when deploying to Cloud Run. Example: default The flag is only applicable to 2nd gen functions. rgz--clear-binary-authorizationrz< Clears the Binary Authorization policy field. rNrrs r; AddBinaryAuthorizationMutexGrouprsP  t ,+   $  ra)TFF)rrT)}r7 __future__rrrrargcomplete.completersr#googlecloudsdk.api_lib.functions.v1rr#googlecloudsdk.api_lib.functions.v2rr*googlecloudsdk.callioper r r r googlecloudsdk.calliope.conceptsr r#googlecloudsdk.command_lib.eventarcrrgooglecloudsdk.command_lib.utilr(googlecloudsdk.command_lib.util.conceptsrrgooglecloudsdk.corerrrgooglecloudsdk.core.consolerrrSrTr[SIGNATURE_TYPESr5rDr?rIINGRESS_SETTINGS_MAPPINGEGRESS_SETTINGS_MAPPING"DIRECT_VPC_EGRESS_SETTINGS_MAPPINGSECURITY_LEVEL_MAPPINGrxry(_DOCKER_REPOSITORY_NAME_RESOURCE_PATTERN#_DOCKER_REPOSITORY_NAME_PKG_PATTERNr~r~rrrrkr<rArFrKr`rnrzrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr ListCommandCompleterrPropertyFallthroughr r<rrArGrrKrQrSrUrWr[r_rarergrnrur|rrrrZr^rrrrrar;rsI&' 7@C+/(.51G6DG#*)2  221 ' (%0@!#45*21 '<#&" %( " 2 P)O$#,"2"2,'# A/, ! " + * )"2J)"2   EHM<: $*K\& !H     , * ". 4(vr88$00$N  6:.   "    $**@"J 7t3:,ra