gcloud composer environments storage plugins export

NAME
gcloud composer environments storage plugins export - export plugins from an environment into local storage or Cloud Storage
SYNOPSIS
gcloud composer environments storage plugins export--destination=DESTINATION(--environment=ENVIRONMENT :--location=LOCATION)[--source=SOURCE][GCLOUD_WIDE_FLAG]
DESCRIPTION
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 pluginsdirectory will be exported. Colliding files in the DESTINATION will beoverwritten. If a file exists in the DESTINATION but there is no correspondingfile to overwrite it, it is untouched.
EXAMPLES
Suppose the environmentmyenv's Cloud Storage bucket has thefollowing 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:

gcloudcomposerenvironmentsstoragepluginsexportmyenv--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 overwrittenwith the contents of the corresponding files in the Cloud Storage bucket.

If instead we had run

gcloudcomposerenvironmentsstoragepluginsexportmyenvfile2.pysubdir1/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' insteadof 'foo/subdir1/file3.py'.

REQUIRED FLAGS
--destination=DESTINATION
The path to an existing local directory or a Cloud Storage bucket/directory intowhich to export files.
Environment resource - The environment from whose Cloud Storage bucket to exportplugins.. The arguments in this group can be used to specify the attributes ofthis resource. (NOTE) Some attributes are not given arguments in this group butcan be set in other ways.

To set theproject attribute:

  • provide the argument--environment on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

--environment=ENVIRONMENT
ID of the environment or fully qualified identifier for the environment.

To set theenvironment attribute:

  • provide the argument--environment on the command line.

This flag argument must be specified if any of the other arguments in this groupare specified.

--location=LOCATION
Region where Composer environment runs or in which to create the environment.

To set thelocation attribute:

  • provide the argument--environment on the command line with a fullyspecified name;
  • provide the argument--location on the command line;
  • set the propertycomposer/location.
OPTIONAL FLAGS
--source=SOURCE
An optional relative path to a file or directory to be exported from theplugins/ subdirectory in the environment's Cloud Storage bucket.
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:
gcloudalphacomposerenvironmentsstoragepluginsexport
gcloudbetacomposerenvironmentsstoragepluginsexport

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-22 UTC.