NAME

gcloud compute target-http-proxies import - import a target HTTP proxy

SYNOPSIS

gcloud compute target-http-proxies import NAME [--source=SOURCE] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION

Imports a target HTTP proxy's configuration from a file.

EXAMPLES

A target HTTP proxy can be imported by running:

$ gcloud compute target-http-proxies import NAME \ --source=<path-to-file>

POSITIONAL ARGUMENTS

NAME

Name of the target HTTP proxy to import.

FLAGS

--source=SOURCE

Path to a YAML file containing configuration export data. Alternatively, you may omit this flag to read from standard input.For a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpProxy.yaml.

Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory.

At most one of these can be specified:
--global

If set, the target HTTP proxy is global.

--region=REGION

Region of the target HTTP proxy to import. If not specified, you might be prompted to select a region (interactive mode only).

To avoid prompting when this flag is omitted, you can set the compute/region property:

$ gcloud config set compute/region REGION

A list of regions can be fetched by running:

$ gcloud compute regions list

To unset the property, run:

$ gcloud config unset compute/region

Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION.

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 help for details.

NOTES

These variants are also available:

$ gcloud alpha compute target-http-proxies import

$ gcloud beta compute target-http-proxies import