gcloud alpha spanner samples backend - run the backend gRPC service for the given Cloud Spanner sample app
gcloud alpha spanner samples backend APPNAME --instance-id=INSTANCE_ID [--database-id=DATABASE_ID] [--duration=DURATION; default="1h"] [--port=PORT] [GCLOUD_WIDE_FLAG ...]
(ALPHA) This command starts the backend gRPC service for the given sample application. Before starting the service, create the database and load any initial data with:
$ gcloud alpha spanner samples init APPNAME --instance-id=INSTANCE_ID
After starting the service, generate traffic with:
$ gcloud alpha spanner samples workload APPNAME
To run all three steps together, use:
$ gcloud alpha spanner samples run APPNAME --instance-id=INSTANCE_ID
To run the backend gRPC service for the 'finance' sample app using instance 'my-instance', run:
$ gcloud alpha spanner samples backend finance \ --instance-id=my-instance
- APPNAME
The sample app name, e.g. "finance".
- --instance-id=INSTANCE_ID
The Cloud Spanner instance ID for the sample app.
- --database-id=DATABASE_ID
The Cloud Spanner database ID for the sample app.
- --duration=DURATION; default="1h"
Duration of time allowed to run before stopping the service.
- --port=PORT
Port on which to receive gRPC requests.
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 $ gcloud help for details.
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. These variants are also available:
$ gcloud spanner samples backend
$ gcloud beta spanner samples backend