.TH "GCLOUD_ALPHA_FUNCTIONS_LOCAL_CALL" 1



.SH "NAME"
.HP
gcloud alpha functions local call \- call a locally deployed Google Cloud Function



.SH "SYNOPSIS"
.HP
\f5gcloud alpha functions local call\fR \fINAME\fR [\fB\-\-cloud\-event\fR=\fICLOUD_EVENT\fR\ |\ \fB\-\-data\fR=\fIDATA\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR \f5gcloud alpha functions local call\fR Call a locally deployed
Google Cloud Function.



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINAME\fR

Name of the locally deployed Google Cloud function.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-cloud\-event\fR=\fICLOUD_EVENT\fR

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.

.TP 2m
\fB\-\-data\fR=\fIDATA\fR

JSON string with data that will be passed to the function.


.RE
.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist.