gcloud_beta_composer_environments_storage_plugins

gcloud_beta_composer_environments_storage_plugins_export (1)

NAME

: gcloud beta composer environments storage plugins export - export plugins from an environment into local storage or Cloud Storage

SYNOPSIS

gcloud beta composer environments storage plugins export --destination=DESTINATION (--environment=ENVIRONMENT : --location=LOCATION) [--source=SOURCE] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION

(BETA) If the SOURCE is a directory, it and its contents are are exported

recursively. If no SOURCE is provided, the entire contents of the environment's plugins directory will be exported. Colliding files in the DESTINATION will be overwritten. If a file exists in the DESTINATION but there is no corresponding file to overwrite it, it is untouched.

REQUIRED FLAGS

--destination=DESTINATION

The path to an existing local directory or a Cloud Storage bucket/directory into which to export files.

Environment resource - The environment from whose Cloud Storage bucket to export plugins.. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the [project] attribute: provide the argument [--environment] on the command line with a fully specified name; provide the argument [--project] on the command line; set the property [core/project]. This must be specified.

--environment=ENVIRONMENT: ID of the environment or fully qualified identifier for the environment. This flag must be specified if any of the other arguments in this group are specified.
--location=LOCATION: Compute Engine region in which to create the environment.

OPTIONAL FLAGS

--source=SOURCE: An optional relative path to a file or directory to be exported from the plugins/ subdirectory in the environment's Cloud Storage bucket.

GCLOUD WIDE FLAGS

These flags are available to all commands: --account, --configuration, --flags-file, --flatten, --format, --help, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details.

EXAMPLES

Suppose the environment myenv's Cloud Storage bucket has the following structure:

: gs://the-bucket | +-- plugins | | | +-- file1.py | +-- file2.py | | | +-- subdir1 | | | | | +-- file3.py | | +-- file4.py

And the local directory '/foo' has the following structure:

: /foo | +-- file1.py +-- fileX.py | | | +-- subdir1 | | | | | +-- file3.py | | +-- fileY.py

The following command:

: gcloud beta composer environments storage plugins export myenv --destination /foo

would result in the following structure in the local '/foo' directory:

: /foo | +-- file1.py +-- file2.py +-- fileX.py | | | +-- subdir1 | | | | | +-- file3.py | | +-- file4.py | | +-- fileY.py

The local files '/foo/file1.py' and '/foo/subdir1/file3.py' will be overwritten with the contents of the corresponding files in the Cloud Storage bucket.
If instead we had run

: gcloud beta composer environments storage plugins export myenv file2.py subdir1/file3.py --destination /foo

the resulting local directory structure would be the following:

: /foo | +-- file1.py +-- file3.py +-- fileX.py | | | +-- subdir1 | | | | | +-- file3.py | | +-- fileY.py

No local files would be overwritten since 'gs://the-bucket/dags/subdir1/file3.py' was written to '/foo/file3.py' instead of 'foo/subdir1/file3.py'.

NOTES

This command is currently in BETA and may change without notice. These variants are also available:

: $ gcloud composer environments storage plugins export $ gcloud alpha composer environments storage plugins export

gcloud_beta_composer_environments_storage_plugins_export • man page

gcloud_beta_composer_environments_storage_plugins_export • man page