gcloud alpha emulators datastore env-init
Stay organized with collections
Save and categorize content based on your preferences.
- NAME
-
- gcloud alpha emulators datastore env-init - print the commands required to export env variables of a datastore
- SYNOPSIS
-
-
gcloud alpha emulators datastore env-init[--data-dir=DATA_DIR] [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
-
(ALPHA)Prints the commands but does not execute them. It will output in shell syntax or on Windows it will be in cmd.exe syntax. - EXAMPLES
-
To print the env variables exports for a datastore emulator, run:
gcloudalphaemulatorsdatastoreenv-init--data-dir=DATA-DIRYou can use this command to set env vars in a bash script by adding the below line in the script.
eval$(gcloudalphaemulatorsdatastoreenv-init--data-dir=DATA-DIR)
- FLAGS
-
--data-dir=DATA_DIR-
The directory to be used to store/retrieve data/config for an emulator run. The
default value is
<USER_CONFIG_DIR>/emulators/datastore. The value of USER_CONFIG_DIR can be found by running:gcloudinfo --format='get(config.paths.global_config_dir)'
- 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
$ gcloud helpfor details. - 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. This variant is also available:
gcloudbetaemulatorsdatastoreenv-init