gcloud beta deploy automation-runs list

NAME
gcloud beta deploy automation-runs list - list the Automation Runs
SYNOPSIS
gcloud beta deploy automation-runs list [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,…]] [--uri] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(BETA) List the automation runs for a specified delivery pipeline.
EXAMPLES
To list the automation runs for delivery pipeline 'test-pipeline' in region 'us-central1', run: 
gcloud beta deploy automation-runs list --delivery-pipeline=test-pipeline --region=us-central1
FLAGS
Delivery pipeline resource - The delivery pipeline for which you want to list the automation runs. 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 --delivery-pipeline on the command line with a fully specified name;
  • set the property deploy/delivery_pipeline with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.
--delivery-pipeline=DELIVERY_PIPELINE
ID of the delivery_pipeline or fully qualified identifier for the delivery_pipeline.

To set the delivery-pipeline attribute:

  • provide the argument --delivery-pipeline on the command line;
  • set the property deploy/delivery_pipeline.
--region=REGION
Location of the delivery_pipeline. To set the region attribute:
  • provide the argument --delivery-pipeline on the command line with a fully specified name;
  • set the property deploy/delivery_pipeline with a fully specified name;
  • provide the argument --region on the command line;
  • set the property deploy/region.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed. If the expression evaluates True, then that item is listed. For more details and examples of filter expressions, run $ gcloud topic filters. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag specifies the maximum number of resources per page. The default is determined by the service if it supports paging, otherwise it is unlimited (no paging). Paging may be applied before or after --filter and --limit depending on the service.
--sort-by=[FIELD,…]
Comma-separated list of resource field key names to sort by. The default order is ascending. Prefix a field with ``~´´ for descending order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit.
--uri
Print a list of resource URIs instead of the default output, and change the command output to a list of URIs. If this flag is used with --format, the formatting is applied on this URI list. To display URIs alongside other keys instead, use the uri() transform.
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.

API REFERENCE
This command uses the clouddeploy/v1 API. The full documentation for this API can be found at: https://cloud.google.com/deploy/
NOTES
This command is currently in beta and might change without notice. These variants are also available: 
gcloud deploy automation-runs list
 
gcloud alpha deploy automation-runs list