gcloud compute security-policies export Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud compute security-policies export - export security policy configs into YAML or JSON files
- SYNOPSIS
gcloud compute security-policies exportNAME--file-name=FILE_NAME[--file-format=FILE_FORMAT][--global|--region=REGION][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
gcloud compute security-policies exportexports all data associatedwith Compute Engine security policy into a local file.- EXAMPLES
- To export a security policy in JSON format to a given file, run:
gcloudcomputesecurity-policiesexportmy-policy--file-name=my-file-name--file-format=json - POSITIONAL ARGUMENTS
NAME- Name of the security policy to export.
- REQUIRED FLAGS
--file-name=FILE_NAME- The name of the file to export the security policy config to.
- OPTIONAL FLAGS
--file-format=FILE_FORMAT- The format of the file to export the security policy config to. Specify eitheryaml or json. Defaults to yaml if not specified.
FILE_FORMATmust be one of:json,yaml. - At most one of these can be specified:
--global- If set, the security policy is global.
--region=REGION- Region of the security policy to export. Overrides the default
compute/regionproperty value for this command invocation.
- 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
- These variants are also available:
gcloudalphacomputesecurity-policiesexportgcloudbetacomputesecurity-policiesexport
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-05-07 UTC.