gcloud: Thu Nov 9 11:45:52 UTC 2023

2026-07-18 14:56:05 +00:00 · 2023-11-09 11:45:52 +00:00 · 2023-11-09 11:45:52 +00:00 · 03f0979970
commit 03f0979970
parent f2c5d1d45f
300 changed files with 8569 additions and 1319 deletions
--- a/gcloud/alpha/deploy/automations/export
+++ b/gcloud/alpha/deploy/automations/export
@ -0,0 +1,87 @@
+NAME
+    gcloud alpha deploy automations export - returns the YAML definition of the
+        specified Automation
+
+SYNOPSIS
+    gcloud alpha deploy automations export
+        (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION)
+        [--destination=DESTINATION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) The exported yaml definition can be applied by using the deploy
+    apply command.
+
+EXAMPLES
+    To return the YAML definition of the automation test-automation of delivery
+    pipeline test-pipeline, in region us-central1, run:
+
+        $ gcloud alpha deploy automations export test-automation \
+            --delivery-pipeline=test-pipeline --region=us-central1
+
+POSITIONAL ARGUMENTS
+     Automation resource - The name of the Automation. 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 automation 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.
+
+       AUTOMATION
+          ID of the automation or fully qualified identifier for the
+          automation.
+
+          To set the name attribute:
+          ▸ provide the argument automation on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --delivery-pipeline=DELIVERY_PIPELINE
+          The delivery pipeline associated with the automation. Alternatively,
+          set the property [deploy/delivery-pipeline].
+
+          To set the delivery-pipeline attribute:
+          ▸ provide the argument automation on the command line with a fully
+            specified name;
+          ▸ provide the argument --delivery-pipeline on the command line;
+          ▸ set the property deploy/delivery_pipeline.
+
+       --region=REGION
+          The Cloud region for the automation. Alternatively, set the property
+          [deploy/region].
+
+          To set the region attribute:
+          ▸ provide the argument automation on the command line with a fully
+            specified name;
+          ▸ provide the argument --region on the command line;
+          ▸ set the property deploy/region.
+
+FLAGS
+     --destination=DESTINATION
+        Path to a YAML file where the configuration will be exported.
+        Alternatively, you may omit this flag to write to standard output.
+
+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
+    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. These variants are also available:
+
+        $ gcloud deploy automations export
+
+        $ gcloud beta deploy automations export
+