1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 12:22:03 +00:00

gcloud: Thu Jun 6 09:19:36 UTC 2024

This commit is contained in:
Automated 2024-06-06 09:19:36 +00:00
parent 595ac8640a
commit 40ba53d37f
93 changed files with 3117 additions and 305 deletions

View file

@ -0,0 +1,111 @@
NAME
gcloud composer environments check-upgrade - check that upgrading a Cloud
Composer environment does not result in PyPI module conflicts
SYNOPSIS
gcloud composer environments check-upgrade
(ENVIRONMENT : --location=LOCATION) [--async]
[--airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Check that upgrading a Cloud Composer environment does not result in PyPI
module conflicts.
EXAMPLES
To check that upgrading to the 'composer-1.16.5-airflow-1.10.15' image in a Cloud Composer environment named 'env-1' does not cause
PyPI package conflicts,
run:
$ gcloud composer environments check-upgrade env-1 \
--image-version=composer-1.16.5-airflow-1.10.15
POSITIONAL ARGUMENTS
Environment resource - The environment to check upgrade for. 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
ID of the environment or fully qualified identifier for the
environment.
To set the environment attribute:
▸ provide the argument environment on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Region where Composer environment runs or in which to create the
environment.
To set the location attribute:
▸ provide the argument environment on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property composer/location.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
Group of arguments for performing in-place environment upgrades.
At most one of these can be specified:
--airflow-version=AIRFLOW_VERSION
Upgrade the environment to a later Apache Airflow version in-place.
Must be of the form X[.Y[.Z]], where [] denotes optional fragments.
Examples: 2, 2.3, 2.3.4.
The Apache Airflow version is a semantic version or an alias in the
form of major or major.minor version numbers, resolved to the latest
matching Apache Airflow version supported in the current Cloud
Composer version. The resolved version is stored in the upgraded
environment.
--image-version=IMAGE_VERSION
Upgrade the environment to a later version in-place.
The image version encapsulates the versions of both Cloud Composer
and Apache Airflow. Must be of the form
composer-A[.B.C[-D.E]]-airflow-X[.Y[.Z]], where [] denotes optional
fragments.
Examples: composer-2-airflow-2, composer-2-airflow-2.2,
composer-2.1.2-airflow-2.3.4.
The Cloud Composer portion of the image version is a semantic version
or an alias in the form of major version number or latest, resolved
to the current Cloud Composer version. The Apache Airflow portion of
the image version is a semantic version or an alias in the form of
major or major.minor version numbers, resolved to the latest matching
Apache Airflow version supported in the given Cloud Composer version.
The resolved versions are stored in the upgraded environment.
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:
$ gcloud alpha composer environments check-upgrade
$ gcloud beta composer environments check-upgrade

View file

@ -31,6 +31,10 @@ GROUPS
COMMANDS
COMMAND is one of the following:
check-upgrade
Check that upgrading a Cloud Composer environment does not result in
PyPI module conflicts.
create
Create and initialize a Cloud Composer environment.
@ -52,6 +56,10 @@ COMMANDS
list-packages
List all PyPI modules installed in an Airflow worker.
list-upgrades
List the Cloud Composer image version upgrades for a specific
environment.
run
Run an Airflow sub-command remotely in a Cloud Composer environment.

View file

@ -0,0 +1,92 @@
NAME
gcloud composer environments list-upgrades - list the Cloud Composer image
version upgrades for a specific environment
SYNOPSIS
gcloud composer environments list-upgrades
(ENVIRONMENT : --location=LOCATION) [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud composer environments list-upgrades prints a table listing the
suggested image-version upgrades with the following columns:
▪ Image Version ID
▪ Composer 'default' flag
▪ List of supported python versions
POSITIONAL ARGUMENTS
Environment resource - The environment to list upgrades. 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
ID of the environment or fully qualified identifier for the
environment.
To set the environment attribute:
▸ provide the argument environment on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Region where Composer environment runs or in which to create the
environment.
To set the location attribute:
▸ provide the argument environment on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property composer/location.
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.
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:
$ gcloud alpha composer environments list-upgrades
$ gcloud beta composer environments list-upgrades