diff --git a/gcloud/_version b/gcloud/_version index 1daf73684..f1d9c0438 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 467.0.0 -alpha 2024.02.29 -beta 2024.02.29 +Google Cloud SDK 468.0.0 +alpha 2024.03.08 +beta 2024.03.08 bq 2.0.101 bundled-python3-unix 3.11.8 -core 2024.02.29 +core 2024.03.08 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/alpha/alloydb/backups/create b/gcloud/alpha/alloydb/backups/create index 3eeb29fff..d1980c450 100644 --- a/gcloud/alpha/alloydb/backups/create +++ b/gcloud/alpha/alloydb/backups/create @@ -1,5 +1,5 @@ NAME - gcloud alpha alloydb backups create - creates a new AlloyDB backup within a + gcloud alpha alloydb backups create - create a new AlloyDB backup within a given project SYNOPSIS @@ -10,7 +10,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Creates a new AlloyDB backup within a given project. + (ALPHA) Create a new AlloyDB backup within a given project. EXAMPLES To create a new backup, run: diff --git a/gcloud/alpha/alloydb/backups/help b/gcloud/alpha/alloydb/backups/help index 4d06f5e2f..15edea1d1 100644 --- a/gcloud/alpha/alloydb/backups/help +++ b/gcloud/alpha/alloydb/backups/help @@ -18,7 +18,7 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Creates a new AlloyDB backup within a given project. + (ALPHA) Create a new AlloyDB backup within a given project. delete (ALPHA) Deletes an AlloyDB backup within a given project. diff --git a/gcloud/alpha/apphub/applications/add-iam-policy-binding b/gcloud/alpha/apphub/applications/add-iam-policy-binding index 9a1f4167a..67a33e373 100644 --- a/gcloud/alpha/apphub/applications/add-iam-policy-binding +++ b/gcloud/alpha/apphub/applications/add-iam-policy-binding @@ -82,5 +82,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications add-iam-policy-binding diff --git a/gcloud/alpha/apphub/applications/create b/gcloud/alpha/apphub/applications/create index c33a32e1e..a862e9eb1 100644 --- a/gcloud/alpha/apphub/applications/create +++ b/gcloud/alpha/apphub/applications/create @@ -122,5 +122,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications create diff --git a/gcloud/alpha/apphub/applications/delete b/gcloud/alpha/apphub/applications/delete index f0bf3e89a..f12b6693f 100644 --- a/gcloud/alpha/apphub/applications/delete +++ b/gcloud/alpha/apphub/applications/delete @@ -61,5 +61,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications delete diff --git a/gcloud/alpha/apphub/applications/describe b/gcloud/alpha/apphub/applications/describe index 477a96857..5bd00bcaf 100644 --- a/gcloud/alpha/apphub/applications/describe +++ b/gcloud/alpha/apphub/applications/describe @@ -57,5 +57,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications describe diff --git a/gcloud/alpha/apphub/applications/get-iam-policy b/gcloud/alpha/apphub/applications/get-iam-policy index c4c9bca9b..dbd70f7b9 100644 --- a/gcloud/alpha/apphub/applications/get-iam-policy +++ b/gcloud/alpha/apphub/applications/get-iam-policy @@ -88,5 +88,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications get-iam-policy diff --git a/gcloud/alpha/apphub/applications/help b/gcloud/alpha/apphub/applications/help index 6b1e6e8e9..f3a0092f4 100644 --- a/gcloud/alpha/apphub/applications/help +++ b/gcloud/alpha/apphub/applications/help @@ -56,5 +56,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications diff --git a/gcloud/alpha/apphub/applications/list b/gcloud/alpha/apphub/applications/list index 4c820a327..aefaefde4 100644 --- a/gcloud/alpha/apphub/applications/list +++ b/gcloud/alpha/apphub/applications/list @@ -77,5 +77,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications list diff --git a/gcloud/alpha/apphub/applications/remove-iam-policy-binding b/gcloud/alpha/apphub/applications/remove-iam-policy-binding index 44e98275a..c92134fc4 100644 --- a/gcloud/alpha/apphub/applications/remove-iam-policy-binding +++ b/gcloud/alpha/apphub/applications/remove-iam-policy-binding @@ -83,5 +83,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications remove-iam-policy-binding diff --git a/gcloud/alpha/apphub/applications/services/create b/gcloud/alpha/apphub/applications/services/create index 017f6ff31..659e861fe 100644 --- a/gcloud/alpha/apphub/applications/services/create +++ b/gcloud/alpha/apphub/applications/services/create @@ -149,5 +149,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications services create diff --git a/gcloud/alpha/apphub/applications/services/delete b/gcloud/alpha/apphub/applications/services/delete index 512ad6f13..e879afe96 100644 --- a/gcloud/alpha/apphub/applications/services/delete +++ b/gcloud/alpha/apphub/applications/services/delete @@ -72,5 +72,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications services delete diff --git a/gcloud/alpha/apphub/applications/services/describe b/gcloud/alpha/apphub/applications/services/describe index a4b685198..630d2dab8 100644 --- a/gcloud/alpha/apphub/applications/services/describe +++ b/gcloud/alpha/apphub/applications/services/describe @@ -67,5 +67,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications services describe diff --git a/gcloud/alpha/apphub/applications/services/help b/gcloud/alpha/apphub/applications/services/help index 266f1826a..e33ce9775 100644 --- a/gcloud/alpha/apphub/applications/services/help +++ b/gcloud/alpha/apphub/applications/services/help @@ -35,5 +35,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications services diff --git a/gcloud/alpha/apphub/applications/services/list b/gcloud/alpha/apphub/applications/services/list index 11fd24fee..3f37ad037 100644 --- a/gcloud/alpha/apphub/applications/services/list +++ b/gcloud/alpha/apphub/applications/services/list @@ -92,5 +92,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications services list diff --git a/gcloud/alpha/apphub/applications/services/update b/gcloud/alpha/apphub/applications/services/update index f3ecfc4a0..6c6454212 100644 --- a/gcloud/alpha/apphub/applications/services/update +++ b/gcloud/alpha/apphub/applications/services/update @@ -122,5 +122,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications services update diff --git a/gcloud/alpha/apphub/applications/set-iam-policy b/gcloud/alpha/apphub/applications/set-iam-policy index 5cb93ecc6..4e474371e 100644 --- a/gcloud/alpha/apphub/applications/set-iam-policy +++ b/gcloud/alpha/apphub/applications/set-iam-policy @@ -73,5 +73,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications set-iam-policy diff --git a/gcloud/alpha/apphub/applications/update b/gcloud/alpha/apphub/applications/update index 088d7db42..eb4946da2 100644 --- a/gcloud/alpha/apphub/applications/update +++ b/gcloud/alpha/apphub/applications/update @@ -114,5 +114,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications update diff --git a/gcloud/alpha/apphub/applications/workloads/create b/gcloud/alpha/apphub/applications/workloads/create index cae81896e..177a16b97 100644 --- a/gcloud/alpha/apphub/applications/workloads/create +++ b/gcloud/alpha/apphub/applications/workloads/create @@ -149,5 +149,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications workloads create diff --git a/gcloud/alpha/apphub/applications/workloads/delete b/gcloud/alpha/apphub/applications/workloads/delete index 8137e00ca..62075085d 100644 --- a/gcloud/alpha/apphub/applications/workloads/delete +++ b/gcloud/alpha/apphub/applications/workloads/delete @@ -72,5 +72,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications workloads delete diff --git a/gcloud/alpha/apphub/applications/workloads/describe b/gcloud/alpha/apphub/applications/workloads/describe index 636523e32..678de73bf 100644 --- a/gcloud/alpha/apphub/applications/workloads/describe +++ b/gcloud/alpha/apphub/applications/workloads/describe @@ -67,5 +67,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications workloads describe diff --git a/gcloud/alpha/apphub/applications/workloads/help b/gcloud/alpha/apphub/applications/workloads/help index 83bd20861..4cdb785d8 100644 --- a/gcloud/alpha/apphub/applications/workloads/help +++ b/gcloud/alpha/apphub/applications/workloads/help @@ -35,5 +35,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications workloads diff --git a/gcloud/alpha/apphub/applications/workloads/list b/gcloud/alpha/apphub/applications/workloads/list index ada872e81..d4e9d24cd 100644 --- a/gcloud/alpha/apphub/applications/workloads/list +++ b/gcloud/alpha/apphub/applications/workloads/list @@ -92,5 +92,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications workloads list diff --git a/gcloud/alpha/apphub/applications/workloads/update b/gcloud/alpha/apphub/applications/workloads/update index 7917b6c87..9a823df08 100644 --- a/gcloud/alpha/apphub/applications/workloads/update +++ b/gcloud/alpha/apphub/applications/workloads/update @@ -122,5 +122,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub applications workloads update diff --git a/gcloud/alpha/apphub/discovered-services/describe b/gcloud/alpha/apphub/discovered-services/describe index 89753eb56..4b1ad1a77 100644 --- a/gcloud/alpha/apphub/discovered-services/describe +++ b/gcloud/alpha/apphub/discovered-services/describe @@ -60,5 +60,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub discovered-services describe diff --git a/gcloud/alpha/apphub/discovered-services/help b/gcloud/alpha/apphub/discovered-services/help index a1315a5ff..5daaeaac3 100644 --- a/gcloud/alpha/apphub/discovered-services/help +++ b/gcloud/alpha/apphub/discovered-services/help @@ -25,9 +25,14 @@ COMMANDS list (ALPHA) List Apphub discovered services. + lookup + (ALPHA) Lookup an Apphub discovered service with URI. + 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. + access allowlist. This variant is also available: + + $ gcloud apphub discovered-services diff --git a/gcloud/alpha/apphub/discovered-services/list b/gcloud/alpha/apphub/discovered-services/list index 07bd776c4..d10a55b5e 100644 --- a/gcloud/alpha/apphub/discovered-services/list +++ b/gcloud/alpha/apphub/discovered-services/list @@ -79,5 +79,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub discovered-services list diff --git a/gcloud/alpha/apphub/discovered-services/lookup b/gcloud/alpha/apphub/discovered-services/lookup new file mode 100644 index 000000000..0f1d013ba --- /dev/null +++ b/gcloud/alpha/apphub/discovered-services/lookup @@ -0,0 +1,56 @@ +NAME + gcloud alpha apphub discovered-services lookup - lookup an Apphub + discovered service with URI + +SYNOPSIS + gcloud alpha apphub discovered-services lookup --location=LOCATION + --uri=URI [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lookup an Apphub discovered service with URI. + +EXAMPLES + To lookup a discovered service with uri my-service-uri in location us-east1 + run: + + $ gcloud alpha apphub discovered-services lookup \ + --location=us-east1 --uri=my-service-uri + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + --uri=URI + Google Cloud Platform resource URI to look up service for. + +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. This variant is also available: + + $ gcloud apphub discovered-services lookup + diff --git a/gcloud/alpha/apphub/discovered-workloads/describe b/gcloud/alpha/apphub/discovered-workloads/describe index e7ded3b69..95a3f5501 100644 --- a/gcloud/alpha/apphub/discovered-workloads/describe +++ b/gcloud/alpha/apphub/discovered-workloads/describe @@ -60,5 +60,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub discovered-workloads describe diff --git a/gcloud/alpha/apphub/discovered-workloads/help b/gcloud/alpha/apphub/discovered-workloads/help index 48370a266..7d9d50114 100644 --- a/gcloud/alpha/apphub/discovered-workloads/help +++ b/gcloud/alpha/apphub/discovered-workloads/help @@ -25,9 +25,14 @@ COMMANDS list (ALPHA) List Apphub discovered workloads. + lookup + (ALPHA) Lookup an Apphub discovered workload with URI. + 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. + access allowlist. This variant is also available: + + $ gcloud apphub discovered-workloads diff --git a/gcloud/alpha/apphub/discovered-workloads/list b/gcloud/alpha/apphub/discovered-workloads/list index 1f30163b6..35fcde443 100644 --- a/gcloud/alpha/apphub/discovered-workloads/list +++ b/gcloud/alpha/apphub/discovered-workloads/list @@ -79,5 +79,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub discovered-workloads list diff --git a/gcloud/alpha/apphub/discovered-workloads/lookup b/gcloud/alpha/apphub/discovered-workloads/lookup new file mode 100644 index 000000000..1cb0c229a --- /dev/null +++ b/gcloud/alpha/apphub/discovered-workloads/lookup @@ -0,0 +1,56 @@ +NAME + gcloud alpha apphub discovered-workloads lookup - lookup an Apphub + discovered workload with URI + +SYNOPSIS + gcloud alpha apphub discovered-workloads lookup --location=LOCATION + --uri=URI [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lookup an Apphub discovered workload with URI. + +EXAMPLES + To lookup a discovered workload with uri my-workload-uri in location + us-east1 run: + + $ gcloud alpha apphub discovered-workloads lookup \ + --location=us-east1 --uri=my-workload-uri + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + --uri=URI + Google Cloud Platform resource URI to look up workload for. + +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. This variant is also available: + + $ gcloud apphub discovered-workloads lookup + diff --git a/gcloud/alpha/apphub/help b/gcloud/alpha/apphub/help index 0eb394824..569709a58 100644 --- a/gcloud/alpha/apphub/help +++ b/gcloud/alpha/apphub/help @@ -34,5 +34,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub diff --git a/gcloud/alpha/apphub/operations/describe b/gcloud/alpha/apphub/operations/describe index fd33545c9..dd431d916 100644 --- a/gcloud/alpha/apphub/operations/describe +++ b/gcloud/alpha/apphub/operations/describe @@ -56,5 +56,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub operations describe diff --git a/gcloud/alpha/apphub/operations/help b/gcloud/alpha/apphub/operations/help index c98aebb3e..a5a434e41 100644 --- a/gcloud/alpha/apphub/operations/help +++ b/gcloud/alpha/apphub/operations/help @@ -26,5 +26,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub operations diff --git a/gcloud/alpha/apphub/operations/list b/gcloud/alpha/apphub/operations/list index fd4f4a77c..2157326a8 100644 --- a/gcloud/alpha/apphub/operations/list +++ b/gcloud/alpha/apphub/operations/list @@ -78,5 +78,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub operations list diff --git a/gcloud/alpha/apphub/service-projects/add b/gcloud/alpha/apphub/service-projects/add index ba735bad2..fd60b8e88 100644 --- a/gcloud/alpha/apphub/service-projects/add +++ b/gcloud/alpha/apphub/service-projects/add @@ -66,5 +66,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects add diff --git a/gcloud/alpha/apphub/service-projects/describe b/gcloud/alpha/apphub/service-projects/describe index f5590993d..a0407e869 100644 --- a/gcloud/alpha/apphub/service-projects/describe +++ b/gcloud/alpha/apphub/service-projects/describe @@ -61,5 +61,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects describe diff --git a/gcloud/alpha/apphub/service-projects/detach b/gcloud/alpha/apphub/service-projects/detach index b8bf61ea1..cc5bb4899 100644 --- a/gcloud/alpha/apphub/service-projects/detach +++ b/gcloud/alpha/apphub/service-projects/detach @@ -26,5 +26,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects detach diff --git a/gcloud/alpha/apphub/service-projects/help b/gcloud/alpha/apphub/service-projects/help index e2df0cc00..1e037cf59 100644 --- a/gcloud/alpha/apphub/service-projects/help +++ b/gcloud/alpha/apphub/service-projects/help @@ -37,5 +37,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects diff --git a/gcloud/alpha/apphub/service-projects/list b/gcloud/alpha/apphub/service-projects/list index 594128267..1cd892c05 100644 --- a/gcloud/alpha/apphub/service-projects/list +++ b/gcloud/alpha/apphub/service-projects/list @@ -79,5 +79,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects list diff --git a/gcloud/alpha/apphub/service-projects/lookup b/gcloud/alpha/apphub/service-projects/lookup index fc864d247..b884084a1 100644 --- a/gcloud/alpha/apphub/service-projects/lookup +++ b/gcloud/alpha/apphub/service-projects/lookup @@ -26,5 +26,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects lookup diff --git a/gcloud/alpha/apphub/service-projects/remove b/gcloud/alpha/apphub/service-projects/remove index cf53fcd77..9c249ef02 100644 --- a/gcloud/alpha/apphub/service-projects/remove +++ b/gcloud/alpha/apphub/service-projects/remove @@ -67,5 +67,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud apphub service-projects remove diff --git a/gcloud/alpha/builds/connections/create/bitbucket-cloud b/gcloud/alpha/builds/connections/create/bitbucket-cloud new file mode 100644 index 000000000..85f9d1a1c --- /dev/null +++ b/gcloud/alpha/builds/connections/create/bitbucket-cloud @@ -0,0 +1,111 @@ +NAME + gcloud alpha builds connections create bitbucket-cloud - create a Cloud + Build Connection for Bitbucket Cloud + +SYNOPSIS + gcloud alpha builds connections create bitbucket-cloud + (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + --workspace=WORKSPACE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Cloud Build Connection for Bitbucket Cloud. + + A Bitbucket Cloud Connection can be created by using a + repository/project/workspace access token with + repository_read,repository_admin, pullrequest_read, webhook scope + permission and a repository/project/workspace access token with + repository_read scope permission. + +EXAMPLES + To create a Bitbucket Cloud connection, provide all the required + parameters: + + $ gcloud alpha builds connections create bitbucket-cloud \ + my-bitbucket-conn --project=myproj --region=us-central1 \ + --workspace=my-workspace \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read,repository_admin, + pullrequest_read, webhook repository/project/workspace access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read repository/project/workspace + access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Cloud. + + --workspace=WORKSPACE + Workspace of the Bitbucket Cloud instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +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 builds connections create bitbucket-cloud + + $ gcloud beta builds connections create bitbucket-cloud + diff --git a/gcloud/alpha/builds/connections/create/bitbucket-data-center b/gcloud/alpha/builds/connections/create/bitbucket-data-center new file mode 100644 index 000000000..206917e69 --- /dev/null +++ b/gcloud/alpha/builds/connections/create/bitbucket-data-center @@ -0,0 +1,142 @@ +NAME + gcloud alpha builds connections create bitbucket-data-center - create a + Cloud Build Connection for Bitbucket Data Center + +SYNOPSIS + gcloud alpha builds connections create bitbucket-data-center + (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] + [--host-uri=HOST_URI] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE + : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Cloud Build Connection for Bitbucket Data Center. + + A Bitbucket Data Center Connection can be created by using a personal + access token with REPO_ADMIN scope permission. A REPO_READ scoped personal + access token will also be required. + + If the Bitbucket Data Center can only be accessed within a VPC, a Service + Directory service resource can be provided for connecting to it. + +EXAMPLES + To create a Bitbucket Data Center connection, provide all the required + parameters: + + $ gcloud alpha builds connections create bitbucket-data-center \ + my-bitbucket-conn --project=myproj --region=us-central1 \ + --host-uri=https://bitbucket-server.net \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + + To create a Bitbucket Data Center connection for a private Bitbucket Data + Center server. Provide the service-directory-service and ssl-ca-file as + well: + + $ gcloud alpha builds connections create bitbucket-data-center \ + my-private-bitbucket-conn \ + --host-uri=https://my.private-bitbucket-server.net \ + --project=myproj --region=us-central1 \ + --service-directory-service=projects/myproj/namespaces/x/\ + services/mysds --ssl-ca-file=mycertificate.crt \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_ADMIN personal access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_READ personal access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Data Center. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --host-uri=HOST_URI + URI of the Bitbucket Data Center instance. + + Group of arguments for configuring access through Service Directory. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the Bitbucket + Data Center. Necessary only if the server has no public access from + the internet. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +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 builds connections create bitbucket-data-center + + $ gcloud beta builds connections create bitbucket-data-center + diff --git a/gcloud/alpha/builds/connections/create/help b/gcloud/alpha/builds/connections/create/help index c5827bdbc..f7a765aa7 100644 --- a/gcloud/alpha/builds/connections/create/help +++ b/gcloud/alpha/builds/connections/create/help @@ -16,6 +16,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (ALPHA) Create a Cloud Build Connection for Bitbucket Cloud. + + bitbucket-data-center + (ALPHA) Create a Cloud Build Connection for Bitbucket Data Center. + github (ALPHA) Create a Cloud Build Connection of type GitHub. diff --git a/gcloud/alpha/builds/connections/update/bitbucket-cloud b/gcloud/alpha/builds/connections/update/bitbucket-cloud new file mode 100644 index 000000000..53493e57a --- /dev/null +++ b/gcloud/alpha/builds/connections/update/bitbucket-cloud @@ -0,0 +1,106 @@ +NAME + gcloud alpha builds connections update bitbucket-cloud - update a Cloud + Build Connection of type Bitbucket Cloud + +SYNOPSIS + gcloud alpha builds connections update bitbucket-cloud + (CONNECTION : --region=REGION) [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] + [--workspace=WORKSPACE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Cloud Build Connection of type Bitbucket Cloud. + +EXAMPLES + To update the workspace, provide the connection name and the workspace + name: + + $ gcloud alpha builds connections update bitbucket-cloud \ + my-bbc-conn --region=us-west1 --workspace=my-workspace + + To update the authorization token, provide the connection name and the new + authorization token secret version. + + $ gcloud alpha builds connections update bitbucket-cloud \ + my-bbc-conn --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read,repository_admin, + pullrequest_read, webhook access token. It can be a repository, project + or workspace access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read access token. It can be a + repository, project or workspace access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Cloud. + + --workspace=WORKSPACE + Workspace of the Bitbucket Cloud instance. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +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 builds connections update bitbucket-cloud + + $ gcloud beta builds connections update bitbucket-cloud + diff --git a/gcloud/alpha/builds/connections/update/bitbucket-data-center b/gcloud/alpha/builds/connections/update/bitbucket-data-center new file mode 100644 index 000000000..e6290af47 --- /dev/null +++ b/gcloud/alpha/builds/connections/update/bitbucket-data-center @@ -0,0 +1,107 @@ +NAME + gcloud alpha builds connections update bitbucket-data-center - update a + Cloud Build Connection of type Bitbucket Data Center + +SYNOPSIS + gcloud alpha builds connections update bitbucket-data-center + (CONNECTION : --region=REGION) [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--host-uri=HOST_URI] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Cloud Build Connection of type Bitbucket Data Center. + +EXAMPLES + To update the ssl_ca, provide the connection name and the ssl_ca file: + + $ gcloud alpha builds connections update bitbucket-data-center \ + my-gle-conn --region=us-west1 --ssl-ca-file=mycertificate.crt + + To update the authorization token, provide the connection name and the new + authorization token secret version name. + + $ gcloud alpha builds connections update bitbucket-data-center \ + my-gle-conn --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_ADMIN personal access token. + + --host-uri=HOST_URI + URI of the Bitbucket Data Center instance. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_READ personal access token. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the Bitbucket + Data Center. Necessary only if the server has no public access from the + internet. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +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 builds connections update bitbucket-data-center + + $ gcloud beta builds connections update bitbucket-data-center + diff --git a/gcloud/alpha/builds/connections/update/help b/gcloud/alpha/builds/connections/update/help index e9d72fc2f..11dce4625 100644 --- a/gcloud/alpha/builds/connections/update/help +++ b/gcloud/alpha/builds/connections/update/help @@ -16,6 +16,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (ALPHA) Update a Cloud Build Connection of type Bitbucket Cloud. + + bitbucket-data-center + (ALPHA) Update a Cloud Build Connection of type Bitbucket Data Center. + github (ALPHA) Update a Cloud Build Connection of type GitHub. diff --git a/gcloud/alpha/builds/triggers/create/bitbucket-cloud b/gcloud/alpha/builds/triggers/create/bitbucket-cloud new file mode 100644 index 000000000..39e926bcf --- /dev/null +++ b/gcloud/alpha/builds/triggers/create/bitbucket-cloud @@ -0,0 +1,225 @@ +NAME + gcloud alpha builds triggers create bitbucket-cloud - create a build + trigger for a 2nd-gen Bitbucket Cloud repository + +SYNOPSIS + gcloud alpha builds triggers create bitbucket-cloud + (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED"]) (--build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Cloud repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud alpha builds triggers create bitbucket-cloud \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" --region=us-central1 + + To create a pull request trigger with a 2nd-gen repository for main: + + $ gcloud alpha builds triggers create bitbucket-cloud \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ + --pull-request-pattern="^main$" --region=us-central1 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. Note: Region must be specified in 2nd gen repo; global is + not supported. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. For + example: + + $ gcloud alpha builds triggers create bitbucket-cloud ... \ + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + +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 builds triggers create bitbucket-cloud + + $ gcloud beta builds triggers create bitbucket-cloud + diff --git a/gcloud/alpha/builds/triggers/create/bitbucket-data-center b/gcloud/alpha/builds/triggers/create/bitbucket-data-center new file mode 100644 index 000000000..c9893eebc --- /dev/null +++ b/gcloud/alpha/builds/triggers/create/bitbucket-data-center @@ -0,0 +1,226 @@ +NAME + gcloud alpha builds triggers create bitbucket-data-center - create a build + trigger for a 2nd-gen Bitbucket Data Center repository + +SYNOPSIS + gcloud alpha builds triggers create bitbucket-data-center + (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED"]) (--build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Data Center + repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud alpha builds triggers create bitbucket-data-center \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" --region=us-central1 + + To create a pull request trigger with a 2nd-gen repository for main: + + $ gcloud alpha builds triggers create bitbucket-data-center \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ + --pull-request-pattern="^main$" --region=us-central1 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. Note: Region must be specified in 2nd gen repo; global is + not supported. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. For + example: + + $ gcloud alpha builds triggers create bitbucket-data-center ... \ + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + +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 builds triggers create bitbucket-data-center + + $ gcloud beta builds triggers create bitbucket-data-center + diff --git a/gcloud/alpha/builds/triggers/create/help b/gcloud/alpha/builds/triggers/create/help index 3de891bc8..c3b35f643 100644 --- a/gcloud/alpha/builds/triggers/create/help +++ b/gcloud/alpha/builds/triggers/create/help @@ -16,6 +16,14 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Cloud + repository. + + bitbucket-data-center + (ALPHA) Create a build trigger for a 2nd-gen Bitbucket Data Center + repository. + bitbucketserver (ALPHA) Create a build trigger for a Bitbucket Server repository. diff --git a/gcloud/alpha/builds/triggers/update/bitbucket-cloud b/gcloud/alpha/builds/triggers/update/bitbucket-cloud new file mode 100644 index 000000000..7e16fbff1 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/bitbucket-cloud @@ -0,0 +1,255 @@ +NAME + gcloud alpha builds triggers update bitbucket-cloud - updates Bitbucket + Cloud trigger used by Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update bitbucket-cloud + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates Bitbucket Cloud trigger used by Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud alpha builds triggers update bitbucket-cloud my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucket-cloud + + $ gcloud beta builds triggers update bitbucket-cloud + diff --git a/gcloud/alpha/builds/triggers/update/bitbucket-data-center b/gcloud/alpha/builds/triggers/update/bitbucket-data-center new file mode 100644 index 000000000..e4ceee977 --- /dev/null +++ b/gcloud/alpha/builds/triggers/update/bitbucket-data-center @@ -0,0 +1,257 @@ +NAME + gcloud alpha builds triggers update bitbucket-data-center - updates + Bitbucket Data Center trigger used by Cloud Build + +SYNOPSIS + gcloud alpha builds triggers update bitbucket-data-center + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates Bitbucket Data Center trigger used by Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud alpha builds triggers update bitbucket-data-center \ + my-trigger --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud alpha builds triggers update bitbucket-data-center \ + my-trigger --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud alpha builds triggers update bitbucket-data-center \ + my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud alpha builds triggers update bitbucket-data-center \ + my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucket-data-center + + $ gcloud beta builds triggers update bitbucket-data-center + diff --git a/gcloud/alpha/builds/triggers/update/help b/gcloud/alpha/builds/triggers/update/help index d44c7b85b..02d1fb39f 100644 --- a/gcloud/alpha/builds/triggers/update/help +++ b/gcloud/alpha/builds/triggers/update/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (ALPHA) Updates Bitbucket Cloud trigger used by Cloud Build. + + bitbucket-data-center + (ALPHA) Updates Bitbucket Data Center trigger used by Cloud Build. + bitbucketserver (ALPHA) Updates Bitbucket Server trigger used by Cloud Build. diff --git a/gcloud/alpha/compute/health-checks/create/http b/gcloud/alpha/compute/health-checks/create/http index 570dde509..c534a53f2 100644 --- a/gcloud/alpha/compute/health-checks/create/http +++ b/gcloud/alpha/compute/health-checks/create/http @@ -70,14 +70,16 @@ FLAGS response body determines health. Only ASCII characters allowed. --source-regions=REGION,...,[...] - Defines the list of cloud regions from which health checks are - performed. This option can be specified only for health checks used - with DNS Routing Policies. If specified, --check-interval should be at - least 30 seconds. --proxy-header field and --request field (for TCP) - are not supported with this option. source-regions is only allowed for - global health checks. If this option is specified, then the health - check cannot be used with BackendService nor with managed instance - group autohealing. + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the diff --git a/gcloud/alpha/compute/health-checks/create/https b/gcloud/alpha/compute/health-checks/create/https index 7feacd1af..59e843944 100644 --- a/gcloud/alpha/compute/health-checks/create/https +++ b/gcloud/alpha/compute/health-checks/create/https @@ -70,14 +70,16 @@ FLAGS response body determines health. Only ASCII characters allowed. --source-regions=REGION,...,[...] - Defines the list of cloud regions from which health checks are - performed. This option can be specified only for health checks used - with DNS Routing Policies. If specified, --check-interval should be at - least 30 seconds. --proxy-header field and --request field (for TCP) - are not supported with this option. source-regions is only allowed for - global health checks. If this option is specified, then the health - check cannot be used with BackendService nor with managed instance - group autohealing. + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the diff --git a/gcloud/alpha/compute/health-checks/create/tcp b/gcloud/alpha/compute/health-checks/create/tcp index 47ea7c435..91e8ae059 100644 --- a/gcloud/alpha/compute/health-checks/create/tcp +++ b/gcloud/alpha/compute/health-checks/create/tcp @@ -74,14 +74,16 @@ FLAGS --request. --source-regions=REGION,...,[...] - Defines the list of cloud regions from which health checks are - performed. This option can be specified only for health checks used - with DNS Routing Policies. If specified, --check-interval should be at - least 30 seconds. --proxy-header field and --request field (for TCP) - are not supported with this option. source-regions is only allowed for - global health checks. If this option is specified, then the health - check cannot be used with BackendService nor with managed instance - group autohealing. + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the diff --git a/gcloud/alpha/compute/health-checks/update/http b/gcloud/alpha/compute/health-checks/update/http index c5e5a9aa0..7d292797a 100644 --- a/gcloud/alpha/compute/health-checks/update/http +++ b/gcloud/alpha/compute/health-checks/update/http @@ -68,14 +68,16 @@ FLAGS response body determines health. Only ASCII characters allowed. --source-regions=REGION,...,[...] - Defines the list of cloud regions from which health checks are - performed. This option can be specified only for health checks used - with DNS Routing Policies. If specified, --check-interval should be at - least 30 seconds. --proxy-header field and --request field (for TCP) - are not supported with this option. source-regions is only allowed for - global health checks. If this option is specified, then the health - check cannot be used with BackendService nor with managed instance - group autohealing. + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the diff --git a/gcloud/alpha/compute/health-checks/update/https b/gcloud/alpha/compute/health-checks/update/https index 4e1bb10b4..784823bd4 100644 --- a/gcloud/alpha/compute/health-checks/update/https +++ b/gcloud/alpha/compute/health-checks/update/https @@ -69,14 +69,16 @@ FLAGS response body determines health. Only ASCII characters allowed. --source-regions=REGION,...,[...] - Defines the list of cloud regions from which health checks are - performed. This option can be specified only for health checks used - with DNS Routing Policies. If specified, --check-interval should be at - least 30 seconds. --proxy-header field and --request field (for TCP) - are not supported with this option. source-regions is only allowed for - global health checks. If this option is specified, then the health - check cannot be used with BackendService nor with managed instance - group autohealing. + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the diff --git a/gcloud/alpha/compute/health-checks/update/tcp b/gcloud/alpha/compute/health-checks/update/tcp index b9236d6aa..0a1581104 100644 --- a/gcloud/alpha/compute/health-checks/update/tcp +++ b/gcloud/alpha/compute/health-checks/update/tcp @@ -72,14 +72,16 @@ FLAGS response value. --source-regions=REGION,...,[...] - Defines the list of cloud regions from which health checks are - performed. This option can be specified only for health checks used - with DNS Routing Policies. If specified, --check-interval should be at - least 30 seconds. --proxy-header field and --request field (for TCP) - are not supported with this option. source-regions is only allowed for - global health checks. If this option is specified, then the health - check cannot be used with BackendService nor with managed instance - group autohealing. + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 83a1e67c5..90064722d 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -1326,6 +1326,12 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + igmp-query + Determines if the Compute Engine Instance can receive and respond + to IGMP query packets on the specified network interface. + IGMP_QUERY must be one of: IGMP_QUERY_V2, IGMP_QUERY_DISABLED. It + is disabled by default. + --network-interface-from-file=KEY=LOCAL_FILE_PATH Same as --network-interface except that the value for the entry will be read from a local file. This is used in case subinterfaces need to diff --git a/gcloud/alpha/compute/project-info/update b/gcloud/alpha/compute/project-info/update index 6d9b704f1..750b9baed 100644 --- a/gcloud/alpha/compute/project-info/update +++ b/gcloud/alpha/compute/project-info/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha compute project-info update + [--cloud-armor-tier=CLOUD_ARMOR_TIER] [--default-network-tier=DEFAULT_NETWORK_TIER] [--managed-protection-tier=MANAGED_PROTECTION_TIER] [GCLOUD_WIDE_FLAG ...] @@ -13,12 +14,16 @@ DESCRIPTION Compute Engine project resource. FLAGS + --cloud-armor-tier=CLOUD_ARMOR_TIER + Cloud armor tier to assign to the project. CLOUD_ARMOR_TIER must be one + of: CA_STANDARD, CA_ENTERPRISE_PAYGO. + --default-network-tier=DEFAULT_NETWORK_TIER The default network tier to assign to the project. DEFAULT_NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. --managed-protection-tier=MANAGED_PROTECTION_TIER - The maanged protection tier to assign to the project. + Managed protection tier to assign to the project. MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO. GCLOUD WIDE FLAGS diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 338e2297a..ffb34784b 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -241,7 +241,9 @@ OPTIONAL FLAGS --reserved Specifies the request should be scheduled on reserved capacity. - If this flag is set the guaranteed flag is also set. + If --reservation-host-project, --reservation-host-folder, or + --reservation-host-organization are present then this flag has no + effect. --scopes=[SCOPES,...] List of comma-separated scopes to be made available for the service diff --git a/gcloud/alpha/dlp/datasources/bigquery/analyze b/gcloud/alpha/dlp/datasources/bigquery/analyze index 7ffa70f30..634c2aef4 100644 --- a/gcloud/alpha/dlp/datasources/bigquery/analyze +++ b/gcloud/alpha/dlp/datasources/bigquery/analyze @@ -90,7 +90,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/datasources/bigquery/inspect b/gcloud/alpha/dlp/datasources/bigquery/inspect index 8383f2f94..7bb095989 100644 --- a/gcloud/alpha/dlp/datasources/bigquery/inspect +++ b/gcloud/alpha/dlp/datasources/bigquery/inspect @@ -127,7 +127,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/datasources/datastore/inspect b/gcloud/alpha/dlp/datasources/datastore/inspect index 544ba5387..ec6e2d2c1 100644 --- a/gcloud/alpha/dlp/datasources/datastore/inspect +++ b/gcloud/alpha/dlp/datasources/datastore/inspect @@ -120,7 +120,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/datasources/gcs/inspect b/gcloud/alpha/dlp/datasources/gcs/inspect index c3cae9b1d..f2e8e786f 100644 --- a/gcloud/alpha/dlp/datasources/gcs/inspect +++ b/gcloud/alpha/dlp/datasources/gcs/inspect @@ -126,7 +126,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/images/inspect b/gcloud/alpha/dlp/images/inspect index 09930f3ac..fb60f6276 100644 --- a/gcloud/alpha/dlp/images/inspect +++ b/gcloud/alpha/dlp/images/inspect @@ -55,7 +55,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/images/redact b/gcloud/alpha/dlp/images/redact index bb0367623..21da3f39f 100644 --- a/gcloud/alpha/dlp/images/redact +++ b/gcloud/alpha/dlp/images/redact @@ -67,7 +67,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/job-triggers/create b/gcloud/alpha/dlp/job-triggers/create index 47d00f63f..62dccc57e 100644 --- a/gcloud/alpha/dlp/job-triggers/create +++ b/gcloud/alpha/dlp/job-triggers/create @@ -141,7 +141,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/job-triggers/delete b/gcloud/alpha/dlp/job-triggers/delete index 567268545..71192e998 100644 --- a/gcloud/alpha/dlp/job-triggers/delete +++ b/gcloud/alpha/dlp/job-triggers/delete @@ -37,7 +37,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/job-triggers/describe b/gcloud/alpha/dlp/job-triggers/describe index ffb2ebb30..b8439218c 100644 --- a/gcloud/alpha/dlp/job-triggers/describe +++ b/gcloud/alpha/dlp/job-triggers/describe @@ -38,7 +38,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/job-triggers/list b/gcloud/alpha/dlp/job-triggers/list index 1e0ef8261..69e05c7ae 100644 --- a/gcloud/alpha/dlp/job-triggers/list +++ b/gcloud/alpha/dlp/job-triggers/list @@ -51,7 +51,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/jobs/cancel b/gcloud/alpha/dlp/jobs/cancel index 1133072c4..991c4bd07 100644 --- a/gcloud/alpha/dlp/jobs/cancel +++ b/gcloud/alpha/dlp/jobs/cancel @@ -38,7 +38,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/jobs/delete b/gcloud/alpha/dlp/jobs/delete index b313698c6..bc4c1880e 100644 --- a/gcloud/alpha/dlp/jobs/delete +++ b/gcloud/alpha/dlp/jobs/delete @@ -36,7 +36,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/jobs/describe b/gcloud/alpha/dlp/jobs/describe index 40fdee521..94b8436cc 100644 --- a/gcloud/alpha/dlp/jobs/describe +++ b/gcloud/alpha/dlp/jobs/describe @@ -36,7 +36,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/jobs/list b/gcloud/alpha/dlp/jobs/list index 6be00ed72..7ff0a08ef 100644 --- a/gcloud/alpha/dlp/jobs/list +++ b/gcloud/alpha/dlp/jobs/list @@ -56,7 +56,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/text/inspect b/gcloud/alpha/dlp/text/inspect index fac956e5e..6aba2082b 100644 --- a/gcloud/alpha/dlp/text/inspect +++ b/gcloud/alpha/dlp/text/inspect @@ -62,7 +62,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/dlp/text/redact b/gcloud/alpha/dlp/text/redact index 61151c3cd..bc106449c 100644 --- a/gcloud/alpha/dlp/text/redact +++ b/gcloud/alpha/dlp/text/redact @@ -70,7 +70,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the dlp/v2 API. The full documentation for this API can - be found at: https://cloud.google.com/dlp/docs/ + be found at: https://cloud.google.com/sensitive-data-protection/docs/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/create b/gcloud/alpha/edge-cloud/container/clusters/node-pools/create index c95ae5d43..91a65dc45 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/node-pools/create +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/create @@ -8,7 +8,7 @@ SYNOPSIS --node-count=NODE_COUNT --node-location=NODE_LOCATION [--async] [--labels=[KEY=VALUE,...]] [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [GCLOUD_WIDE_FLAG ...] + [--node-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create an Edge Container node pool. @@ -111,6 +111,10 @@ OPTIONAL FLAGS pool. The filtering language accepts strings like "name=", and is documented in more detail at https://google.aip.dev/160. + --node-labels=[KEY=VALUE,...] + Comma-delimited list of key-value pairs that comprise labels for the + individual nodes in the node pool. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/update b/gcloud/alpha/edge-cloud/container/clusters/node-pools/update index 7a32311a5..8629e1100 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/node-pools/update +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha edge-cloud container clusters node-pools update (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [--node-count=NODE_COUNT] [--update-labels=[KEY=VALUE,...]] + [--node-count=NODE_COUNT] [--node-labels=[KEY=VALUE,...]] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +76,10 @@ FLAGS --node-count=NODE_COUNT Default nodeCount used by this node pool. + --node-labels=[KEY=VALUE,...] + Comma-delimited list of key-value pairs that comprise labels for the + individual nodes in the node pool. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/alpha/iam/roles/create b/gcloud/alpha/iam/roles/create index 70e1699e5..02a2576e5 100644 --- a/gcloud/alpha/iam/roles/create +++ b/gcloud/alpha/iam/roles/create @@ -28,17 +28,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to create. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to create. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to create. + Organization of the role you want to create. --project=PROJECT_ID - The project of the role you want to create. + Project of the role you want to create. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/iam/roles/delete b/gcloud/alpha/iam/roles/delete index f5954abe1..42495b20a 100644 --- a/gcloud/alpha/iam/roles/delete +++ b/gcloud/alpha/iam/roles/delete @@ -25,17 +25,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to delete. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to delete. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to delete. + Organization of the role you want to delete. --project=PROJECT_ID - The project of the role you want to delete. + Project of the role you want to delete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/iam/roles/describe b/gcloud/alpha/iam/roles/describe index b578a8534..231071c48 100644 --- a/gcloud/alpha/iam/roles/describe +++ b/gcloud/alpha/iam/roles/describe @@ -32,18 +32,18 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the role to describe. Curated roles example: roles/viewer. - Custom roles example: CustomRole. For custom roles, you must also - specify the --organization or --project flag. + ID of the role to describe. Curated roles example: roles/viewer. Custom + roles example: CustomRole. For custom roles, you must also specify the + --organization or --project flag. FLAGS At most one of these can be specified: --organization=ORGANIZATION - The organization of the role you want to describe. + Organization of the role you want to describe. --project=PROJECT_ID - The project of the role you want to describe. + Project of the role you want to describe. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/iam/roles/list b/gcloud/alpha/iam/roles/list index 24347c78b..0d1811891 100644 --- a/gcloud/alpha/iam/roles/list +++ b/gcloud/alpha/iam/roles/list @@ -34,10 +34,10 @@ FLAGS At most one of these can be specified: --organization=ORGANIZATION - The organization of the role you want to list. + Organization of the role you want to list. --project=PROJECT_ID - The project of the role you want to list. + Project of the role you want to list. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/iam/roles/undelete b/gcloud/alpha/iam/roles/undelete index bcde4e1d3..df5c9ed4e 100644 --- a/gcloud/alpha/iam/roles/undelete +++ b/gcloud/alpha/iam/roles/undelete @@ -28,17 +28,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to undelete. For example: CustomRole. You - must also specify the --organization or --project flag. + ID of the custom role to undelete. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to undelete. + Organization of the role you want to undelete. --project=PROJECT_ID - The project of the role you want to undelete. + Project of the role you want to undelete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/iam/roles/update b/gcloud/alpha/iam/roles/update index 57de46d91..fb06c3c47 100644 --- a/gcloud/alpha/iam/roles/update +++ b/gcloud/alpha/iam/roles/update @@ -25,17 +25,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to update. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to update. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to update. + Organization of the role you want to update. --project=PROJECT_ID - The project of the role you want to update. + Project of the role you want to update. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/alpha/iam/workforce-pools/create-cred-config b/gcloud/alpha/iam/workforce-pools/create-cred-config index 510356e45..d35366ec2 100644 --- a/gcloud/alpha/iam/workforce-pools/create-cred-config +++ b/gcloud/alpha/iam/workforce-pools/create-cred-config @@ -86,13 +86,13 @@ REQUIRED FLAGS OPTIONAL FLAGS --credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME - The subject token field name (key) in a JSON credential source. + Subject token field name (key) in a JSON credential source. --credential-source-headers=[key=value,...] Headers to use when querying the credential-source-url. --credential-source-type=CREDENTIAL_SOURCE_TYPE - The format of the credential source (JSON or text). + Format of the credential source (JSON or text). --subject-token-type=SUBJECT_TOKEN_TYPE The type of token being used for authorization. This defaults to @@ -101,29 +101,29 @@ OPTIONAL FLAGS Arguments for an executable type credential source. --executable-interactive-timeout-millis=EXECUTABLE_INTERACTIVE_TIMEOUT_MILLIS - The timeout duration, in milliseconds, to wait for the executable to + Timeout duration, in milliseconds, to wait for the executable to finish when the command is running in interactive mode. --executable-output-file=EXECUTABLE_OUTPUT_FILE - The absolute path to the file storing the executable response. + Absolute path to the file storing the executable response. --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS - The timeout duration in milliseconds for waiting for the executable - to finish. + Timeout duration, in milliseconds, to wait for the executable to + finish. Service account impersonation options. --service-account=SERVICE_ACCOUNT - The email of the service account to impersonate. + Email of the service account to impersonate. This flag argument must be specified if any of the other arguments in this group are specified. --service-account-token-lifetime-seconds=SERVICE_ACCOUNT_TOKEN_LIFETIME_SECONDS - The desired lifetime duration of the service account access token in - seconds. This defaults to one hour when not provided. If a lifetime - greater than one hour is required, the service account must be added - as an allowed value in an Organization Policy that enforces the + Lifetime duration of the service account access token in seconds. + Defaults to one hour if not specified. If a lifetime greater than one + hour is required, the service account must be added as an allowed + value in an Organization Policy that enforces the constraints/iam.allowServiceAccountCredentialLifetimeExtension constraint. diff --git a/gcloud/alpha/iam/workload-identity-pools/create-cred-config b/gcloud/alpha/iam/workload-identity-pools/create-cred-config index ea795e7b2..9645b32e6 100644 --- a/gcloud/alpha/iam/workload-identity-pools/create-cred-config +++ b/gcloud/alpha/iam/workload-identity-pools/create-cred-config @@ -106,13 +106,13 @@ OPTIONAL FLAGS The custom Application ID URI for the Azure access token. --credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME - The subject token field name (key) in a JSON credential source. + Subject token field name (key) in a JSON credential source. --credential-source-headers=[key=value,...] Headers to use when querying the credential-source-url. --credential-source-type=CREDENTIAL_SOURCE_TYPE - The format of the credential source (JSON or text). + Format of the credential source (JSON or text). --enable-imdsv2 Adds the AWS IMDSv2 session token Url to the credential source to @@ -125,25 +125,25 @@ OPTIONAL FLAGS Arguments for an executable type credential source. --executable-output-file=EXECUTABLE_OUTPUT_FILE - The absolute path to the file storing the executable response. + Absolute path to the file storing the executable response. --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS - The timeout duration in milliseconds for waiting for the executable - to finish. + Timeout duration, in milliseconds, to wait for the executable to + finish. Service account impersonation options. --service-account=SERVICE_ACCOUNT - The email of the service account to impersonate. + Email of the service account to impersonate. This flag argument must be specified if any of the other arguments in this group are specified. --service-account-token-lifetime-seconds=SERVICE_ACCOUNT_TOKEN_LIFETIME_SECONDS - The desired lifetime duration of the service account access token in - seconds. This defaults to one hour when not provided. If a lifetime - greater than one hour is required, the service account must be added - as an allowed value in an Organization Policy that enforces the + Lifetime duration of the service account access token in seconds. + Defaults to one hour if not specified. If a lifetime greater than one + hour is required, the service account must be added as an allowed + value in an Organization Policy that enforces the constraints/iam.allowServiceAccountCredentialLifetimeExtension constraint. diff --git a/gcloud/alpha/metastore/services/create b/gcloud/alpha/metastore/services/create index 80c65ceea..73a16ebe4 100644 --- a/gcloud/alpha/metastore/services/create +++ b/gcloud/alpha/metastore/services/create @@ -23,6 +23,7 @@ SYNOPSIS --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE | --enable-scheduled-backup --scheduled-backup-cron=SCHEDULED_BACKUP_CRON --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -331,6 +332,39 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + At most one of these can be specified: + + --scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE + Path to a JSON file containing a mapping of scheduled backup + configurations key-value pairs to apply to the scheduled backup. + + For example: + + backup_configs.json + { + "enabled": true, + "cron_schedule": "0 * * * *", + "backup_location": "gs://example-bucket", + "time_zone": "UTC" + } + + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + --enable-scheduled-backup + Enable or disable scheduled backups for the Metastore service. + + --scheduled-backup-cron=SCHEDULED_BACKUP_CRON + Specify the frequency of a scheduled backup of the metastore + service. + + --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION + Set the Cloud Storage URI to store the scheduled backups of the + metastore service. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/metastore/services/update b/gcloud/alpha/metastore/services/update index b2b08a69f..ec0e06176 100644 --- a/gcloud/alpha/metastore/services/update +++ b/gcloud/alpha/metastore/services/update @@ -13,6 +13,7 @@ SYNOPSIS --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE | --enable-scheduled-backup --scheduled-backup-cron=SCHEDULED_BACKUP_CRON --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION] [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS, ...] --clear-auxiliary-versions] [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[KEY=VALUE, @@ -200,6 +201,39 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + At most one of these can be specified: + + --scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE + Path to a JSON file containing a mapping of scheduled backup + configurations key-value pairs to apply to the scheduled backup. + + For example: + + backup_configs.json + { + "enabled": true, + "cron_schedule": "0 * * * *", + "backup_location": "gs://example-bucket", + "time_zone": "UTC" + } + + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + --enable-scheduled-backup + Enable or disable scheduled backups for the Metastore service. + + --scheduled-backup-cron=SCHEDULED_BACKUP_CRON + Specify the frequency of a scheduled backup of the metastore + service. + + --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION + Set the Cloud Storage URI to store the scheduled backups of the + metastore service. + Auxiliary versions configuration for the Dataproc Metastore service. When specified, a secondary Hive metastore service is created along with the primary service. diff --git a/gcloud/alpha/notebooks/instances/create b/gcloud/alpha/notebooks/instances/create index d23468662..41013c8bb 100644 --- a/gcloud/alpha/notebooks/instances/create +++ b/gcloud/alpha/notebooks/instances/create @@ -167,7 +167,7 @@ FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3. + TPU_V2, TPU_V3, NVIDIA_L4. Boot disk configurations. diff --git a/gcloud/alpha/notebooks/instances/update b/gcloud/alpha/notebooks/instances/update index 0d23ac4d6..6fbb8d838 100644 --- a/gcloud/alpha/notebooks/instances/update +++ b/gcloud/alpha/notebooks/instances/update @@ -78,7 +78,7 @@ REQUIRED FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3. + TPU_V2, TPU_V3, NVIDIA_L4. --labels=[KEY=VALUE,...] Labels to apply to this instance. These can be later modified by the diff --git a/gcloud/alpha/projects/create b/gcloud/alpha/projects/create index 425674ff3..abb9e7b84 100644 --- a/gcloud/alpha/projects/create +++ b/gcloud/alpha/projects/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha projects create [PROJECT_ID] [--no-enable-cloud-apis] [--folder=FOLDER_ID] [--labels=[KEY=VALUE,...]] [--name=NAME] [--organization=ORGANIZATION_ID] [--set-as-default] - [GCLOUD_WIDE_FLAG ...] + [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a new project with the given project ID. By default, @@ -64,6 +64,12 @@ FLAGS --set-as-default Set newly created project as [core.project] property. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + "=". + + Example: 123/environment=production,123/costCenter=marketing + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/resource-manager/folders/create b/gcloud/alpha/resource-manager/folders/create index e85369025..cd46b4dde 100644 --- a/gcloud/alpha/resource-manager/folders/create +++ b/gcloud/alpha/resource-manager/folders/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha resource-manager folders create --display-name=DISPLAY_NAME [--async] [--folder=FOLDER_ID] [--organization=ORGANIZATION_ID] - [GCLOUD_WIDE_FLAG ...] + [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a new folder in the given parent folder or organization. @@ -37,6 +37,12 @@ OPTIONAL FLAGS --organization=ORGANIZATION_ID ID for the organization to use as a parent + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + "=". + + Example: 123/environment=production,123/costCenter=marketing + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index f506bcc29..5c9cbb72e 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -442,10 +442,12 @@ FLAGS disable. --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to start - listening on its port for the deployment to succeed. This check is - enabled by default if unspecified. Use --deploy-health-check to - enable and --no-deploy-health-check to disable. + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 5a72e4fc5..4228bc868 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -328,10 +328,12 @@ FLAGS disable. --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to start - listening on its port for the deployment to succeed. This check is - enabled by default if unspecified. Use --deploy-health-check to - enable and --no-deploy-health-check to disable. + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/sql/backups/list b/gcloud/alpha/sql/backups/list index 9342dbb97..6cc7e033c 100644 --- a/gcloud/alpha/sql/backups/list +++ b/gcloud/alpha/sql/backups/list @@ -3,7 +3,7 @@ NAME project or a given instance SYNOPSIS - gcloud alpha sql backups list --instance=INSTANCE, -i INSTANCE + gcloud alpha sql backups list [--instance=INSTANCE, -i INSTANCE] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -12,7 +12,7 @@ DESCRIPTION instance and configuration in the reverse chronological order of the enqueued time. -REQUIRED FLAGS +FLAGS --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID or "-" for all instances. diff --git a/gcloud/alpha/storage/buckets/create b/gcloud/alpha/storage/buckets/create index 4e6153cdf..b58f3bc58 100644 --- a/gcloud/alpha/storage/buckets/create +++ b/gcloud/alpha/storage/buckets/create @@ -8,7 +8,8 @@ SYNOPSIS -k DEFAULT_ENCRYPTION_KEY] [--default-storage-class=DEFAULT_STORAGE_CLASS, -c DEFAULT_STORAGE_CLASS, -s DEFAULT_STORAGE_CLASS] - [--enable-per-object-retention] [--location=LOCATION, -l LOCATION] + [--enable-hierarchical-namespace] [--enable-per-object-retention] + [--location=LOCATION, -l LOCATION] [--[no-]pap, --[no-]public-access-prevention] [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] @@ -57,6 +58,9 @@ FLAGS If not specified, the default storage class used by Cloud Storage is "Standard". + --enable-hierarchical-namespace + Enable heirarchical namepsace for the bucket + --enable-per-object-retention Enables each object in the bucket to have its own retention settings, which prevents deletion until stored for a specific length of time. diff --git a/gcloud/alpha/tasks/buffer b/gcloud/alpha/tasks/buffer index 0df484d12..c8ae76e7f 100644 --- a/gcloud/alpha/tasks/buffer +++ b/gcloud/alpha/tasks/buffer @@ -36,7 +36,9 @@ 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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud tasks buffer $ gcloud beta tasks buffer diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 3725b019e..f85fcb0a9 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -14,6 +14,7 @@ SYNOPSIS [--disable-public-ip-addresses] [--disable-ssh-to-vm] [--disable-tcp-connections] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] + [--ephemeral-directory=[PROPERTY=VALUE,...]] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--network-tags=[NETWORK_TAGS,...]] @@ -161,6 +162,9 @@ FLAGS Default value is false. If set, instances will have nested virtualization enabled. + --ephemeral-directory=[PROPERTY=VALUE,...] + Ephemeral directory which won't persist across workstation sessions. + --idle-timeout=IDLE_TIMEOUT; default=7200 How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/apphub/applications/add-iam-policy-binding b/gcloud/apphub/applications/add-iam-policy-binding new file mode 100644 index 000000000..9fc3212fc --- /dev/null +++ b/gcloud/apphub/applications/add-iam-policy-binding @@ -0,0 +1,85 @@ +NAME + gcloud apphub applications add-iam-policy-binding - add IAM policy binding + to an Apphub application + +SYNOPSIS + gcloud apphub applications add-iam-policy-binding + (APPLICATION : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add IAM policy binding to an Apphub application. + +EXAMPLES + To add an IAM policy binding for the role of roles/apphub.viewer for the + user test-user@gmail.com to Application my-app in location us-east1, run: + + $ gcloud apphub applications add-iam-policy-binding my-app \ + --location=us-east1 --role=roles/apphub.viewer \ + --member=user:test-user@gmail.com + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +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 variant is also available: + + $ gcloud alpha apphub applications add-iam-policy-binding + diff --git a/gcloud/apphub/applications/create b/gcloud/apphub/applications/create new file mode 100644 index 000000000..1d6d3fc2c --- /dev/null +++ b/gcloud/apphub/applications/create @@ -0,0 +1,123 @@ +NAME + gcloud apphub applications create - create an Apphub application + +SYNOPSIS + gcloud apphub applications create (APPLICATION : --location=LOCATION) + --scope-type=SCOPE_TYPE [--async] + [--business-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] + [--developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] + [--operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an Apphub application. + +EXAMPLES + To create the Application my-app with scope type REGIONAL in location + us-east1, run: + + $ gcloud apphub applications create my-app --location=us-east1 \ + --scope-type=REGIONAL + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --scope-type=SCOPE_TYPE + Scope of the Application. SCOPE_TYPE must be (only one value is + supported): + + REGIONAL + Represents a regional application + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --business-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Business owners of the application + + --criticality-type=CRITICALITY_TYPE + Criticality Type of the application. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type + + --description=DESCRIPTION + Description of the Application + + --developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Developer owners of the application + + --display-name=DISPLAY_NAME + Human-friendly display name + + --environment-type=ENVIRONMENT_TYPE + Environment Type of the application. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type + + --operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Operator owners of the application + +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 variant is also available: + + $ gcloud alpha apphub applications create + diff --git a/gcloud/apphub/applications/delete b/gcloud/apphub/applications/delete new file mode 100644 index 000000000..e6e9591d8 --- /dev/null +++ b/gcloud/apphub/applications/delete @@ -0,0 +1,64 @@ +NAME + gcloud apphub applications delete - delete an Apphub application + +SYNOPSIS + gcloud apphub applications delete (APPLICATION : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an Apphub application. + +EXAMPLES + To delete the Application my-app in location us-east1, run: + + $ gcloud apphub applications delete my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 variant is also available: + + $ gcloud alpha apphub applications delete + diff --git a/gcloud/apphub/applications/describe b/gcloud/apphub/applications/describe new file mode 100644 index 000000000..d713085c7 --- /dev/null +++ b/gcloud/apphub/applications/describe @@ -0,0 +1,59 @@ +NAME + gcloud apphub applications describe - describe an Apphub application + +SYNOPSIS + gcloud apphub applications describe (APPLICATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub application. + +EXAMPLES + To describe the Application my-app in location us-east1, run: + + $ gcloud apphub applications describe my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 variant is also available: + + $ gcloud alpha apphub applications describe + diff --git a/gcloud/apphub/applications/get-iam-policy b/gcloud/apphub/applications/get-iam-policy new file mode 100644 index 000000000..b40902739 --- /dev/null +++ b/gcloud/apphub/applications/get-iam-policy @@ -0,0 +1,91 @@ +NAME + gcloud apphub applications get-iam-policy - get the IAM policy for an + Apphub application + +SYNOPSIS + gcloud apphub applications get-iam-policy + (APPLICATION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Returns an empty policy if the application does not have an existing IAM + policy set. + +EXAMPLES + To get the application IAM policy for the Application my-app in in location + us-east1, run: + + $ gcloud apphub applications get-iam-policy my-app \ + --location=us-east1 + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 + This variant is also available: + + $ gcloud alpha apphub applications get-iam-policy + diff --git a/gcloud/apphub/applications/help b/gcloud/apphub/applications/help new file mode 100644 index 000000000..800fe1e15 --- /dev/null +++ b/gcloud/apphub/applications/help @@ -0,0 +1,59 @@ +NAME + gcloud apphub applications - manage App Hub Applications + +SYNOPSIS + gcloud apphub applications GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Applications. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + services + Manage App Hub Application Services. + + workloads + Manage App Hub Application Workloads. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add IAM policy binding to an Apphub application. + + create + Create an Apphub application. + + delete + Delete an Apphub application. + + describe + Describe an Apphub application. + + get-iam-policy + Get the IAM policy for an Apphub application. + + list + List Apphub applications. + + remove-iam-policy-binding + Remove IAM policy binding from an Apphub application. + + set-iam-policy + Set the IAM policy for an Apphub application as defined in a JSON/YAML + file. + + update + Update an Apphub application. + +NOTES + This variant is also available: + + $ gcloud alpha apphub applications + diff --git a/gcloud/apphub/applications/list b/gcloud/apphub/applications/list new file mode 100644 index 000000000..a29b9e878 --- /dev/null +++ b/gcloud/apphub/applications/list @@ -0,0 +1,80 @@ +NAME + gcloud apphub applications list - list Apphub applications + +SYNOPSIS + gcloud apphub applications list --location=LOCATION [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub applications. + +EXAMPLES + To list all applications in locations us-east1, run: + + $ gcloud apphub applications list --location=us-east1 + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub applications list + diff --git a/gcloud/apphub/applications/remove-iam-policy-binding b/gcloud/apphub/applications/remove-iam-policy-binding new file mode 100644 index 000000000..d05fa88cd --- /dev/null +++ b/gcloud/apphub/applications/remove-iam-policy-binding @@ -0,0 +1,86 @@ +NAME + gcloud apphub applications remove-iam-policy-binding - remove IAM policy + binding from an Apphub application + +SYNOPSIS + gcloud apphub applications remove-iam-policy-binding + (APPLICATION : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove IAM policy binding from an Apphub application. + +EXAMPLES + To remove an IAM policy binding for the role of roles/apphub.viewer for the + user test-user@gmail.com from Application my-app in location us-east1, run: + + $ gcloud apphub applications remove-iam-policy-binding my-app \ + --location=us-east1 --role=roles/apphub.viewer \ + --member=user:test-user@gmail.com + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +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 variant is also available: + + $ gcloud alpha apphub applications remove-iam-policy-binding + diff --git a/gcloud/apphub/applications/services/create b/gcloud/apphub/applications/services/create new file mode 100644 index 000000000..ace97e942 --- /dev/null +++ b/gcloud/apphub/applications/services/create @@ -0,0 +1,150 @@ +NAME + gcloud apphub applications services create - create an Apphub application + service + +SYNOPSIS + gcloud apphub applications services create + (SERVICE : --application=APPLICATION --location=LOCATION) + --discovered-service=DISCOVERED_SERVICE [--async] + [--business-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] + [--developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] + [--operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an Apphub application service. + +EXAMPLES + To create the Service my-service with discovered service + my-discovered-service in the Application my-app in location us-east1, run: + + $ gcloud apphub applications services create my-service \ + --application=my-app --location=us-east1 \ + --discovered-service=my-discovered-service + +POSITIONAL ARGUMENTS + Service resource - The Service resource. 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 SERVICE 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. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument SERVICE on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the service. + + To set the location attribute: + ▸ provide the argument SERVICE on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + DiscoveredService resource - The discovered service resource. This + represents a Cloud 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 --discovered-service on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --discovered-service on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --discovered-service=DISCOVERED_SERVICE + ID of the discoveredService or fully qualified identifier for the + discoveredService. + + To set the discovered_service attribute: + ▸ provide the argument --discovered-service on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --business-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Business owners of the service + + --criticality-type=CRITICALITY_TYPE + Criticality Type of the service. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type + + --description=DESCRIPTION + Description of the service + + --developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Developer owners of the service + + --display-name=DISPLAY_NAME + Human-friendly display name + + --environment-type=ENVIRONMENT_TYPE + Environment Type of the service. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type + + --operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Operator owners of the service + +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 variant is also available: + + $ gcloud alpha apphub applications services create + diff --git a/gcloud/apphub/applications/services/delete b/gcloud/apphub/applications/services/delete new file mode 100644 index 000000000..e112da9ef --- /dev/null +++ b/gcloud/apphub/applications/services/delete @@ -0,0 +1,75 @@ +NAME + gcloud apphub applications services delete - delete an Apphub application + service + +SYNOPSIS + gcloud apphub applications services delete + (SERVICE : --application=APPLICATION --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an Apphub application service. + +EXAMPLES + To delete the Service my-service from the Application my-app in location + us-east1, run: + + $ gcloud apphub applications services delete my-service \ + --application=my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Service resource - The Service ID. 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 service 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. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the service. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 variant is also available: + + $ gcloud alpha apphub applications services delete + diff --git a/gcloud/apphub/applications/services/describe b/gcloud/apphub/applications/services/describe new file mode 100644 index 000000000..083484b79 --- /dev/null +++ b/gcloud/apphub/applications/services/describe @@ -0,0 +1,70 @@ +NAME + gcloud apphub applications services describe - describe an Apphub + application service + +SYNOPSIS + gcloud apphub applications services describe + (SERVICE : --application=APPLICATION --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub application service. + +EXAMPLES + To describe the Service my-service in the Application my-app in location + us-east1, run: + + $ gcloud apphub applications services describe my-service \ + --application=my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Service resource - The Service ID. 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 service 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. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the service. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 variant is also available: + + $ gcloud alpha apphub applications services describe + diff --git a/gcloud/apphub/applications/services/help b/gcloud/apphub/applications/services/help new file mode 100644 index 000000000..bbd4af918 --- /dev/null +++ b/gcloud/apphub/applications/services/help @@ -0,0 +1,37 @@ +NAME + gcloud apphub applications services - manage App Hub Application Services + +SYNOPSIS + gcloud apphub applications services COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Application Services. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create an Apphub application service. + + delete + Delete an Apphub application service. + + describe + Describe an Apphub application service. + + list + List Apphub application services. + + update + Update an Apphub application service. + +NOTES + This variant is also available: + + $ gcloud alpha apphub applications services + diff --git a/gcloud/apphub/applications/services/list b/gcloud/apphub/applications/services/list new file mode 100644 index 000000000..00b6c1abe --- /dev/null +++ b/gcloud/apphub/applications/services/list @@ -0,0 +1,94 @@ +NAME + gcloud apphub applications services list - list Apphub application services + +SYNOPSIS + gcloud apphub applications services list + (--application=APPLICATION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub application services. + +EXAMPLES + To list all Services in the Application my-app in location us-east1, run: + + $ gcloud apphub applications services list --application=my-app \ + --location=us-east1 + +REQUIRED FLAGS + Application resource - The Application ID. 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 --application 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. + + --application=APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument --application on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument --application on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub applications services list + diff --git a/gcloud/apphub/applications/services/update b/gcloud/apphub/applications/services/update new file mode 100644 index 000000000..ae0f4ee15 --- /dev/null +++ b/gcloud/apphub/applications/services/update @@ -0,0 +1,123 @@ +NAME + gcloud apphub applications services update - update an Apphub application + service + +SYNOPSIS + gcloud apphub applications services update + (SERVICE : --application=APPLICATION --location=LOCATION) [--async] + [--business-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] + [--developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] + [--operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Apphub application service. + +EXAMPLES + To update the Service my-service with a new environment prod in the + Application my-app in location us-east1, run: + + $ gcloud apphub applications services update my-service \ + --environment-type=TEST --application=my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Service resource - The Service ID. 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 service 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. + + SERVICE + ID of the service or fully qualified identifier for the service. + + To set the service attribute: + ▸ provide the argument service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the service. + + To set the location attribute: + ▸ provide the argument service on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --business-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Business owners of the service + + --criticality-type=CRITICALITY_TYPE + Criticality Type of the service. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type + + --description=DESCRIPTION + Description of the service + + --developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Developer owners of the service + + --display-name=DISPLAY_NAME + Human-friendly display name + + --environment-type=ENVIRONMENT_TYPE + Environment Type of the service. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type + + --operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Operator owners of the service + +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 variant is also available: + + $ gcloud alpha apphub applications services update + diff --git a/gcloud/apphub/applications/set-iam-policy b/gcloud/apphub/applications/set-iam-policy new file mode 100644 index 000000000..c5280dc10 --- /dev/null +++ b/gcloud/apphub/applications/set-iam-policy @@ -0,0 +1,76 @@ +NAME + gcloud apphub applications set-iam-policy - set the IAM policy for an + Apphub application as defined in a JSON/YAML file + +SYNOPSIS + gcloud apphub applications set-iam-policy + (APPLICATION : --location=LOCATION) POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To set the application IAM policy using a json file 'my_policy.json' for + the Application my-app in location us-east1, run: + + $ gcloud apphub applications set-iam-policy my-app \ + --location=us-east1 /path/to/my_policy.json + + To set the application IAM policy using a yaml file 'my_policy.yaml for the + Application my-app in location us-east1, run: + + $ gcloud apphub applications set-iam-policy my-app \ + --location=us-east1 /path/to/my_policy.yaml + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +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 variant is also available: + + $ gcloud alpha apphub applications set-iam-policy + diff --git a/gcloud/apphub/applications/update b/gcloud/apphub/applications/update new file mode 100644 index 000000000..d7c6ccd78 --- /dev/null +++ b/gcloud/apphub/applications/update @@ -0,0 +1,114 @@ +NAME + gcloud apphub applications update - update an Apphub application + +SYNOPSIS + gcloud apphub applications update (APPLICATION : --location=LOCATION) + [--async] [--business-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] + [--developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] + [--operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Apphub application. + +EXAMPLES + To update the Application my-app with a new environment prod in location + us-east1, run: + + $ gcloud apphub applications update my-app --location=us-east1 \ + --environment-type=TEST + +POSITIONAL ARGUMENTS + Application resource - The Application ID. 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 application 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument application on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument application on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --business-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Business owners of the application + + --criticality-type=CRITICALITY_TYPE + Criticality Type of the application. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type + + --description=DESCRIPTION + Description of the Application + + --developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Developer owners of the application + + --display-name=DISPLAY_NAME + Human-friendly display name + + --environment-type=ENVIRONMENT_TYPE + Environment Type of the application. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type + + --operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Operator owners of the application + +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 variant is also available: + + $ gcloud alpha apphub applications update + diff --git a/gcloud/apphub/applications/workloads/create b/gcloud/apphub/applications/workloads/create new file mode 100644 index 000000000..f7f6de2a3 --- /dev/null +++ b/gcloud/apphub/applications/workloads/create @@ -0,0 +1,150 @@ +NAME + gcloud apphub applications workloads create - create an Apphub application + workload + +SYNOPSIS + gcloud apphub applications workloads create + (WORKLOAD : --application=APPLICATION --location=LOCATION) + --discovered-workload=DISCOVERED_WORKLOAD [--async] + [--business-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] + [--developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] + [--operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an Apphub application workload. + +EXAMPLES + To create the Workload my-workload with discovered workload + my-discovered-workload in the Application my-app in location us-east1, run: + + $ gcloud apphub applications workloads create my-workload \ + --application=my-app --location=us-east1 \ + --discovered-workload=my-discovered-workload + +POSITIONAL ARGUMENTS + Workload resource - The Workload resource. 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 WORKLOAD 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. + + WORKLOAD + ID of the workload or fully qualified identifier for the workload. + + To set the workload attribute: + ▸ provide the argument WORKLOAD on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument WORKLOAD on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the workload. + + To set the location attribute: + ▸ provide the argument WORKLOAD on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + DiscoveredWorkload resource - The discovered workload resource. This + represents a Cloud 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 --discovered-workload on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --discovered-workload on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --discovered-workload=DISCOVERED_WORKLOAD + ID of the discoveredWorkload or fully qualified identifier for the + discoveredWorkload. + + To set the discovered_workload attribute: + ▸ provide the argument --discovered-workload on the command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --business-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Business owners of the workload + + --criticality-type=CRITICALITY_TYPE + Criticality Type of the workload. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type + + --description=DESCRIPTION + Description of the Workload + + --developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Developer owners of the workload + + --display-name=DISPLAY_NAME + Human-friendly display name + + --environment-type=ENVIRONMENT_TYPE + Environment Type of the workload. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type + + --operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Operator owners of the workload + +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 variant is also available: + + $ gcloud alpha apphub applications workloads create + diff --git a/gcloud/apphub/applications/workloads/delete b/gcloud/apphub/applications/workloads/delete new file mode 100644 index 000000000..8dab80888 --- /dev/null +++ b/gcloud/apphub/applications/workloads/delete @@ -0,0 +1,75 @@ +NAME + gcloud apphub applications workloads delete - delete an Apphub application + workload + +SYNOPSIS + gcloud apphub applications workloads delete + (WORKLOAD : --application=APPLICATION --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an Apphub application workload. + +EXAMPLES + To delete the Workload my-workload from the Application my-app in location + us-east1, run: + + $ gcloud apphub applications workloads delete my-workload \ + --application=my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Workload resource - The Workload ID. 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 workload 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. + + WORKLOAD + ID of the workload or fully qualified identifier for the workload. + + To set the workload attribute: + ▸ provide the argument workload on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the workload. + + To set the location attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 variant is also available: + + $ gcloud alpha apphub applications workloads delete + diff --git a/gcloud/apphub/applications/workloads/describe b/gcloud/apphub/applications/workloads/describe new file mode 100644 index 000000000..87c265d1f --- /dev/null +++ b/gcloud/apphub/applications/workloads/describe @@ -0,0 +1,70 @@ +NAME + gcloud apphub applications workloads describe - describe an Apphub + application workload + +SYNOPSIS + gcloud apphub applications workloads describe + (WORKLOAD : --application=APPLICATION --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub application workload. + +EXAMPLES + To describe the Workload my-workload in the Application my-app in location + us-east1, run: + + $ gcloud apphub applications workloads describe my-workload \ + --application=my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Workload resource - The Workload ID. 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 workload 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. + + WORKLOAD + ID of the workload or fully qualified identifier for the workload. + + To set the workload attribute: + ▸ provide the argument workload on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the workload. + + To set the location attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 variant is also available: + + $ gcloud alpha apphub applications workloads describe + diff --git a/gcloud/apphub/applications/workloads/help b/gcloud/apphub/applications/workloads/help new file mode 100644 index 000000000..71fb99685 --- /dev/null +++ b/gcloud/apphub/applications/workloads/help @@ -0,0 +1,37 @@ +NAME + gcloud apphub applications workloads - manage App Hub Application Workloads + +SYNOPSIS + gcloud apphub applications workloads COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Application Workloads. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create an Apphub application workload. + + delete + Delete an Apphub application workload. + + describe + Describe an Apphub application workload. + + list + List Apphub application workloads. + + update + Update an Apphub application workload. + +NOTES + This variant is also available: + + $ gcloud alpha apphub applications workloads + diff --git a/gcloud/apphub/applications/workloads/list b/gcloud/apphub/applications/workloads/list new file mode 100644 index 000000000..51d15012d --- /dev/null +++ b/gcloud/apphub/applications/workloads/list @@ -0,0 +1,95 @@ +NAME + gcloud apphub applications workloads list - list Apphub application + workloads + +SYNOPSIS + gcloud apphub applications workloads list + (--application=APPLICATION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub application workloads. + +EXAMPLES + To list all Workloads in the Application my-app in location us-east1, run: + + $ gcloud apphub applications workloads list --application=my-app \ + --location=us-east1 + +REQUIRED FLAGS + Application resource - The Application ID. 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 --application 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. + + --application=APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument --application on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument --application on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub applications workloads list + diff --git a/gcloud/apphub/applications/workloads/update b/gcloud/apphub/applications/workloads/update new file mode 100644 index 000000000..726a6ab50 --- /dev/null +++ b/gcloud/apphub/applications/workloads/update @@ -0,0 +1,123 @@ +NAME + gcloud apphub applications workloads update - update an Apphub application + workload + +SYNOPSIS + gcloud apphub applications workloads update + (WORKLOAD : --application=APPLICATION --location=LOCATION) [--async] + [--business-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--criticality-type=CRITICALITY_TYPE] [--description=DESCRIPTION] + [--developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [--display-name=DISPLAY_NAME] [--environment-type=ENVIRONMENT_TYPE] + [--operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Apphub application workload. + +EXAMPLES + To update the Workload my-workload with a new environment prod in the + Application my-app in location us-east1, run: + + $ gcloud apphub applications workloads update my-workload \ + --environment-type=TEST --application=my-app --location=us-east1 + +POSITIONAL ARGUMENTS + Workload resource - The Workload ID. 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 workload 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. + + WORKLOAD + ID of the workload or fully qualified identifier for the workload. + + To set the workload attribute: + ▸ provide the argument workload on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --application=APPLICATION + Name for the application + + To set the application attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --application on the command line. + + --location=LOCATION + The Cloud location for the workload. + + To set the location attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --business-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Business owners of the workload + + --criticality-type=CRITICALITY_TYPE + Criticality Type of the workload. CRITICALITY_TYPE must be one of: + + HIGH + High impact + LOW + Low impact + MEDIUM + Medium impact + MISSION_CRITICAL + Mission critical service, application or workload + TYPE_UNSPECIFIED + Unspecified criticality type + + --description=DESCRIPTION + Description of the Workload + + --developer-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Developer owners of the workload + + --display-name=DISPLAY_NAME + Human-friendly display name + + --environment-type=ENVIRONMENT_TYPE + Environment Type of the workload. ENVIRONMENT_TYPE must be one of: + + DEVELOPMENT + Development environment + PRODUCTION + Production environment + STAGING + Staging environment + TEST + Test environment + TYPE_UNSPECIFIED + Unspecified environment type + + --operator-owners=[display-name=DISPLAY-NAME],[email=EMAIL] + Operator owners of the workload + +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 variant is also available: + + $ gcloud alpha apphub applications workloads update + diff --git a/gcloud/apphub/discovered-services/describe b/gcloud/apphub/discovered-services/describe new file mode 100644 index 000000000..2de81c321 --- /dev/null +++ b/gcloud/apphub/discovered-services/describe @@ -0,0 +1,63 @@ +NAME + gcloud apphub discovered-services describe - describe an Apphub discovered + service + +SYNOPSIS + gcloud apphub discovered-services describe + (DISCOVERED_SERVICE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub discovered service. + +EXAMPLES + To describe the DiscoveredService my-discovered-service in location + us-east1, run: + + $ gcloud apphub discovered-services describe my-discovered-service \ + --location=us-east1 + +POSITIONAL ARGUMENTS + DiscoveredService resource - The Discovered Service ID. 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 discovered_service 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. + + DISCOVERED_SERVICE + ID of the discoveredService or fully qualified identifier for the + discoveredService. + + To set the discovered_service attribute: + ▸ provide the argument discovered_service on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the discoveredService. + + To set the location attribute: + ▸ provide the argument discovered_service on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +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 variant is also available: + + $ gcloud alpha apphub discovered-services describe + diff --git a/gcloud/apphub/discovered-services/help b/gcloud/apphub/discovered-services/help new file mode 100644 index 000000000..6df5eff6e --- /dev/null +++ b/gcloud/apphub/discovered-services/help @@ -0,0 +1,31 @@ +NAME + gcloud apphub discovered-services - manage App Hub Discovered Services + +SYNOPSIS + gcloud apphub discovered-services COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Discovered Services. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an Apphub discovered service. + + list + List Apphub discovered services. + + lookup + Lookup an Apphub discovered service with URI. + +NOTES + This variant is also available: + + $ gcloud alpha apphub discovered-services + diff --git a/gcloud/apphub/discovered-services/list b/gcloud/apphub/discovered-services/list new file mode 100644 index 000000000..fa34dc4d8 --- /dev/null +++ b/gcloud/apphub/discovered-services/list @@ -0,0 +1,81 @@ +NAME + gcloud apphub discovered-services list - list Apphub discovered services + +SYNOPSIS + gcloud apphub discovered-services list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub discovered services. + +EXAMPLES + To list DiscoveredServices that could be added to an application in + location us-east1, run: + + $ gcloud apphub discovered-services list --location=us-east1 + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub discovered-services list + diff --git a/gcloud/apphub/discovered-services/lookup b/gcloud/apphub/discovered-services/lookup new file mode 100644 index 000000000..193be73fc --- /dev/null +++ b/gcloud/apphub/discovered-services/lookup @@ -0,0 +1,53 @@ +NAME + gcloud apphub discovered-services lookup - lookup an Apphub discovered + service with URI + +SYNOPSIS + gcloud apphub discovered-services lookup --location=LOCATION --uri=URI + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lookup an Apphub discovered service with URI. + +EXAMPLES + To lookup a discovered service with uri my-service-uri in location us-east1 + run: + + $ gcloud apphub discovered-services lookup --location=us-east1 \ + --uri=my-service-uri + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + --uri=URI + Google Cloud Platform resource URI to look up service for. + +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 variant is also available: + + $ gcloud alpha apphub discovered-services lookup + diff --git a/gcloud/apphub/discovered-workloads/describe b/gcloud/apphub/discovered-workloads/describe new file mode 100644 index 000000000..afca57e0e --- /dev/null +++ b/gcloud/apphub/discovered-workloads/describe @@ -0,0 +1,63 @@ +NAME + gcloud apphub discovered-workloads describe - describe an Apphub discovered + workload + +SYNOPSIS + gcloud apphub discovered-workloads describe + (DISCOVERED_WORKLOAD : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub discovered workload. + +EXAMPLES + To describe the DiscoveredWorkload my-discovered-workload in location + us-east1, run: + + $ gcloud apphub discovered-workloads describe \ + my-discovered-workload --location=us-east1 + +POSITIONAL ARGUMENTS + DiscoveredWorkload resource - The Discovered Workload ID. 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 discovered_workload 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. + + DISCOVERED_WORKLOAD + ID of the discoveredWorkload or fully qualified identifier for the + discoveredWorkload. + + To set the discovered_workload attribute: + ▸ provide the argument discovered_workload on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the discoveredWorkload. + + To set the location attribute: + ▸ provide the argument discovered_workload on the command line with + a fully specified name; + ▸ provide the argument --location on the command line. + +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 variant is also available: + + $ gcloud alpha apphub discovered-workloads describe + diff --git a/gcloud/apphub/discovered-workloads/help b/gcloud/apphub/discovered-workloads/help new file mode 100644 index 000000000..6ef1f9201 --- /dev/null +++ b/gcloud/apphub/discovered-workloads/help @@ -0,0 +1,31 @@ +NAME + gcloud apphub discovered-workloads - manage App Hub Discovered Workloads + +SYNOPSIS + gcloud apphub discovered-workloads COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Discovered Workloads. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an Apphub discovered workload. + + list + List Apphub discovered workloads that could be added to an application. + + lookup + Lookup an Apphub discovered workload with URI. + +NOTES + This variant is also available: + + $ gcloud alpha apphub discovered-workloads + diff --git a/gcloud/apphub/discovered-workloads/list b/gcloud/apphub/discovered-workloads/list new file mode 100644 index 000000000..cdb28994d --- /dev/null +++ b/gcloud/apphub/discovered-workloads/list @@ -0,0 +1,82 @@ +NAME + gcloud apphub discovered-workloads list - list Apphub discovered workloads + that could be added to an application + +SYNOPSIS + gcloud apphub discovered-workloads list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub discovered workloads that could be added to an application. + +EXAMPLES + To list DiscoveredWorkloads that could be added to an application in + location us-east1, run: + + $ gcloud apphub discovered-workloads list --location=us-east1 + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub discovered-workloads list + diff --git a/gcloud/apphub/discovered-workloads/lookup b/gcloud/apphub/discovered-workloads/lookup new file mode 100644 index 000000000..0dab02e47 --- /dev/null +++ b/gcloud/apphub/discovered-workloads/lookup @@ -0,0 +1,53 @@ +NAME + gcloud apphub discovered-workloads lookup - lookup an Apphub discovered + workload with URI + +SYNOPSIS + gcloud apphub discovered-workloads lookup --location=LOCATION --uri=URI + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lookup an Apphub discovered workload with URI. + +EXAMPLES + To lookup a discovered workload with uri my-workload-uri in location + us-east1 run: + + $ gcloud apphub discovered-workloads lookup --location=us-east1 \ + --uri=my-workload-uri + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + --uri=URI + Google Cloud Platform resource URI to look up workload for. + +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 variant is also available: + + $ gcloud alpha apphub discovered-workloads lookup + diff --git a/gcloud/apphub/help b/gcloud/apphub/help new file mode 100644 index 000000000..f3c4bdb98 --- /dev/null +++ b/gcloud/apphub/help @@ -0,0 +1,37 @@ +NAME + gcloud apphub - manage App Hub resources + +SYNOPSIS + gcloud apphub GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage App Hub resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + applications + Manage App Hub Applications. + + discovered-services + Manage App Hub Discovered Services. + + discovered-workloads + Manage App Hub Discovered Workloads. + + operations + Manage App Hub Operations (long-running operations). + + service-projects + Manage App Hub Service Projects. + +NOTES + This variant is also available: + + $ gcloud alpha apphub + diff --git a/gcloud/apphub/operations/describe b/gcloud/apphub/operations/describe new file mode 100644 index 000000000..835e9eca9 --- /dev/null +++ b/gcloud/apphub/operations/describe @@ -0,0 +1,59 @@ +NAME + gcloud apphub operations describe - describe an Apphub operation + (long-running operation) + +SYNOPSIS + gcloud apphub operations describe (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub operation (long-running operation). + +EXAMPLES + To describe a specific apphub operation with the name my-operation, run: + + $ gcloud apphub operations describe my-operation + +POSITIONAL ARGUMENTS + Operation resource - The Operation ID. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the operation. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +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 variant is also available: + + $ gcloud alpha apphub operations describe + diff --git a/gcloud/apphub/operations/help b/gcloud/apphub/operations/help new file mode 100644 index 000000000..44a6915ef --- /dev/null +++ b/gcloud/apphub/operations/help @@ -0,0 +1,29 @@ +NAME + gcloud apphub operations - manage App Hub Operations + (long-running operations) + +SYNOPSIS + gcloud apphub operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Operations (long-running operations). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an Apphub operation (long-running operation). + + list + List Apphub operations (long-running operations). + +NOTES + This variant is also available: + + $ gcloud alpha apphub operations + diff --git a/gcloud/apphub/operations/list b/gcloud/apphub/operations/list new file mode 100644 index 000000000..84fb846d0 --- /dev/null +++ b/gcloud/apphub/operations/list @@ -0,0 +1,81 @@ +NAME + gcloud apphub operations list - list Apphub operations + (long-running operations) + +SYNOPSIS + gcloud apphub operations list --location=LOCATION [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub operations (long-running operations). + +EXAMPLES + To list all operations, run: + + $ gcloud apphub operations list + +REQUIRED FLAGS + Location resource - Location. This represents a Cloud 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 --location 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. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub operations list + diff --git a/gcloud/apphub/service-projects/add b/gcloud/apphub/service-projects/add new file mode 100644 index 000000000..ad35eefd2 --- /dev/null +++ b/gcloud/apphub/service-projects/add @@ -0,0 +1,68 @@ +NAME + gcloud apphub service-projects add - add an Apphub service project + +SYNOPSIS + gcloud apphub service-projects add (SERVICE_PROJECT : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an Apphub service project. + +EXAMPLES + To add the service project my-service-project to the host project + my-host-project, run: + + $ gcloud apphub service-projects add my-service-project \ + --project=my-host-project + +POSITIONAL ARGUMENTS + ServiceProjectAttachment resource - The Service Project ID. 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 service_project 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. + + SERVICE_PROJECT + ID of the ServiceProjectAttachment or fully qualified identifier for + the ServiceProjectAttachment. + + To set the service_project attribute: + ▸ provide the argument service_project on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the ServiceProjectAttachment. + + To set the location attribute: + ▸ provide the argument service_project on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ Service project attachments only support global location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 variant is also available: + + $ gcloud alpha apphub service-projects add + diff --git a/gcloud/apphub/service-projects/describe b/gcloud/apphub/service-projects/describe new file mode 100644 index 000000000..6e79caa56 --- /dev/null +++ b/gcloud/apphub/service-projects/describe @@ -0,0 +1,64 @@ +NAME + gcloud apphub service-projects describe - describe an Apphub service + project + +SYNOPSIS + gcloud apphub service-projects describe + (SERVICE_PROJECT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub service project. + +EXAMPLES + To describe the service project my-service-project attached to the host + project my-host-project, run: + + $ gcloud apphub service-projects describe my-service-project \ + --project=my-host-project + +POSITIONAL ARGUMENTS + ServiceProjectAttachment resource - The Service Project ID. 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 service_project 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. + + SERVICE_PROJECT + ID of the ServiceProjectAttachment or fully qualified identifier for + the ServiceProjectAttachment. + + To set the service_project attribute: + ▸ provide the argument service_project on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the ServiceProjectAttachment. + + To set the location attribute: + ▸ provide the argument service_project on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ Service project attachments only support global location. + +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 variant is also available: + + $ gcloud alpha apphub service-projects describe + diff --git a/gcloud/apphub/service-projects/detach b/gcloud/apphub/service-projects/detach new file mode 100644 index 000000000..96a0be402 --- /dev/null +++ b/gcloud/apphub/service-projects/detach @@ -0,0 +1,27 @@ +NAME + gcloud apphub service-projects detach - detach an Apphub service project + +SYNOPSIS + gcloud apphub service-projects detach [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Detach an Apphub service project. + +EXAMPLES + To detach the service project my-service-project, run: + + $ gcloud apphub service-projects detach --project=my-service-project + +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 variant is also available: + + $ gcloud alpha apphub service-projects detach + diff --git a/gcloud/apphub/service-projects/help b/gcloud/apphub/service-projects/help new file mode 100644 index 000000000..9befe2180 --- /dev/null +++ b/gcloud/apphub/service-projects/help @@ -0,0 +1,40 @@ +NAME + gcloud apphub service-projects - manage App Hub Service Projects + +SYNOPSIS + gcloud apphub service-projects COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing App Hub Service Projects. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add + Add an Apphub service project. + + describe + Describe an Apphub service project. + + detach + Detach an Apphub service project. + + list + List Apphub service projects. + + lookup + Lookup an Apphub service project. + + remove + Remove an Apphub service project. + +NOTES + This variant is also available: + + $ gcloud alpha apphub service-projects + diff --git a/gcloud/apphub/service-projects/list b/gcloud/apphub/service-projects/list new file mode 100644 index 000000000..b763b3f28 --- /dev/null +++ b/gcloud/apphub/service-projects/list @@ -0,0 +1,82 @@ +NAME + gcloud apphub service-projects list - list Apphub service projects + +SYNOPSIS + gcloud apphub service-projects list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub service projects. + +EXAMPLES + To list all service projects attached to the host project my-host-project, + run: + + $ gcloud apphub service-projects list --project=my-host-project + +FLAGS + Location resource - Location. This represents a Cloud 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 --location on the command line with a fully + specified name; + ◆ Service project attachments only support global location with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ Service project attachments only support global 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. + + --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. + +NOTES + This variant is also available: + + $ gcloud alpha apphub service-projects list + diff --git a/gcloud/apphub/service-projects/lookup b/gcloud/apphub/service-projects/lookup new file mode 100644 index 000000000..109437864 --- /dev/null +++ b/gcloud/apphub/service-projects/lookup @@ -0,0 +1,27 @@ +NAME + gcloud apphub service-projects lookup - lookup an Apphub service project + +SYNOPSIS + gcloud apphub service-projects lookup [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lookup an Apphub service project. + +EXAMPLES + To lookup the service project my-service-project, run: + + $ gcloud apphub service-projects lookup --project=my-service-project + +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 variant is also available: + + $ gcloud alpha apphub service-projects lookup + diff --git a/gcloud/apphub/service-projects/remove b/gcloud/apphub/service-projects/remove new file mode 100644 index 000000000..e610984ae --- /dev/null +++ b/gcloud/apphub/service-projects/remove @@ -0,0 +1,69 @@ +NAME + gcloud apphub service-projects remove - remove an Apphub service project + +SYNOPSIS + gcloud apphub service-projects remove + (SERVICE_PROJECT : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove an Apphub service project. + +EXAMPLES + To remove the service project my-service-project from the host project + my-host-project, run: + + $ gcloud apphub service-projects remove my-service-project \ + --project=my-host-project + +POSITIONAL ARGUMENTS + ServiceProjectAttachment resource - The Service Project ID. 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 service_project 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. + + SERVICE_PROJECT + ID of the ServiceProjectAttachment or fully qualified identifier for + the ServiceProjectAttachment. + + To set the service_project attribute: + ▸ provide the argument service_project on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the ServiceProjectAttachment. + + To set the location attribute: + ▸ provide the argument service_project on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ Service project attachments only support global location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 variant is also available: + + $ gcloud alpha apphub service-projects remove + diff --git a/gcloud/artifacts/docker/upgrade/help b/gcloud/artifacts/docker/upgrade/help index fb551cf8d..5fa13c74c 100644 --- a/gcloud/artifacts/docker/upgrade/help +++ b/gcloud/artifacts/docker/upgrade/help @@ -12,11 +12,29 @@ DESCRIPTION $ gcloud artifacts docker upgrade print-iam-policy gcr.io \ --project=my-project + To migrate a project from Container Registry to Artifact Registry using + gcr.io repos: + + $ gcloud artifacts docker upgrade migrate --projects=my-project + + To migrate a project from Container Registry to Artifact Registry using + pkg.dev repos: + + $ gcloud artifacts docker upgrade migrate \ + --from-gcr-io=gcr.io/from-project \ + --to-pkg-dev=to-project/to-repo + GCLOUD WIDE FLAGS These flags are available to all commands: --help. Run $ gcloud help for details. +COMMANDS + COMMAND is one of the following: + + migrate + Migrate projects from Container Registry to Artifact Registry. + NOTES This variant is also available: diff --git a/gcloud/artifacts/docker/upgrade/migrate b/gcloud/artifacts/docker/upgrade/migrate new file mode 100644 index 000000000..59885b150 --- /dev/null +++ b/gcloud/artifacts/docker/upgrade/migrate @@ -0,0 +1,73 @@ +NAME + gcloud artifacts docker upgrade migrate - migrate projects from Container + Registry to Artifact Registry + +SYNOPSIS + gcloud artifacts docker upgrade migrate [--copy-only] + [--from-gcr=GCR_HOST/PROJECT_ID] [--last-uploaded-versions=N] + [--max-threads=MAX_THREADS; default=8] [--projects=PROJECTS] + [--recent-images=NUM_DAYS] [--skip-iam-update] + [--to-pkg-dev=PROJECT_ID/REPOSITORY_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Migrate projects from Container Registry to Artifact Registry + +EXAMPLES + To migrate a project my-project using gcr.io repositories: + + $ gcloud artifacts docker upgrade migrate --projects=my-project + + To migrate several projects using gcr.io repositories: + + $ gcloud artifacts docker upgrade migrate \ + --projects=my-project1,my-project2,my-project3 + + To migrate a project using pkg.dev repositories: + + $ gcloud artifacts docker upgrade migrate \ + --from-gcr=gcr.io/project1 --to-pkg-dev=project2/repo_name + +FLAGS + --copy-only + Only perform image copying + + --from-gcr=GCR_HOST/PROJECT_ID + Container Registry host + project to copy from. This flag is only used + when migrating to pkg.dev repos. Example: gcr.io/my-project + + --last-uploaded-versions=N + Only copy the N most recently uploaded versions of each image. More + than N images may be copied if new images are uploaded during + migration. + + --max-threads=MAX_THREADS; default=8 + Max number of images to copy simultaneously. Consider quota usage when + increasing this + + --projects=PROJECTS + Comma seperated list of Container Registry projects to migrate to + Artifact Registry gcr.io repositories. + + --recent-images=NUM_DAYS + Only copy images pulled or pushed in the last NUM_DAYS days. NUM_DAYS + must be between 30 and 90 inclusive. + + --skip-iam-update + Migrate without changing iam-policy. Users without Artifact Registry + permissions will not have access to migrated images. + + --to-pkg-dev=PROJECT_ID/REPOSITORY_ID + Artifact Registry pkg.dev project ID and repository ID to copy to. + Example: my-project/my-repo + +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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/files/download b/gcloud/artifacts/files/download new file mode 100644 index 000000000..ef16a21db --- /dev/null +++ b/gcloud/artifacts/files/download @@ -0,0 +1,88 @@ +NAME + gcloud artifacts files download - download an Artifact Registry file + +SYNOPSIS + gcloud artifacts files download + (FILE : --location=LOCATION --repository=REPOSITORY) + --destination=DESTINATION [--allow-overwrite] + [--local-filename=LOCAL_FILENAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Downloads an Artifact Registry file based on file name. + +EXAMPLES + To download a file named myfile in project my-project under repository + my-repo in us-central1 to the local path ~/: + + $ gcloud artifacts files download --location=us-central1 \ + --project=my-project --repository=my-repo --destination=~/ \ + myfile + + To download a file named myfile in project my-project under repository + my-repo in us-central1 to the local path ~/ with file overwriting enabled: + + $ gcloud artifacts files download --location=us-central1 \ + --project=my-project --repository=my-repo --destination=~/ \ + myfile --allow-overwrite + +POSITIONAL ARGUMENTS + File resource - The Artifact Registry file name. If not specified, the + current artifacts/location is used. 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 file 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. + + FILE + ID of the file or fully qualified identifier for the file. + + To set the name attribute: + ▸ provide the argument file on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the file. + + To set the location attribute: + ▸ provide the argument file on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + + --repository=REPOSITORY + Repository of the file. + + To set the repository attribute: + ▸ provide the argument file on the command line with a fully + specified name; + ▸ provide the argument --repository on the command line; + ▸ set the property artifacts/repository. + +REQUIRED FLAGS + --destination=DESTINATION + The path where you want to download the file. + +OPTIONAL FLAGS + --allow-overwrite + If specified, the command overwrites an existing file + + --local-filename=LOCAL_FILENAME + If specified, the name of the downloaded file on the local system is + set to the value you use for LOCAL_FILENAME. Otherwise the name of the + downloaded file is based on the file name in the registry. + +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. diff --git a/gcloud/artifacts/files/help b/gcloud/artifacts/files/help index 6dbaada4d..0790f5dcb 100644 --- a/gcloud/artifacts/files/help +++ b/gcloud/artifacts/files/help @@ -23,6 +23,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + download + Download an Artifact Registry file. + list List Artifact Registry files. diff --git a/gcloud/artifacts/repositories/create b/gcloud/artifacts/repositories/create index 594644d4a..fbcb8f57d 100644 --- a/gcloud/artifacts/repositories/create +++ b/gcloud/artifacts/repositories/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud artifacts repositories create (REPOSITORY : --location=LOCATION) --repository-format=REPOSITORY_FORMAT [--allow-snapshot-overwrites] - [--async] [--description=DESCRIPTION] [--immutable-tags] - [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] + [--async] [--description=DESCRIPTION] [--disable-remote-validation] + [--immutable-tags] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [--mode=MODE; default="NONE"] [--remote-apt-repo=REMOTE_APT_REPO] [--remote-apt-repo-path=REMOTE_APT_REPO_PATH] [--remote-docker-repo=REMOTE_DOCKER_REPO] @@ -108,6 +108,11 @@ OPTIONAL FLAGS --description=DESCRIPTION Description for the repository. + --disable-remote-validation + Do not make an HTTP request to validate the remote upstream. Not + recommended when setting a custom remote upstream unless you are + absolutely sure your upstream URI and any auth is valid. + --immutable-tags (Docker only) Prevent changes to tagged images in the repository. Tags cannot be deleted or moved to a different image digest, and tagged @@ -148,15 +153,21 @@ OPTIONAL FLAGS --remote-docker-repo=REMOTE_DOCKER_REPO (Docker only) Repo upstream for docker remote repository. - REMOTE_DOCKER_REPO must be one of: [docker-hub]. + REMOTE_DOCKER_REPO can be either: + ◆ one of the following enums: [docker-hub]. + ◆ an http/https custom registry uri (ex: https://my.docker.registry) --remote-mvn-repo=REMOTE_MVN_REPO (Maven only) Repo upstream for maven remote repository. REMOTE_MVN_REPO - must be one of: [maven-central]. + can be either: + ◆ one of the following enums: [maven-central]. + ◆ an http/https custom registry uri (ex: https://my.maven.registry) --remote-npm-repo=REMOTE_NPM_REPO - (Npm only) Repo upstream for npm remote repository. REMOTE_NPM_REPO - must be one of: [npmjs]. + (Npm only) Repo upstream for npm remote repository. REMOTE_NPM_REPO can + be either: + ◆ one of the following enums: [npmjs]. + ◆ an http/https custom registry uri (ex: https://my.npm.registry) --remote-password-secret-version=REMOTE_PASSWORD_SECRET_VERSION Secret Manager secret version that contains password for the remote @@ -164,7 +175,9 @@ OPTIONAL FLAGS --remote-python-repo=REMOTE_PYTHON_REPO (Python only) Repo upstream for python remote repository. - REMOTE_PYTHON_REPO must be one of: [pypi]. + REMOTE_PYTHON_REPO can be either: + ◆ one of the following enums: [pypi]. + ◆ an http/https custom registry uri (ex: https://my.python.registry) --remote-repo-config-desc=REMOTE_REPO_CONFIG_DESC The description for the remote repository config. diff --git a/gcloud/artifacts/repositories/update b/gcloud/artifacts/repositories/update index 6bbb29cbf..fd0fa47f6 100644 --- a/gcloud/artifacts/repositories/update +++ b/gcloud/artifacts/repositories/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud artifacts repositories update (REPOSITORY : --location=LOCATION) - [--description=DESCRIPTION] [--immutable-tags] + [--description=DESCRIPTION] [--disable-remote-validation] + [--immutable-tags] [--remote-password-secret-version=REMOTE_PASSWORD_SECRET_VERSION] [--remote-username=REMOTE_USERNAME] [--update-labels=[KEY=VALUE,...]] [--upstream-policy-file=FILE] @@ -63,6 +64,11 @@ FLAGS --description=DESCRIPTION Description for the repository. + --disable-remote-validation + Do not make an HTTP request to validate the remote upstream. Not + recommended when setting a custom remote upstream unless you are + absolutely sure your upstream URI and any auth is valid. + --immutable-tags (Docker only) Prevent changes to tagged images in the repository. Tags cannot be deleted or moved to a different image digest, and tagged diff --git a/gcloud/beta/alloydb/backups/create b/gcloud/beta/alloydb/backups/create index d6c70d774..1bd9245bf 100644 --- a/gcloud/beta/alloydb/backups/create +++ b/gcloud/beta/alloydb/backups/create @@ -1,5 +1,5 @@ NAME - gcloud beta alloydb backups create - creates a new AlloyDB backup within a + gcloud beta alloydb backups create - create a new AlloyDB backup within a given project SYNOPSIS @@ -10,7 +10,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Creates a new AlloyDB backup within a given project. + (BETA) Create a new AlloyDB backup within a given project. EXAMPLES To create a new backup, run: diff --git a/gcloud/beta/alloydb/backups/help b/gcloud/beta/alloydb/backups/help index 7e15cb960..9f51c6d7f 100644 --- a/gcloud/beta/alloydb/backups/help +++ b/gcloud/beta/alloydb/backups/help @@ -17,7 +17,7 @@ COMMANDS COMMAND is one of the following: create - (BETA) Creates a new AlloyDB backup within a given project. + (BETA) Create a new AlloyDB backup within a given project. delete (BETA) Deletes an AlloyDB backup within a given project. diff --git a/gcloud/beta/artifacts/docker/upgrade/help b/gcloud/beta/artifacts/docker/upgrade/help index 3dc94a96c..eb1c271ef 100644 --- a/gcloud/beta/artifacts/docker/upgrade/help +++ b/gcloud/beta/artifacts/docker/upgrade/help @@ -12,6 +12,18 @@ DESCRIPTION $ gcloud beta artifacts docker upgrade print-iam-policy gcr.io \ --project=my-project + To migrate a project from Container Registry to Artifact Registry using + gcr.io repos: + + $ gcloud beta artifacts docker upgrade migrate --projects=my-project + + To migrate a project from Container Registry to Artifact Registry using + pkg.dev repos: + + $ gcloud beta artifacts docker upgrade migrate \ + --from-gcr-io=gcr.io/from-project \ + --to-pkg-dev=to-project/to-repo + GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/builds/connections/create/bitbucket-cloud b/gcloud/beta/builds/connections/create/bitbucket-cloud new file mode 100644 index 000000000..a5c141590 --- /dev/null +++ b/gcloud/beta/builds/connections/create/bitbucket-cloud @@ -0,0 +1,109 @@ +NAME + gcloud beta builds connections create bitbucket-cloud - create a Cloud + Build Connection for Bitbucket Cloud + +SYNOPSIS + gcloud beta builds connections create bitbucket-cloud + (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + --workspace=WORKSPACE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Cloud Build Connection for Bitbucket Cloud. + + A Bitbucket Cloud Connection can be created by using a + repository/project/workspace access token with + repository_read,repository_admin, pullrequest_read, webhook scope + permission and a repository/project/workspace access token with + repository_read scope permission. + +EXAMPLES + To create a Bitbucket Cloud connection, provide all the required + parameters: + + $ gcloud beta builds connections create bitbucket-cloud \ + my-bitbucket-conn --project=myproj --region=us-central1 \ + --workspace=my-workspace \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read,repository_admin, + pullrequest_read, webhook repository/project/workspace access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read repository/project/workspace + access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Cloud. + + --workspace=WORKSPACE + Workspace of the Bitbucket Cloud instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections create bitbucket-cloud + + $ gcloud alpha builds connections create bitbucket-cloud + diff --git a/gcloud/beta/builds/connections/create/bitbucket-data-center b/gcloud/beta/builds/connections/create/bitbucket-data-center new file mode 100644 index 000000000..9033c4083 --- /dev/null +++ b/gcloud/beta/builds/connections/create/bitbucket-data-center @@ -0,0 +1,140 @@ +NAME + gcloud beta builds connections create bitbucket-data-center - create a + Cloud Build Connection for Bitbucket Data Center + +SYNOPSIS + gcloud beta builds connections create bitbucket-data-center + (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] + [--host-uri=HOST_URI] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE + : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Cloud Build Connection for Bitbucket Data Center. + + A Bitbucket Data Center Connection can be created by using a personal + access token with REPO_ADMIN scope permission. A REPO_READ scoped personal + access token will also be required. + + If the Bitbucket Data Center can only be accessed within a VPC, a Service + Directory service resource can be provided for connecting to it. + +EXAMPLES + To create a Bitbucket Data Center connection, provide all the required + parameters: + + $ gcloud beta builds connections create bitbucket-data-center \ + my-bitbucket-conn --project=myproj --region=us-central1 \ + --host-uri=https://bitbucket-server.net \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + + To create a Bitbucket Data Center connection for a private Bitbucket Data + Center server. Provide the service-directory-service and ssl-ca-file as + well: + + $ gcloud beta builds connections create bitbucket-data-center \ + my-private-bitbucket-conn \ + --host-uri=https://my.private-bitbucket-server.net \ + --project=myproj --region=us-central1 \ + --service-directory-service=projects/myproj/namespaces/x/\ + services/mysds --ssl-ca-file=mycertificate.crt \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_ADMIN personal access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_READ personal access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Data Center. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --host-uri=HOST_URI + URI of the Bitbucket Data Center instance. + + Group of arguments for configuring access through Service Directory. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the Bitbucket + Data Center. Necessary only if the server has no public access from + the internet. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections create bitbucket-data-center + + $ gcloud alpha builds connections create bitbucket-data-center + diff --git a/gcloud/beta/builds/connections/create/help b/gcloud/beta/builds/connections/create/help index 11317f047..6702b24dc 100644 --- a/gcloud/beta/builds/connections/create/help +++ b/gcloud/beta/builds/connections/create/help @@ -16,6 +16,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (BETA) Create a Cloud Build Connection for Bitbucket Cloud. + + bitbucket-data-center + (BETA) Create a Cloud Build Connection for Bitbucket Data Center. + github (BETA) Create a Cloud Build Connection of type GitHub. diff --git a/gcloud/beta/builds/connections/update/bitbucket-cloud b/gcloud/beta/builds/connections/update/bitbucket-cloud new file mode 100644 index 000000000..8950430b5 --- /dev/null +++ b/gcloud/beta/builds/connections/update/bitbucket-cloud @@ -0,0 +1,104 @@ +NAME + gcloud beta builds connections update bitbucket-cloud - update a Cloud + Build Connection of type Bitbucket Cloud + +SYNOPSIS + gcloud beta builds connections update bitbucket-cloud + (CONNECTION : --region=REGION) [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] + [--workspace=WORKSPACE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Cloud Build Connection of type Bitbucket Cloud. + +EXAMPLES + To update the workspace, provide the connection name and the workspace + name: + + $ gcloud beta builds connections update bitbucket-cloud \ + my-bbc-conn --region=us-west1 --workspace=my-workspace + + To update the authorization token, provide the connection name and the new + authorization token secret version. + + $ gcloud beta builds connections update bitbucket-cloud \ + my-bbc-conn --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read,repository_admin, + pullrequest_read, webhook access token. It can be a repository, project + or workspace access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read access token. It can be a + repository, project or workspace access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Cloud. + + --workspace=WORKSPACE + Workspace of the Bitbucket Cloud instance. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections update bitbucket-cloud + + $ gcloud alpha builds connections update bitbucket-cloud + diff --git a/gcloud/beta/builds/connections/update/bitbucket-data-center b/gcloud/beta/builds/connections/update/bitbucket-data-center new file mode 100644 index 000000000..0266920a0 --- /dev/null +++ b/gcloud/beta/builds/connections/update/bitbucket-data-center @@ -0,0 +1,105 @@ +NAME + gcloud beta builds connections update bitbucket-data-center - update a + Cloud Build Connection of type Bitbucket Data Center + +SYNOPSIS + gcloud beta builds connections update bitbucket-data-center + (CONNECTION : --region=REGION) [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--host-uri=HOST_URI] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Cloud Build Connection of type Bitbucket Data Center. + +EXAMPLES + To update the ssl_ca, provide the connection name and the ssl_ca file: + + $ gcloud beta builds connections update bitbucket-data-center \ + my-gle-conn --region=us-west1 --ssl-ca-file=mycertificate.crt + + To update the authorization token, provide the connection name and the new + authorization token secret version name. + + $ gcloud beta builds connections update bitbucket-data-center \ + my-gle-conn --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_ADMIN personal access token. + + --host-uri=HOST_URI + URI of the Bitbucket Data Center instance. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_READ personal access token. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the Bitbucket + Data Center. Necessary only if the server has no public access from the + internet. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections update bitbucket-data-center + + $ gcloud alpha builds connections update bitbucket-data-center + diff --git a/gcloud/beta/builds/connections/update/help b/gcloud/beta/builds/connections/update/help index 26a5da5ef..3fbf7f023 100644 --- a/gcloud/beta/builds/connections/update/help +++ b/gcloud/beta/builds/connections/update/help @@ -16,6 +16,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (BETA) Update a Cloud Build Connection of type Bitbucket Cloud. + + bitbucket-data-center + (BETA) Update a Cloud Build Connection of type Bitbucket Data Center. + github (BETA) Update a Cloud Build Connection of type GitHub. diff --git a/gcloud/beta/builds/triggers/create/bitbucket-cloud b/gcloud/beta/builds/triggers/create/bitbucket-cloud new file mode 100644 index 000000000..f73756478 --- /dev/null +++ b/gcloud/beta/builds/triggers/create/bitbucket-cloud @@ -0,0 +1,223 @@ +NAME + gcloud beta builds triggers create bitbucket-cloud - create a build trigger + for a 2nd-gen Bitbucket Cloud repository + +SYNOPSIS + gcloud beta builds triggers create bitbucket-cloud + (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED"]) (--build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger for a 2nd-gen Bitbucket Cloud repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud beta builds triggers create bitbucket-cloud \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" --region=us-central1 + + To create a pull request trigger with a 2nd-gen repository for main: + + $ gcloud beta builds triggers create bitbucket-cloud \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ + --pull-request-pattern="^main$" --region=us-central1 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. Note: Region must be specified in 2nd gen repo; global is + not supported. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. For + example: + + $ gcloud beta builds triggers create bitbucket-cloud ... \ + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + +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 beta and might change without notice. These + variants are also available: + + $ gcloud builds triggers create bitbucket-cloud + + $ gcloud alpha builds triggers create bitbucket-cloud + diff --git a/gcloud/beta/builds/triggers/create/bitbucket-data-center b/gcloud/beta/builds/triggers/create/bitbucket-data-center new file mode 100644 index 000000000..98dfbc81c --- /dev/null +++ b/gcloud/beta/builds/triggers/create/bitbucket-data-center @@ -0,0 +1,224 @@ +NAME + gcloud beta builds triggers create bitbucket-data-center - create a build + trigger for a 2nd-gen Bitbucket Data Center repository + +SYNOPSIS + gcloud beta builds triggers create bitbucket-data-center + (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED"]) (--build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger for a 2nd-gen Bitbucket Data Center + repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud beta builds triggers create bitbucket-data-center \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" --region=us-central1 + + To create a pull request trigger with a 2nd-gen repository for main: + + $ gcloud beta builds triggers create bitbucket-data-center \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ + --pull-request-pattern="^main$" --region=us-central1 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. Note: Region must be specified in 2nd gen repo; global is + not supported. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. For + example: + + $ gcloud beta builds triggers create bitbucket-data-center ... \ + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + +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 beta and might change without notice. These + variants are also available: + + $ gcloud builds triggers create bitbucket-data-center + + $ gcloud alpha builds triggers create bitbucket-data-center + diff --git a/gcloud/beta/builds/triggers/create/help b/gcloud/beta/builds/triggers/create/help index cb1b5ebef..57db58fa3 100644 --- a/gcloud/beta/builds/triggers/create/help +++ b/gcloud/beta/builds/triggers/create/help @@ -16,6 +16,13 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (BETA) Create a build trigger for a 2nd-gen Bitbucket Cloud repository. + + bitbucket-data-center + (BETA) Create a build trigger for a 2nd-gen Bitbucket Data Center + repository. + bitbucketserver (BETA) Create a build trigger for a Bitbucket Server repository. diff --git a/gcloud/beta/builds/triggers/update/bitbucket-cloud b/gcloud/beta/builds/triggers/update/bitbucket-cloud new file mode 100644 index 000000000..17538e215 --- /dev/null +++ b/gcloud/beta/builds/triggers/update/bitbucket-cloud @@ -0,0 +1,253 @@ +NAME + gcloud beta builds triggers update bitbucket-cloud - updates Bitbucket + Cloud trigger used by Cloud Build + +SYNOPSIS + gcloud beta builds triggers update bitbucket-cloud + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates Bitbucket Cloud trigger used by Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud beta builds triggers update bitbucket-cloud my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 beta and might change without notice. These + variants are also available: + + $ gcloud builds triggers update bitbucket-cloud + + $ gcloud alpha builds triggers update bitbucket-cloud + diff --git a/gcloud/beta/builds/triggers/update/bitbucket-data-center b/gcloud/beta/builds/triggers/update/bitbucket-data-center new file mode 100644 index 000000000..feac36aaf --- /dev/null +++ b/gcloud/beta/builds/triggers/update/bitbucket-data-center @@ -0,0 +1,255 @@ +NAME + gcloud beta builds triggers update bitbucket-data-center - updates + Bitbucket Data Center trigger used by Cloud Build + +SYNOPSIS + gcloud beta builds triggers update bitbucket-data-center + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates Bitbucket Data Center trigger used by Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud beta builds triggers update bitbucket-data-center \ + my-trigger --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud beta builds triggers update bitbucket-data-center \ + my-trigger --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud beta builds triggers update bitbucket-data-center \ + my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud beta builds triggers update bitbucket-data-center \ + my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 beta and might change without notice. These + variants are also available: + + $ gcloud builds triggers update bitbucket-data-center + + $ gcloud alpha builds triggers update bitbucket-data-center + diff --git a/gcloud/beta/builds/triggers/update/help b/gcloud/beta/builds/triggers/update/help index fbf2bf5db..ba0c8cba5 100644 --- a/gcloud/beta/builds/triggers/update/help +++ b/gcloud/beta/builds/triggers/update/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + (BETA) Updates Bitbucket Cloud trigger used by Cloud Build. + + bitbucket-data-center + (BETA) Updates Bitbucket Data Center trigger used by Cloud Build. + bitbucketserver (BETA) Updates Bitbucket Server trigger used by Cloud Build. diff --git a/gcloud/beta/compute/health-checks/create/http b/gcloud/beta/compute/health-checks/create/http index 340403613..9ed9b27e1 100644 --- a/gcloud/beta/compute/health-checks/create/http +++ b/gcloud/beta/compute/health-checks/create/http @@ -9,7 +9,7 @@ SYNOPSIS [--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--host=HOST] [--proxy-header=PROXY_HEADER; default="NONE"] [--request-path=REQUEST_PATH; default="/"] [--response=RESPONSE] - [--timeout=TIMEOUT; default="5s"] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT; default="5s"] [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] [--global | --region=REGION] [--port=PORT; default=80 --port-name=PORT_NAME --use-serving-port] @@ -69,6 +69,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/beta/compute/health-checks/create/https b/gcloud/beta/compute/health-checks/create/https index c18f8e328..c66b34f1a 100644 --- a/gcloud/beta/compute/health-checks/create/https +++ b/gcloud/beta/compute/health-checks/create/https @@ -9,7 +9,7 @@ SYNOPSIS [--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--host=HOST] [--proxy-header=PROXY_HEADER; default="NONE"] [--request-path=REQUEST_PATH; default="/"] [--response=RESPONSE] - [--timeout=TIMEOUT; default="5s"] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT; default="5s"] [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] [--global | --region=REGION] [--port=PORT; default=80 --port-name=PORT_NAME --use-serving-port] @@ -69,6 +69,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/beta/compute/health-checks/create/tcp b/gcloud/beta/compute/health-checks/create/tcp index 9887a6576..d619de437 100644 --- a/gcloud/beta/compute/health-checks/create/tcp +++ b/gcloud/beta/compute/health-checks/create/tcp @@ -8,7 +8,8 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD; default=2] [--proxy-header=PROXY_HEADER; default="NONE"] [--request=REQUEST] - [--response=RESPONSE] [--timeout=TIMEOUT; default="5s"] + [--response=RESPONSE] [--source-regions=REGION,...,[...]] + [--timeout=TIMEOUT; default="5s"] [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] [--global | --region=REGION] [--port=PORT; default=80 --port-name=PORT_NAME --use-serving-port] @@ -72,6 +73,18 @@ FLAGS successful handshake, only configure --response to match an explicit --request. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT; default="5s" If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/beta/compute/health-checks/update/http b/gcloud/beta/compute/health-checks/update/http index c6b02fdb3..c8c8e41c8 100644 --- a/gcloud/beta/compute/health-checks/update/http +++ b/gcloud/beta/compute/health-checks/update/http @@ -6,7 +6,8 @@ SYNOPSIS [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD] [--host=HOST] [--proxy-header=PROXY_HEADER] - [--request-path=REQUEST_PATH] [--response=RESPONSE] [--timeout=TIMEOUT] + [--request-path=REQUEST_PATH] [--response=RESPONSE] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT] [--unhealthy-threshold=UNHEALTHY_THRESHOLD] [--global | --region=REGION] [--port=PORT --port-name=PORT_NAME --use-serving-port] @@ -66,6 +67,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/beta/compute/health-checks/update/https b/gcloud/beta/compute/health-checks/update/https index 325dae054..afafeb9f5 100644 --- a/gcloud/beta/compute/health-checks/update/https +++ b/gcloud/beta/compute/health-checks/update/https @@ -7,7 +7,8 @@ SYNOPSIS [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD] [--host=HOST] [--proxy-header=PROXY_HEADER] - [--request-path=REQUEST_PATH] [--response=RESPONSE] [--timeout=TIMEOUT] + [--request-path=REQUEST_PATH] [--response=RESPONSE] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT] [--unhealthy-threshold=UNHEALTHY_THRESHOLD] [--global | --region=REGION] [--port=PORT --port-name=PORT_NAME --use-serving-port] @@ -67,6 +68,18 @@ FLAGS empty, presence of specified string in first 1024 characters of response body determines health. Only ASCII characters allowed. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/beta/compute/health-checks/update/tcp b/gcloud/beta/compute/health-checks/update/tcp index 6edbae6ab..eb69b6874 100644 --- a/gcloud/beta/compute/health-checks/update/tcp +++ b/gcloud/beta/compute/health-checks/update/tcp @@ -6,7 +6,8 @@ SYNOPSIS [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] [--enable-logging] [--healthy-threshold=HEALTHY_THRESHOLD] [--proxy-header=PROXY_HEADER] [--request=REQUEST] [--response=RESPONSE] - [--timeout=TIMEOUT] [--unhealthy-threshold=UNHEALTHY_THRESHOLD] + [--source-regions=REGION,...,[...]] [--timeout=TIMEOUT] + [--unhealthy-threshold=UNHEALTHY_THRESHOLD] [--global | --region=REGION] [--port=PORT --port-name=PORT_NAME --use-serving-port] [GCLOUD_WIDE_FLAG ...] @@ -70,6 +71,18 @@ FLAGS --request. Setting this to an empty string will clear any existing response value. + --source-regions=REGION,...,[...] + Define the list of Google Cloud regions from which health checks are + performed. This option is supported only for global health checks that + will be referenced by DNS routing policies. If specified, the + --check-interval field should be at least 30 seconds. The + --proxy-header and --request fields (for TCP health checks) are not + supported with this option. + + If --source-regions is specified for a health check, then that health + check cannot be used by a backend service or by a managed instance + group (for autohealing). + --timeout=TIMEOUT If Google Compute Engine doesn't receive a healthy response from the instance by the time specified by the value of this flag, the health diff --git a/gcloud/beta/compute/project-info/update b/gcloud/beta/compute/project-info/update index c9d2ebcfa..f2b92e46a 100644 --- a/gcloud/beta/compute/project-info/update +++ b/gcloud/beta/compute/project-info/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta compute project-info update + [--cloud-armor-tier=CLOUD_ARMOR_TIER] [--default-network-tier=DEFAULT_NETWORK_TIER] [--managed-protection-tier=MANAGED_PROTECTION_TIER] [GCLOUD_WIDE_FLAG ...] @@ -13,12 +14,16 @@ DESCRIPTION Engine project resource. FLAGS + --cloud-armor-tier=CLOUD_ARMOR_TIER + Cloud armor tier to assign to the project. CLOUD_ARMOR_TIER must be one + of: CA_STANDARD, CA_ENTERPRISE_PAYGO. + --default-network-tier=DEFAULT_NETWORK_TIER The default network tier to assign to the project. DEFAULT_NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. --managed-protection-tier=MANAGED_PROTECTION_TIER - The maanged protection tier to assign to the project. + Managed protection tier to assign to the project. MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO. GCLOUD WIDE FLAGS diff --git a/gcloud/beta/datastream/streams/create b/gcloud/beta/datastream/streams/create index e3ee449b3..6857a1e21 100644 --- a/gcloud/beta/datastream/streams/create +++ b/gcloud/beta/datastream/streams/create @@ -82,11 +82,14 @@ REQUIRED FLAGS Exactly one of these must be specified: --backfill-none - Do not automatically backfill any objects. + Do not automatically backfill any objects. This flag is equivalent to + selecting the Manual backfill type in the Google Cloud console. --backfill-all Automatically backfill objects included in the stream source - configuration. Specific objects can be excluded. + configuration. Specific objects can be excluded. This flag is + equivalent to selecting the Automatic backfill type in the Google + Cloud console. At most one of these can be specified: diff --git a/gcloud/beta/datastream/streams/update b/gcloud/beta/datastream/streams/update index edcdf3b6f..67a9e8dc1 100644 --- a/gcloud/beta/datastream/streams/update +++ b/gcloud/beta/datastream/streams/update @@ -103,11 +103,14 @@ FLAGS At most one of these can be specified: --backfill-none - Do not automatically backfill any objects. + Do not automatically backfill any objects. This flag is equivalent to + selecting the Manual backfill type in the Google Cloud console. --backfill-all Automatically backfill objects included in the stream source - configuration. Specific objects can be excluded. + configuration. Specific objects can be excluded. This flag is + equivalent to selecting the Automatic backfill type in the Google + Cloud console. At most one of these can be specified: diff --git a/gcloud/beta/iam/roles/create b/gcloud/beta/iam/roles/create index c7cb26491..e96fc6881 100644 --- a/gcloud/beta/iam/roles/create +++ b/gcloud/beta/iam/roles/create @@ -28,17 +28,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to create. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to create. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to create. + Organization of the role you want to create. --project=PROJECT_ID - The project of the role you want to create. + Project of the role you want to create. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/iam/roles/delete b/gcloud/beta/iam/roles/delete index 75f492813..507a33d7d 100644 --- a/gcloud/beta/iam/roles/delete +++ b/gcloud/beta/iam/roles/delete @@ -25,17 +25,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to delete. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to delete. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to delete. + Organization of the role you want to delete. --project=PROJECT_ID - The project of the role you want to delete. + Project of the role you want to delete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/iam/roles/describe b/gcloud/beta/iam/roles/describe index 97757a62f..ffb89124d 100644 --- a/gcloud/beta/iam/roles/describe +++ b/gcloud/beta/iam/roles/describe @@ -32,18 +32,18 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the role to describe. Curated roles example: roles/viewer. - Custom roles example: CustomRole. For custom roles, you must also - specify the --organization or --project flag. + ID of the role to describe. Curated roles example: roles/viewer. Custom + roles example: CustomRole. For custom roles, you must also specify the + --organization or --project flag. FLAGS At most one of these can be specified: --organization=ORGANIZATION - The organization of the role you want to describe. + Organization of the role you want to describe. --project=PROJECT_ID - The project of the role you want to describe. + Project of the role you want to describe. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/iam/roles/list b/gcloud/beta/iam/roles/list index 257d70afc..f34f73b82 100644 --- a/gcloud/beta/iam/roles/list +++ b/gcloud/beta/iam/roles/list @@ -34,10 +34,10 @@ FLAGS At most one of these can be specified: --organization=ORGANIZATION - The organization of the role you want to list. + Organization of the role you want to list. --project=PROJECT_ID - The project of the role you want to list. + Project of the role you want to list. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/iam/roles/undelete b/gcloud/beta/iam/roles/undelete index 3f7010084..3eea7eae7 100644 --- a/gcloud/beta/iam/roles/undelete +++ b/gcloud/beta/iam/roles/undelete @@ -28,17 +28,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to undelete. For example: CustomRole. You - must also specify the --organization or --project flag. + ID of the custom role to undelete. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to undelete. + Organization of the role you want to undelete. --project=PROJECT_ID - The project of the role you want to undelete. + Project of the role you want to undelete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/iam/roles/update b/gcloud/beta/iam/roles/update index 47a639df8..e1bace3bd 100644 --- a/gcloud/beta/iam/roles/update +++ b/gcloud/beta/iam/roles/update @@ -25,17 +25,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to update. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to update. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to update. + Organization of the role you want to update. --project=PROJECT_ID - The project of the role you want to update. + Project of the role you want to update. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/beta/iam/workforce-pools/create-cred-config b/gcloud/beta/iam/workforce-pools/create-cred-config index 4b34a910b..79181b1b7 100644 --- a/gcloud/beta/iam/workforce-pools/create-cred-config +++ b/gcloud/beta/iam/workforce-pools/create-cred-config @@ -86,13 +86,13 @@ REQUIRED FLAGS OPTIONAL FLAGS --credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME - The subject token field name (key) in a JSON credential source. + Subject token field name (key) in a JSON credential source. --credential-source-headers=[key=value,...] Headers to use when querying the credential-source-url. --credential-source-type=CREDENTIAL_SOURCE_TYPE - The format of the credential source (JSON or text). + Format of the credential source (JSON or text). --subject-token-type=SUBJECT_TOKEN_TYPE The type of token being used for authorization. This defaults to @@ -101,29 +101,29 @@ OPTIONAL FLAGS Arguments for an executable type credential source. --executable-interactive-timeout-millis=EXECUTABLE_INTERACTIVE_TIMEOUT_MILLIS - The timeout duration, in milliseconds, to wait for the executable to + Timeout duration, in milliseconds, to wait for the executable to finish when the command is running in interactive mode. --executable-output-file=EXECUTABLE_OUTPUT_FILE - The absolute path to the file storing the executable response. + Absolute path to the file storing the executable response. --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS - The timeout duration in milliseconds for waiting for the executable - to finish. + Timeout duration, in milliseconds, to wait for the executable to + finish. Service account impersonation options. --service-account=SERVICE_ACCOUNT - The email of the service account to impersonate. + Email of the service account to impersonate. This flag argument must be specified if any of the other arguments in this group are specified. --service-account-token-lifetime-seconds=SERVICE_ACCOUNT_TOKEN_LIFETIME_SECONDS - The desired lifetime duration of the service account access token in - seconds. This defaults to one hour when not provided. If a lifetime - greater than one hour is required, the service account must be added - as an allowed value in an Organization Policy that enforces the + Lifetime duration of the service account access token in seconds. + Defaults to one hour if not specified. If a lifetime greater than one + hour is required, the service account must be added as an allowed + value in an Organization Policy that enforces the constraints/iam.allowServiceAccountCredentialLifetimeExtension constraint. diff --git a/gcloud/beta/iam/workload-identity-pools/create-cred-config b/gcloud/beta/iam/workload-identity-pools/create-cred-config index 1b28192ef..ba567061b 100644 --- a/gcloud/beta/iam/workload-identity-pools/create-cred-config +++ b/gcloud/beta/iam/workload-identity-pools/create-cred-config @@ -106,13 +106,13 @@ OPTIONAL FLAGS The custom Application ID URI for the Azure access token. --credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME - The subject token field name (key) in a JSON credential source. + Subject token field name (key) in a JSON credential source. --credential-source-headers=[key=value,...] Headers to use when querying the credential-source-url. --credential-source-type=CREDENTIAL_SOURCE_TYPE - The format of the credential source (JSON or text). + Format of the credential source (JSON or text). --enable-imdsv2 Adds the AWS IMDSv2 session token Url to the credential source to @@ -125,25 +125,25 @@ OPTIONAL FLAGS Arguments for an executable type credential source. --executable-output-file=EXECUTABLE_OUTPUT_FILE - The absolute path to the file storing the executable response. + Absolute path to the file storing the executable response. --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS - The timeout duration in milliseconds for waiting for the executable - to finish. + Timeout duration, in milliseconds, to wait for the executable to + finish. Service account impersonation options. --service-account=SERVICE_ACCOUNT - The email of the service account to impersonate. + Email of the service account to impersonate. This flag argument must be specified if any of the other arguments in this group are specified. --service-account-token-lifetime-seconds=SERVICE_ACCOUNT_TOKEN_LIFETIME_SECONDS - The desired lifetime duration of the service account access token in - seconds. This defaults to one hour when not provided. If a lifetime - greater than one hour is required, the service account must be added - as an allowed value in an Organization Policy that enforces the + Lifetime duration of the service account access token in seconds. + Defaults to one hour if not specified. If a lifetime greater than one + hour is required, the service account must be added as an allowed + value in an Organization Policy that enforces the constraints/iam.allowServiceAccountCredentialLifetimeExtension constraint. diff --git a/gcloud/beta/metastore/services/create b/gcloud/beta/metastore/services/create index ea0a99038..b47d7e184 100644 --- a/gcloud/beta/metastore/services/create +++ b/gcloud/beta/metastore/services/create @@ -22,6 +22,7 @@ SYNOPSIS --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE | --enable-scheduled-backup --scheduled-backup-cron=SCHEDULED_BACKUP_CRON --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -330,6 +331,39 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + At most one of these can be specified: + + --scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE + Path to a JSON file containing a mapping of scheduled backup + configurations key-value pairs to apply to the scheduled backup. + + For example: + + backup_configs.json + { + "enabled": true, + "cron_schedule": "0 * * * *", + "backup_location": "gs://example-bucket", + "time_zone": "UTC" + } + + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + --enable-scheduled-backup + Enable or disable scheduled backups for the Metastore service. + + --scheduled-backup-cron=SCHEDULED_BACKUP_CRON + Specify the frequency of a scheduled backup of the metastore + service. + + --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION + Set the Cloud Storage URI to store the scheduled backups of the + metastore service. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/metastore/services/update b/gcloud/beta/metastore/services/update index 842b6b1f9..831260b88 100644 --- a/gcloud/beta/metastore/services/update +++ b/gcloud/beta/metastore/services/update @@ -12,6 +12,7 @@ SYNOPSIS --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE | --enable-scheduled-backup --scheduled-backup-cron=SCHEDULED_BACKUP_CRON --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION] [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS, ...] --clear-auxiliary-versions] [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[KEY=VALUE, @@ -199,6 +200,39 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + At most one of these can be specified: + + --scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE + Path to a JSON file containing a mapping of scheduled backup + configurations key-value pairs to apply to the scheduled backup. + + For example: + + backup_configs.json + { + "enabled": true, + "cron_schedule": "0 * * * *", + "backup_location": "gs://example-bucket", + "time_zone": "UTC" + } + + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + --enable-scheduled-backup + Enable or disable scheduled backups for the Metastore service. + + --scheduled-backup-cron=SCHEDULED_BACKUP_CRON + Specify the frequency of a scheduled backup of the metastore + service. + + --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION + Set the Cloud Storage URI to store the scheduled backups of the + metastore service. + Auxiliary versions configuration for the Dataproc Metastore service. When specified, a secondary Hive metastore service is created along with the primary service. diff --git a/gcloud/beta/notebooks/instances/create b/gcloud/beta/notebooks/instances/create index ea163fd97..f63e87f70 100644 --- a/gcloud/beta/notebooks/instances/create +++ b/gcloud/beta/notebooks/instances/create @@ -167,7 +167,7 @@ FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3. + TPU_V2, TPU_V3, NVIDIA_L4. Boot disk configurations. diff --git a/gcloud/beta/notebooks/instances/update b/gcloud/beta/notebooks/instances/update index f5fac1c98..d7aaedfcd 100644 --- a/gcloud/beta/notebooks/instances/update +++ b/gcloud/beta/notebooks/instances/update @@ -78,7 +78,7 @@ REQUIRED FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3. + TPU_V2, TPU_V3, NVIDIA_L4. --labels=[KEY=VALUE,...] Labels to apply to this instance. These can be later modified by the diff --git a/gcloud/beta/projects/create b/gcloud/beta/projects/create index ab1a400ca..10b045e6f 100644 --- a/gcloud/beta/projects/create +++ b/gcloud/beta/projects/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta projects create [PROJECT_ID] [--no-enable-cloud-apis] [--folder=FOLDER_ID] [--labels=[KEY=VALUE,...]] [--name=NAME] [--organization=ORGANIZATION_ID] [--set-as-default] - [GCLOUD_WIDE_FLAG ...] + [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a new project with the given project ID. By default, @@ -64,6 +64,12 @@ FLAGS --set-as-default Set newly created project as [core.project] property. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + "=". + + Example: 123/environment=production,123/costCenter=marketing + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/resource-manager/folders/create b/gcloud/beta/resource-manager/folders/create index 2933251c6..9e6735fe8 100644 --- a/gcloud/beta/resource-manager/folders/create +++ b/gcloud/beta/resource-manager/folders/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta resource-manager folders create --display-name=DISPLAY_NAME [--async] [--folder=FOLDER_ID] [--organization=ORGANIZATION_ID] - [GCLOUD_WIDE_FLAG ...] + [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a new folder in the given parent folder or organization. @@ -37,6 +37,12 @@ OPTIONAL FLAGS --organization=ORGANIZATION_ID ID for the organization to use as a parent + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + "=". + + Example: 123/environment=production,123/costCenter=marketing + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 88f189739..d73f6b309 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -25,7 +25,8 @@ SYNOPSIS --update-config-maps=[KEY=VALUE,...]] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --[no-]default-url --description=DESCRIPTION + --[no-]default-url --[no-]deploy-health-check + --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity @@ -439,6 +440,14 @@ FLAGS if not specified. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index c3b477e10..35d666dd6 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -20,7 +20,7 @@ SYNOPSIS | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --[no-]default-url + --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check --execution-environment=EXECUTION_ENVIRONMENT --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity @@ -325,6 +325,14 @@ FLAGS if not specified. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + --execution-environment=EXECUTION_ENVIRONMENT Selects the execution environment where the application will run. EXECUTION_ENVIRONMENT must be one of: diff --git a/gcloud/beta/secrets/add-iam-policy-binding b/gcloud/beta/secrets/add-iam-policy-binding index b7a4824e5..ea4db1393 100644 --- a/gcloud/beta/secrets/add-iam-policy-binding +++ b/gcloud/beta/secrets/add-iam-policy-binding @@ -1,16 +1,15 @@ NAME gcloud beta secrets add-iam-policy-binding - add IAM policy binding to a - secret + secret resource SYNOPSIS - gcloud beta secrets add-iam-policy-binding SECRET --member=PRINCIPAL - --role=ROLE + gcloud beta secrets add-iam-policy-binding (SECRET : --location=LOCATION) + --member=PRINCIPAL --role=ROLE [--condition=[KEY=VALUE,...] | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Add an IAM policy binding to the IAM policy of a secret. One binding - consists of a member and a role. + (BETA) Add IAM policy binding to a secret resource. EXAMPLES To add an IAM policy binding for the role of @@ -25,24 +24,39 @@ EXAMPLES policy role and member types. POSITIONAL ARGUMENTS - Secret resource - Name of the secret for which to add the IAM policy - binding. This represents a Cloud resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. + Global or regional secret resource - create a secret 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 secret on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: ▸ provide the argument secret on the command line. + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. + REQUIRED FLAGS --member=PRINCIPAL The principal to add the binding for. Should be of the form @@ -110,10 +124,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the secretmanager/v1 API. The full documentation for this - API can be found at: https://cloud.google.com/secret-manager/ - NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/secrets/create b/gcloud/beta/secrets/create index 29acd6beb..6e453e2cc 100644 --- a/gcloud/beta/secrets/create +++ b/gcloud/beta/secrets/create @@ -2,9 +2,10 @@ NAME gcloud beta secrets create - create a new secret SYNOPSIS - gcloud beta secrets create SECRET [--data-file=PATH] - [--labels=[KEY=VALUE,...]] [--set-annotations=[KEY=VALUE,...]] - [--topics=[TOPICS,...]] [--expire-time=EXPIRE-TIME | --ttl=TTL] + gcloud beta secrets create (SECRET : --location=LOCATION) + [--data-file=PATH] [--labels=[KEY=VALUE,...]] + [--set-annotations=[KEY=VALUE,...]] [--topics=[TOPICS,...]] + [--expire-time=EXPIRE-TIME | --ttl=TTL] [--next-rotation-time=NEXT_ROTATION_TIME --rotation-period=ROTATION_PERIOD] [--replication-policy-file=REPLICATION-POLICY-FILE @@ -73,23 +74,38 @@ EXAMPLES --rotation-period="7200s" POSITIONAL ARGUMENTS - Secret resource - The secret to create. This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. + Global or regional secret resource - create a secret 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 SECRET on the command line with a fully + ◆ provide the argument secret on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: - ▸ provide the argument SECRET on the command line. + ▸ provide the argument secret on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. FLAGS --data-file=PATH diff --git a/gcloud/beta/secrets/delete b/gcloud/beta/secrets/delete index 8143734e0..b9e3fb7b6 100644 --- a/gcloud/beta/secrets/delete +++ b/gcloud/beta/secrets/delete @@ -2,7 +2,8 @@ NAME gcloud beta secrets delete - delete a secret SYNOPSIS - gcloud beta secrets delete SECRET [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets delete (SECRET : --location=LOCATION) [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a secret and destroy all secret versions. This action is @@ -19,23 +20,38 @@ EXAMPLES $ gcloud beta secrets delete my-secret --etag=\"123\" POSITIONAL ARGUMENTS - Secret resource - The secret to delete. This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. + Global or regional secret resource - to delete 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 SECRET on the command line with a fully + ◆ provide the argument secret on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: - ▸ provide the argument SECRET on the command line. + ▸ provide the argument secret on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. FLAGS --etag=ETAG diff --git a/gcloud/beta/secrets/describe b/gcloud/beta/secrets/describe index baf728e78..e90c36a32 100644 --- a/gcloud/beta/secrets/describe +++ b/gcloud/beta/secrets/describe @@ -2,7 +2,8 @@ NAME gcloud beta secrets describe - describe a secret's metadata SYNOPSIS - gcloud beta secrets describe SECRET [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets describe (SECRET : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe a secret's metadata. @@ -13,23 +14,38 @@ EXAMPLES $ gcloud beta secrets describe my-secret POSITIONAL ARGUMENTS - Secret resource - The secret to describe. This represents a Cloud - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + Global or regional secret resource - to describe 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 SECRET on the command line with a fully + ◆ provide the argument secret on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: - ▸ provide the argument SECRET on the command line. + ▸ provide the argument secret on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/secrets/get-iam-policy b/gcloud/beta/secrets/get-iam-policy index 0f70f3d35..772779302 100644 --- a/gcloud/beta/secrets/get-iam-policy +++ b/gcloud/beta/secrets/get-iam-policy @@ -1,43 +1,55 @@ NAME - gcloud beta secrets get-iam-policy - get the IAM policy for the secret + gcloud beta secrets get-iam-policy - get the IAM policy of a secret SYNOPSIS - gcloud beta secrets get-iam-policy SECRET [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets get-iam-policy (SECRET : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Displays the IAM policy associated with the secret. If formatted as - JSON, the output can be edited and used as a policy file for - set-iam-policy. The output includes an "etag" field identifying the version - emitted and allowing detection of concurrent policy updates. + (BETA) Gets the IAM policy for the given secret. - Run gcloud beta secrets set-iam-policy for additional details. + Returns an empty policy if the resource does not have a policy set. EXAMPLES To print the IAM policy for secret named 'my-secret', run: - $ gcloud beta secrets get-iam-policy my-secret + $ gcloud beta secrets get-iam-policy my-secret [--location=] POSITIONAL ARGUMENTS - Secret resource - Name of the secret from which to get IAM policy. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + Global or regional secret resource - create a secret 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 secret on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: ▸ provide the argument secret on the command line. + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. @@ -72,10 +84,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the secretmanager/v1 API. The full documentation for this - API can be found at: https://cloud.google.com/secret-manager/ - NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/secrets/help b/gcloud/beta/secrets/help index cdf2fd861..333dffd27 100644 --- a/gcloud/beta/secrets/help +++ b/gcloud/beta/secrets/help @@ -39,7 +39,7 @@ COMMANDS COMMAND is one of the following: add-iam-policy-binding - (BETA) Add IAM policy binding to a secret. + (BETA) Add IAM policy binding to a secret resource. create (BETA) Create a new secret. @@ -51,16 +51,16 @@ COMMANDS (BETA) Describe a secret's metadata. get-iam-policy - (BETA) Get the IAM policy for the secret. + (BETA) Get the IAM policy of a secret. list (BETA) List all secret names. remove-iam-policy-binding - (BETA) Remove IAM policy binding for a secret. + (BETA) Remove IAM policy binding of a secret resource. set-iam-policy - (BETA) Set the IAM policy binding for a secret. + (BETA) Set the IAM policy for a secret. update (BETA) Update a secret's metadata. diff --git a/gcloud/beta/secrets/remove-iam-policy-binding b/gcloud/beta/secrets/remove-iam-policy-binding index 85135f813..ae4910aa7 100644 --- a/gcloud/beta/secrets/remove-iam-policy-binding +++ b/gcloud/beta/secrets/remove-iam-policy-binding @@ -1,19 +1,15 @@ NAME gcloud beta secrets remove-iam-policy-binding - remove IAM policy binding - for a secret + of a secret resource SYNOPSIS - gcloud beta secrets remove-iam-policy-binding SECRET --member=PRINCIPAL - --role=ROLE + gcloud beta secrets remove-iam-policy-binding + (SECRET : --location=LOCATION) --member=PRINCIPAL --role=ROLE [--all | --condition=[KEY=VALUE,...] | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Removes a policy binding from the IAM policy of a secret. One - binding consists of a member and a role. - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. + (BETA) Remove IAM policy binding of a secret resource. EXAMPLES To remove an IAM policy binding for the role of 'roles/viewer' for the user @@ -23,24 +19,39 @@ EXAMPLES --member='user:test-user@gmail.com' --role='roles/viewer' POSITIONAL ARGUMENTS - Secret resource - Name of the secret from which to remove IAM policy - binding. This represents a Cloud resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. + Global or regional secret resource - create a secret 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 secret on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: ▸ provide the argument secret on the command line. + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. + REQUIRED FLAGS --member=PRINCIPAL The principal to remove the binding for. Should be of the form @@ -113,10 +124,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the secretmanager/v1 API. The full documentation for this - API can be found at: https://cloud.google.com/secret-manager/ - NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/secrets/set-iam-policy b/gcloud/beta/secrets/set-iam-policy index 2189f19ac..292d8ff7e 100644 --- a/gcloud/beta/secrets/set-iam-policy +++ b/gcloud/beta/secrets/set-iam-policy @@ -1,43 +1,54 @@ NAME - gcloud beta secrets set-iam-policy - set the IAM policy binding for a - secret + gcloud beta secrets set-iam-policy - set the IAM policy for a secret SYNOPSIS - gcloud beta secrets set-iam-policy SECRET POLICY_FILE - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets set-iam-policy (SECRET : --location=LOCATION) + POLICY_FILE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Sets the IAM policy for the given secret as defined in a JSON or - YAML file. + (BETA) Sets the IAM policy for the given secret. - See https://cloud.google.com/iam/docs/managing-policies for details of the - policy file format and contents. + Returns an empty policy if the resource does not have a policy set. EXAMPLES - The following command will read an IAM policy defined in a JSON file - 'policy.json' and set it for the secret 'my-secret': + To print the IAM policy for secret named 'my-secret', run: - $ gcloud beta secrets set-iam-policy my-secret policy.json + $ gcloud beta secrets set-iam-policy my-secret [--location=] POSITIONAL ARGUMENTS - Secret resource - Name of the secret for which to set the IAM policy. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + Global or regional secret resource - create a secret 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 secret on the command line with a fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: ▸ provide the argument secret on the command line. + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. + POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. @@ -53,10 +64,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the secretmanager/v1 API. The full documentation for this - API can be found at: https://cloud.google.com/secret-manager/ - NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/secrets/update b/gcloud/beta/secrets/update index b96029b75..ef0ac1dc1 100644 --- a/gcloud/beta/secrets/update +++ b/gcloud/beta/secrets/update @@ -2,7 +2,7 @@ NAME gcloud beta secrets update - update a secret's metadata SYNOPSIS - gcloud beta secrets update SECRET [--etag=ETAG] + gcloud beta secrets update (SECRET : --location=LOCATION) [--etag=ETAG] [--update-labels=[KEY=VALUE,...]] [--add-topics=[ADD-TOPICS,...] | --clear-topics | --remove-topics=[REMOVE-TOPICS,...]] @@ -64,23 +64,38 @@ EXAMPLES $ gcloud beta secrets update my-secret --remove-rotation-schedule POSITIONAL ARGUMENTS - Secret resource - The secret to update. This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. + Global or regional secret resource - to update 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 SECRET on the command line with a fully + ◆ provide the argument secret on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: - ▸ provide the argument SECRET on the command line. + ▸ provide the argument secret on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. FLAGS --etag=ETAG diff --git a/gcloud/beta/secrets/versions/access b/gcloud/beta/secrets/versions/access index 0ef4a748d..512d1b856 100644 --- a/gcloud/beta/secrets/versions/access +++ b/gcloud/beta/secrets/versions/access @@ -2,7 +2,8 @@ NAME gcloud beta secrets versions access - access a secret version's data SYNOPSIS - gcloud beta secrets versions access (VERSION : --secret=SECRET) + gcloud beta secrets versions access + (VERSION : --location=LOCATION --secret=SECRET) [--out-file=OUT-FILE-PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -28,34 +29,44 @@ EXAMPLES --format='get(payload.data)' | tr '_-' '/+' | base64 -d POSITIONAL ARGUMENTS - Version resource - Numeric secret version to access or a configured alias - (including 'latest' to use the latest version). 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. + Global or regional secret version resource - to access 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 VERSION on the command line with a fully + ◆ provide the argument version on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [version, regional version]. This must be specified. VERSION - ID of the version or fully qualified identifier for the version. + ID of the global or regional secret version or fully qualified + identifier for the global or regional secret version. To set the version attribute: - ▸ provide the argument VERSION on the command line. + ▸ provide the argument version on the command line. This positional argument must be specified if any of the other arguments in this group are specified. + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret version. + + To set the location attribute: + ▸ provide the argument version on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional version]. + --secret=SECRET - The secret of the version. + The secret of the global or regional secret version. To set the secret attribute: - ▸ provide the argument VERSION on the command line with a fully + ▸ provide the argument version on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/add b/gcloud/beta/secrets/versions/add index a0dcb4e40..ded0b3b55 100644 --- a/gcloud/beta/secrets/versions/add +++ b/gcloud/beta/secrets/versions/add @@ -3,8 +3,8 @@ NAME secret SYNOPSIS - gcloud beta secrets versions add SECRET --data-file=PATH - [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions add (SECRET : --location=LOCATION) + --data-file=PATH [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new version of an existing secret with the provided data. @@ -30,23 +30,38 @@ EXAMPLES $ gcloud beta secrets versions add my-secret --data-file=/tmp/secret POSITIONAL ARGUMENTS - Secret resource - The secret to create. This represents a Cloud resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. + Global or regional secret resource - to create 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 SECRET on the command line with a fully + ◆ provide the argument secret on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: - ▸ provide the argument SECRET on the command line. + ▸ provide the argument secret on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. REQUIRED FLAGS --data-file=PATH diff --git a/gcloud/beta/secrets/versions/destroy b/gcloud/beta/secrets/versions/destroy index 556582e1f..8bfaf3ca0 100644 --- a/gcloud/beta/secrets/versions/destroy +++ b/gcloud/beta/secrets/versions/destroy @@ -3,8 +3,9 @@ NAME and secret data SYNOPSIS - gcloud beta secrets versions destroy (VERSION : --secret=SECRET) - [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions destroy + (VERSION : --location=LOCATION --secret=SECRET) [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Destroy a secret version's metadata and secret data. This action is @@ -21,33 +22,44 @@ EXAMPLES --etag=\"123\" POSITIONAL ARGUMENTS - Version resource - Numeric secret version to destroy. The arguments in + Global or regional secret version resource - to destroy 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 VERSION on the command line with a fully + ◆ provide the argument version on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [version, regional version]. This must be specified. VERSION - ID of the version or fully qualified identifier for the version. + ID of the global or regional secret version or fully qualified + identifier for the global or regional secret version. To set the version attribute: - ▸ provide the argument VERSION on the command line. + ▸ provide the argument version on the command line. This positional argument must be specified if any of the other arguments in this group are specified. + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret version. + + To set the location attribute: + ▸ provide the argument version on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional version]. + --secret=SECRET - The secret of the version. + The secret of the global or regional secret version. To set the secret attribute: - ▸ provide the argument VERSION on the command line with a fully + ▸ provide the argument version on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/disable b/gcloud/beta/secrets/versions/disable index 18e93e372..bfd92a4e3 100644 --- a/gcloud/beta/secrets/versions/disable +++ b/gcloud/beta/secrets/versions/disable @@ -3,8 +3,9 @@ NAME secret SYNOPSIS - gcloud beta secrets versions disable (VERSION : --secret=SECRET) - [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions disable + (VERSION : --location=LOCATION --secret=SECRET) [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Disable the version of the provided secret. It can be re-enabled @@ -21,33 +22,44 @@ EXAMPLES --etag=\"123\" POSITIONAL ARGUMENTS - Version resource - Numeric secret version to disable. The arguments in + Global or regional secret version resource - to disable 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 VERSION on the command line with a fully + ◆ provide the argument version on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [version, regional version]. This must be specified. VERSION - ID of the version or fully qualified identifier for the version. + ID of the global or regional secret version or fully qualified + identifier for the global or regional secret version. To set the version attribute: - ▸ provide the argument VERSION on the command line. + ▸ provide the argument version on the command line. This positional argument must be specified if any of the other arguments in this group are specified. + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret version. + + To set the location attribute: + ▸ provide the argument version on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional version]. + --secret=SECRET - The secret of the version. + The secret of the global or regional secret version. To set the secret attribute: - ▸ provide the argument VERSION on the command line with a fully + ▸ provide the argument version on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/enable b/gcloud/beta/secrets/versions/enable index 7742f3b82..ccdd6e2b5 100644 --- a/gcloud/beta/secrets/versions/enable +++ b/gcloud/beta/secrets/versions/enable @@ -3,8 +3,9 @@ NAME secret SYNOPSIS - gcloud beta secrets versions enable (VERSION : --secret=SECRET) - [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions enable + (VERSION : --location=LOCATION --secret=SECRET) [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Enable the version of the provided secret. It can be disabled with @@ -21,33 +22,44 @@ EXAMPLES --etag=\"123\" POSITIONAL ARGUMENTS - Version resource - Numeric secret version to enable. 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. + Global or regional secret version resource - to enable 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 VERSION on the command line with a fully + ◆ provide the argument version on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [version, regional version]. This must be specified. VERSION - ID of the version or fully qualified identifier for the version. + ID of the global or regional secret version or fully qualified + identifier for the global or regional secret version. To set the version attribute: - ▸ provide the argument VERSION on the command line. + ▸ provide the argument version on the command line. This positional argument must be specified if any of the other arguments in this group are specified. + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret version. + + To set the location attribute: + ▸ provide the argument version on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional version]. + --secret=SECRET - The secret of the version. + The secret of the global or regional secret version. To set the secret attribute: - ▸ provide the argument VERSION on the command line with a fully + ▸ provide the argument version on the command line with a fully specified name; ▸ provide the argument --secret on the command line. diff --git a/gcloud/beta/secrets/versions/list b/gcloud/beta/secrets/versions/list index f5bb6b6eb..db716ea87 100644 --- a/gcloud/beta/secrets/versions/list +++ b/gcloud/beta/secrets/versions/list @@ -2,9 +2,10 @@ NAME gcloud beta secrets versions list - list all versions for a secret SYNOPSIS - gcloud beta secrets versions list SECRET [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE; default=100] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud beta secrets versions list (SECRET : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List all versions and their status (For example: @@ -16,23 +17,38 @@ EXAMPLES $ gcloud beta secrets versions list my-secret POSITIONAL ARGUMENTS - Secret resource - The secret from which to list versions. This represents - a Cloud resource. (NOTE) Some attributes are not given arguments in this - group but can be set in other ways. + Global or regional secret resource - from which to list versions 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 SECRET on the command line with a fully + ◆ provide the argument secret on the command line with a fully specified name; ◆ provide the argument --project on the command line; - ◆ set the property core/project. + ◆ set the property core/project. This resource can be one of the + following types: [secret, regional secret]. This must be specified. SECRET - ID of the secret or fully qualified identifier for the secret. + ID of the global or regional secret or fully qualified identifier for + the global or regional secret. To set the secret attribute: - ▸ provide the argument SECRET on the command line. + ▸ provide the argument secret on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + [EXPERIMENTAL] The location of the global or regional secret. + + To set the location attribute: + ▸ provide the argument secret on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. Must be + specified for resource of type [regional secret]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/sql/backups/list b/gcloud/beta/sql/backups/list index 6df79136a..3ef4c5a77 100644 --- a/gcloud/beta/sql/backups/list +++ b/gcloud/beta/sql/backups/list @@ -3,7 +3,7 @@ NAME project or a given instance SYNOPSIS - gcloud beta sql backups list --instance=INSTANCE, -i INSTANCE + gcloud beta sql backups list [--instance=INSTANCE, -i INSTANCE] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -12,7 +12,7 @@ DESCRIPTION instance and configuration in the reverse chronological order of the enqueued time. -REQUIRED FLAGS +FLAGS --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID or "-" for all instances. diff --git a/gcloud/beta/tasks/buffer b/gcloud/beta/tasks/buffer index 7235e5349..18b3363e3 100644 --- a/gcloud/beta/tasks/buffer +++ b/gcloud/beta/tasks/buffer @@ -33,8 +33,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud tasks buffer $ gcloud alpha tasks buffer diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index 587a304c9..5b642995b 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -14,6 +14,7 @@ SYNOPSIS [--disable-public-ip-addresses] [--disable-ssh-to-vm] [--disable-tcp-connections] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] + [--ephemeral-directory=[PROPERTY=VALUE,...]] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--network-tags=[NETWORK_TAGS,...]] @@ -161,6 +162,9 @@ FLAGS Default value is false. If set, instances will have nested virtualization enabled. + --ephemeral-directory=[PROPERTY=VALUE,...] + Ephemeral directory which won't persist across workstation sessions. + --idle-timeout=IDLE_TIMEOUT; default=7200 How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/bigtable/instances/tables/create b/gcloud/bigtable/instances/tables/create index 95ec5fcef..53936835d 100644 --- a/gcloud/bigtable/instances/tables/create +++ b/gcloud/bigtable/instances/tables/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud bigtable instances tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] + [--deletion-protection] [--enable-automated-backup] + [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Cloud Bigtable table. @@ -58,6 +59,14 @@ EXAMPLES --instance=my-instance --column-families="my-family" \ --no-deletion-protection + To create a table my-table with automated backup policy + (retention_period=72h, frequency=24h) enabled in instance my-instance with + a column family my-family, run: + + $ gcloud bigtable instances tables create my-table \ + --instance=my-instance --column-families="my-family" \ + --enable-automated-backup + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -106,6 +115,10 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=72h, frequency=24h) for the table. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/bigtable/instances/tables/update b/gcloud/bigtable/instances/tables/update index 9678a0568..100eb6965 100644 --- a/gcloud/bigtable/instances/tables/update +++ b/gcloud/bigtable/instances/tables/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud bigtable instances tables update (TABLE : --instance=INSTANCE) - [--async] [--deletion-protection] + [--async] [--deletion-protection] [--disable-automated-backup] + [--enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] @@ -34,6 +35,17 @@ EXAMPLES $ gcloud bigtable instances tables update my-table \ --instance=my-instance --clear-change-stream-retention-period + To enable default automated backup policy (retention_period=72h, + frequency=24h), run: + + $ gcloud bigtable instances tables update my-table \ + --instance=my-instance --enable-automated-backup + + To disable automated backup: run: + + $ gcloud bigtable instances tables update my-table \ + --instance=my-instance --disable-automated-backup + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -73,6 +85,13 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=72h, frequency=24h) for the table. + At most one of these can be specified: --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD diff --git a/gcloud/bigtable/tables/create b/gcloud/bigtable/tables/create index 61a9936c6..1cf2a801b 100644 --- a/gcloud/bigtable/tables/create +++ b/gcloud/bigtable/tables/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud bigtable tables create (TABLE : --instance=INSTANCE) --column-families=[COLUMN_FAMILIES,...] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD] - [--deletion-protection] [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] + [--deletion-protection] [--enable-automated-backup] + [--splits=[SPLITS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Cloud Bigtable table. @@ -53,6 +54,13 @@ EXAMPLES $ gcloud bigtable tables create my-table --instance=my-instance \ --column-families="my-family" --no-deletion-protection + To create a table my-table with automated backup policy + (retention_period=72h, frequency=24h) enabled in instance my-instance with + a column family my-family, run: + + $ gcloud bigtable tables create my-table --instance=my-instance \ + --column-families="my-family" --enable-automated-backup + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -101,6 +109,10 @@ OPTIONAL FLAGS --deletion-protection Once specified, the table is deletion protected. + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=72h, frequency=24h) for the table. + --splits=[SPLITS,...] Row keys where the table should initially be split. For example: car,key diff --git a/gcloud/bigtable/tables/update b/gcloud/bigtable/tables/update index bf88df098..7b386eb31 100644 --- a/gcloud/bigtable/tables/update +++ b/gcloud/bigtable/tables/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud bigtable tables update (TABLE : --instance=INSTANCE) [--async] - [--deletion-protection] + [--deletion-protection] [--disable-automated-backup] + [--enable-automated-backup] [--change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD | --clear-change-stream-retention-period] [GCLOUD_WIDE_FLAG ...] @@ -33,6 +34,17 @@ EXAMPLES $ gcloud bigtable tables update my-table --instance=my-instance \ --clear-change-stream-retention-period + To enable default automated backup policy (retention_period=72h, + frequency=24h), run: + + $ gcloud bigtable tables update my-table --instance=my-instance \ + --enable-automated-backup + + To disable automated backup: run: + + $ gcloud bigtable tables update my-table --instance=my-instance \ + --disable-automated-backup + POSITIONAL ARGUMENTS Table resource - Cloud Bigtable table to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -72,6 +84,13 @@ FLAGS --deletion-protection Once specified, the table is deletion protected. + --disable-automated-backup + Once set, disables automated backup policy for the table. + + --enable-automated-backup + Once set, enables the default automated backup policy + (retention_period=72h, frequency=24h) for the table. + At most one of these can be specified: --change-stream-retention-period=CHANGE_STREAM_RETENTION_PERIOD diff --git a/gcloud/builds/connections/create/bitbucket-cloud b/gcloud/builds/connections/create/bitbucket-cloud new file mode 100644 index 000000000..37eb9246a --- /dev/null +++ b/gcloud/builds/connections/create/bitbucket-cloud @@ -0,0 +1,108 @@ +NAME + gcloud builds connections create bitbucket-cloud - create a Cloud Build + Connection for Bitbucket Cloud + +SYNOPSIS + gcloud builds connections create bitbucket-cloud + (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + --workspace=WORKSPACE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Build Connection for Bitbucket Cloud. + + A Bitbucket Cloud Connection can be created by using a + repository/project/workspace access token with + repository_read,repository_admin, pullrequest_read, webhook scope + permission and a repository/project/workspace access token with + repository_read scope permission. + +EXAMPLES + To create a Bitbucket Cloud connection, provide all the required + parameters: + + $ gcloud builds connections create bitbucket-cloud \ + my-bitbucket-conn --project=myproj --region=us-central1 \ + --workspace=my-workspace \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read,repository_admin, + pullrequest_read, webhook repository/project/workspace access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read repository/project/workspace + access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Cloud. + + --workspace=WORKSPACE + Workspace of the Bitbucket Cloud instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections create bitbucket-cloud + + $ gcloud beta builds connections create bitbucket-cloud + diff --git a/gcloud/builds/connections/create/bitbucket-data-center b/gcloud/builds/connections/create/bitbucket-data-center new file mode 100644 index 000000000..5d104aeab --- /dev/null +++ b/gcloud/builds/connections/create/bitbucket-data-center @@ -0,0 +1,139 @@ +NAME + gcloud builds connections create bitbucket-data-center - create a Cloud + Build Connection for Bitbucket Data Center + +SYNOPSIS + gcloud builds connections create bitbucket-data-center + (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] + [--host-uri=HOST_URI] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE + : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Build Connection for Bitbucket Data Center. + + A Bitbucket Data Center Connection can be created by using a personal + access token with REPO_ADMIN scope permission. A REPO_READ scoped personal + access token will also be required. + + If the Bitbucket Data Center can only be accessed within a VPC, a Service + Directory service resource can be provided for connecting to it. + +EXAMPLES + To create a Bitbucket Data Center connection, provide all the required + parameters: + + $ gcloud builds connections create bitbucket-data-center \ + my-bitbucket-conn --project=myproj --region=us-central1 \ + --host-uri=https://bitbucket-server.net \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + + To create a Bitbucket Data Center connection for a private Bitbucket Data + Center server. Provide the service-directory-service and ssl-ca-file as + well: + + $ gcloud builds connections create bitbucket-data-center \ + my-private-bitbucket-conn \ + --host-uri=https://my.private-bitbucket-server.net \ + --project=myproj --region=us-central1 \ + --service-directory-service=projects/myproj/namespaces/x/\ + services/mysds --ssl-ca-file=mycertificate.crt \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_ADMIN personal access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_READ personal access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Data Center. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --host-uri=HOST_URI + URI of the Bitbucket Data Center instance. + + Group of arguments for configuring access through Service Directory. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the Bitbucket + Data Center. Necessary only if the server has no public access from + the internet. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections create bitbucket-data-center + + $ gcloud beta builds connections create bitbucket-data-center + diff --git a/gcloud/builds/connections/create/help b/gcloud/builds/connections/create/help index d9ef19a9e..a4fc637eb 100644 --- a/gcloud/builds/connections/create/help +++ b/gcloud/builds/connections/create/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + Create a Cloud Build Connection for Bitbucket Cloud. + + bitbucket-data-center + Create a Cloud Build Connection for Bitbucket Data Center. + github Create a Cloud Build Connection of type GitHub. diff --git a/gcloud/builds/connections/update/bitbucket-cloud b/gcloud/builds/connections/update/bitbucket-cloud new file mode 100644 index 000000000..9c888a26e --- /dev/null +++ b/gcloud/builds/connections/update/bitbucket-cloud @@ -0,0 +1,103 @@ +NAME + gcloud builds connections update bitbucket-cloud - update a Cloud Build + Connection of type Bitbucket Cloud + +SYNOPSIS + gcloud builds connections update bitbucket-cloud + (CONNECTION : --region=REGION) [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] + [--workspace=WORKSPACE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud Build Connection of type Bitbucket Cloud. + +EXAMPLES + To update the workspace, provide the connection name and the workspace + name: + + $ gcloud builds connections update bitbucket-cloud my-bbc-conn \ + --region=us-west1 --workspace=my-workspace + + To update the authorization token, provide the connection name and the new + authorization token secret version. + + $ gcloud builds connections update bitbucket-cloud my-bbc-conn \ + --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read,repository_admin, + pullrequest_read, webhook access token. It can be a repository, project + or workspace access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the repository_read access token. It can be a + repository, project or workspace access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by Bitbucket Cloud. + + --workspace=WORKSPACE + Workspace of the Bitbucket Cloud instance. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections update bitbucket-cloud + + $ gcloud beta builds connections update bitbucket-cloud + diff --git a/gcloud/builds/connections/update/bitbucket-data-center b/gcloud/builds/connections/update/bitbucket-data-center new file mode 100644 index 000000000..4ec0b3c69 --- /dev/null +++ b/gcloud/builds/connections/update/bitbucket-data-center @@ -0,0 +1,104 @@ +NAME + gcloud builds connections update bitbucket-data-center - update a Cloud + Build Connection of type Bitbucket Data Center + +SYNOPSIS + gcloud builds connections update bitbucket-data-center + (CONNECTION : --region=REGION) [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--host-uri=HOST_URI] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud Build Connection of type Bitbucket Data Center. + +EXAMPLES + To update the ssl_ca, provide the connection name and the ssl_ca file: + + $ gcloud builds connections update bitbucket-data-center \ + my-gle-conn --region=us-west1 --ssl-ca-file=mycertificate.crt + + To update the authorization token, provide the connection name and the new + authorization token secret version name. + + $ gcloud builds connections update bitbucket-data-center \ + my-gle-conn --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + admin-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. 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 connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_ADMIN personal access token. + + --host-uri=HOST_URI + URI of the Bitbucket Data Center instance. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the REPO_READ personal access token. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the Bitbucket + Data Center. Necessary only if the server has no public access from the + internet. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections update bitbucket-data-center + + $ gcloud beta builds connections update bitbucket-data-center + diff --git a/gcloud/builds/connections/update/help b/gcloud/builds/connections/update/help index 07871e5ba..cb4141591 100644 --- a/gcloud/builds/connections/update/help +++ b/gcloud/builds/connections/update/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + Update a Cloud Build Connection of type Bitbucket Cloud. + + bitbucket-data-center + Update a Cloud Build Connection of type Bitbucket Data Center. + github Update a Cloud Build Connection of type GitHub. diff --git a/gcloud/builds/triggers/create/bitbucket-cloud b/gcloud/builds/triggers/create/bitbucket-cloud new file mode 100644 index 000000000..8fb276812 --- /dev/null +++ b/gcloud/builds/triggers/create/bitbucket-cloud @@ -0,0 +1,222 @@ +NAME + gcloud builds triggers create bitbucket-cloud - create a build trigger for + a 2nd-gen Bitbucket Cloud repository + +SYNOPSIS + gcloud builds triggers create bitbucket-cloud + (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED"]) (--build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a build trigger for a 2nd-gen Bitbucket Cloud repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud builds triggers create bitbucket-cloud \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" --region=us-central1 + + To create a pull request trigger with a 2nd-gen repository for main: + + $ gcloud builds triggers create bitbucket-cloud \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ + --pull-request-pattern="^main$" --region=us-central1 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. Note: Region must be specified in 2nd gen repo; global is + not supported. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. For + example: + + $ gcloud builds triggers create bitbucket-cloud ... \ + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + +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 builds triggers create bitbucket-cloud + + $ gcloud beta builds triggers create bitbucket-cloud + diff --git a/gcloud/builds/triggers/create/bitbucket-data-center b/gcloud/builds/triggers/create/bitbucket-data-center new file mode 100644 index 000000000..db76e3dea --- /dev/null +++ b/gcloud/builds/triggers/create/bitbucket-data-center @@ -0,0 +1,222 @@ +NAME + gcloud builds triggers create bitbucket-data-center - create a build + trigger for a 2nd-gen Bitbucket Data Center repository + +SYNOPSIS + gcloud builds triggers create bitbucket-data-center + (--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default="COMMENTS_ENABLED"]) (--build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a build trigger for a 2nd-gen Bitbucket Data Center repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud builds triggers create bitbucket-data-center \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" --region=us-central1 + + To create a pull request trigger with a 2nd-gen repository for main: + + $ gcloud builds triggers create bitbucket-data-center \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/us-central1/connections/my\ + conn/repositories/myrepo" --build-config="cloudbuild.yaml" \ + --pull-request-pattern="^main$" --region=us-central1 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. Note: Region must be specified in 2nd gen repo; global is + not supported. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. For + example: + + $ gcloud builds triggers create bitbucket-data-center ... \ + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED" + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + +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 builds triggers create bitbucket-data-center + + $ gcloud beta builds triggers create bitbucket-data-center + diff --git a/gcloud/builds/triggers/create/help b/gcloud/builds/triggers/create/help index 892daf30b..889bfb238 100644 --- a/gcloud/builds/triggers/create/help +++ b/gcloud/builds/triggers/create/help @@ -16,6 +16,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + Create a build trigger for a 2nd-gen Bitbucket Cloud repository. + + bitbucket-data-center + Create a build trigger for a 2nd-gen Bitbucket Data Center repository. + bitbucketserver Create a build trigger for a Bitbucket Server repository. diff --git a/gcloud/builds/triggers/update/bitbucket-cloud b/gcloud/builds/triggers/update/bitbucket-cloud new file mode 100644 index 000000000..558a3609d --- /dev/null +++ b/gcloud/builds/triggers/update/bitbucket-cloud @@ -0,0 +1,251 @@ +NAME + gcloud builds triggers update bitbucket-cloud - updates Bitbucket Cloud + trigger used by Cloud Build + +SYNOPSIS + gcloud builds triggers update bitbucket-cloud (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates Bitbucket Cloud trigger used by Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud builds triggers update bitbucket-cloud my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud builds triggers update bitbucket-cloud my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud builds triggers update bitbucket-cloud my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud builds triggers update bitbucket-cloud my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucket-cloud + + $ gcloud beta builds triggers update bitbucket-cloud + diff --git a/gcloud/builds/triggers/update/bitbucket-data-center b/gcloud/builds/triggers/update/bitbucket-data-center new file mode 100644 index 000000000..401c53961 --- /dev/null +++ b/gcloud/builds/triggers/update/bitbucket-data-center @@ -0,0 +1,252 @@ +NAME + gcloud builds triggers update bitbucket-data-center - updates Bitbucket + Data Center trigger used by Cloud Build + +SYNOPSIS + gcloud builds triggers update bitbucket-data-center + (TRIGGER : --region=REGION) + (--trigger-config=PATH | --description=DESCRIPTION + --ignored-files=[GLOB,...] --included-files=[GLOB,...] + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --branch-pattern=REGEX + | --tag-pattern=REGEX | --comment-control=COMMENT_CONTROL + --pull-request-pattern=REGEX --build-config=PATH + | --inline-config=PATH + | [--dockerfile=DOCKERFILE --dockerfile-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR] --clear-substitutions + | --remove-substitutions=[KEY,...] + | --update-substitutions=[KEY=VALUE,...]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates Bitbucket Data Center trigger used by Cloud Build. + +EXAMPLES + To update the branch pattern of the trigger: + + $ gcloud builds triggers update bitbucket-data-center my-trigger \ + --branch-pattern=".*" + + To update the build config of the trigger: + + $ gcloud builds triggers update bitbucket-data-center my-trigger \ + --build-config="cloudbuild.yaml" + + To update the substitutions of the trigger: + + $ gcloud builds triggers update bitbucket-data-center my-trigger \ + --update-substitutions=_REPO_NAME=my-repo,_BRANCH_NAME=master + + To update the 2nd-gen repository resource of the trigger: + + $ gcloud builds triggers update bitbucket-data-center my-trigger \ + --repository=projects/my-project/locations/us-west1/\ + connections/my-conn/repositories/my-repo + +POSITIONAL ARGUMENTS + Trigger resource - Build Trigger. 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 TRIGGER 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. + + TRIGGER + ID of the trigger or fully qualified identifier for the trigger. + + To set the trigger attribute: + ▸ provide the argument TRIGGER on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud location for the trigger. + + To set the region attribute: + ▸ provide the argument TRIGGER on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + At most one of these can be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --comment-control=COMMENT_CONTROL + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. COMMENT_CONTROL + must be one of: + + COMMENTS_DISABLED + Do not require comments on Pull Requests before builds are + triggered. + COMMENTS_ENABLED + Enforce that repository owners or collaborators must + comment on Pull Requests before builds are triggered. + COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY + Enforce that repository owners or collaborators must + comment on external contributors' Pull Requests before + builds are triggered. + + --pull-request-pattern=REGEX + A regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regular expression search for the + base branch (the branch you are trying to merge into) for pull + request updates. For example, --pull-request-pattern=foo will + match "foo", "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + At most one of these can be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-dir=DOCKERFILE_DIR + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + At most one of these can be specified: + + --clear-substitutions + Clear existing substitutions. + + --remove-substitutions=[KEY,...] + Remove existing substitutions if present. + + --update-substitutions=[KEY=VALUE,...] + Update or add to existing substitutions. Substitutions are + parameters to be substituted or add in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers update ... + --update-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will add the provided substitutions to the existing + substitutions and results in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/build-config-file-schema#substitutions + +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 builds triggers update bitbucket-data-center + + $ gcloud beta builds triggers update bitbucket-data-center + diff --git a/gcloud/builds/triggers/update/help b/gcloud/builds/triggers/update/help index a5529e459..30a4b34d7 100644 --- a/gcloud/builds/triggers/update/help +++ b/gcloud/builds/triggers/update/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + bitbucket-cloud + Updates Bitbucket Cloud trigger used by Cloud Build. + + bitbucket-data-center + Updates Bitbucket Data Center trigger used by Cloud Build. + bitbucketserver Updates Bitbucket Server trigger used by Cloud Build. diff --git a/gcloud/compute/project-info/update b/gcloud/compute/project-info/update index 799764b80..98f1e32f5 100644 --- a/gcloud/compute/project-info/update +++ b/gcloud/compute/project-info/update @@ -3,7 +3,7 @@ NAME resource SYNOPSIS - gcloud compute project-info update + gcloud compute project-info update [--cloud-armor-tier=CLOUD_ARMOR_TIER] [--default-network-tier=DEFAULT_NETWORK_TIER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -11,6 +11,10 @@ DESCRIPTION project resource. FLAGS + --cloud-armor-tier=CLOUD_ARMOR_TIER + Cloud armor tier to assign to the project. CLOUD_ARMOR_TIER must be one + of: CA_STANDARD, CA_ENTERPRISE_PAYGO. + --default-network-tier=DEFAULT_NETWORK_TIER The default network tier to assign to the project. DEFAULT_NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. diff --git a/gcloud/compute/tpus/queued-resources/create b/gcloud/compute/tpus/queued-resources/create index 39550000f..9836934e1 100644 --- a/gcloud/compute/tpus/queued-resources/create +++ b/gcloud/compute/tpus/queued-resources/create @@ -13,7 +13,7 @@ SYNOPSIS [--network=NETWORK; default="default"] [--range=RANGE] [--reservation-host-folder=RESERVATION_HOST_FOLDER] [--reservation-host-organization=RESERVATION_HOST_ORGANIZATION] - [--reservation-host-project=RESERVATION_HOST_PROJECT] + [--reservation-host-project=RESERVATION_HOST_PROJECT] [--reserved] [--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot] [--spot] [--subnetwork=SUBNETWORK] [--tags=[TAGS,...]] [--valid-after-duration=VALID_AFTER_DURATION] @@ -207,6 +207,13 @@ OPTIONAL FLAGS The project hosting the reservation that the TPU should use. Only one reservation host entity may be specified. + --reserved + Specifies the request should be scheduled on reserved capacity. + + If --reservation-host-project, --reservation-host-folder, or + --reservation-host-organization are present then this flag has no + effect. + --scopes=[SCOPES,...] List of comma-separated scopes to be made available for the service account. diff --git a/gcloud/data-catalog/entries/create b/gcloud/data-catalog/entries/create index e8884c2d6..1903e2f22 100644 --- a/gcloud/data-catalog/entries/create +++ b/gcloud/data-catalog/entries/create @@ -100,7 +100,8 @@ REQUIRED FLAGS --type=TYPE Type of the entry. TYPE must be one of: cluster, dashboard, database, database-schema, data-source-connection, data-stream, - entry-type-unspecified, explore, fileset, lake, look, model, + entry-type-unspecified, explore, feature-group, + feature-online-store, feature-view, fileset, lake, look, model, routine, service, table, zone. This flag argument must be specified if any of the other arguments diff --git a/gcloud/database-migration/conversion-workspaces/apply b/gcloud/database-migration/conversion-workspaces/apply index f65e4e769..76e4dc925 100644 --- a/gcloud/database-migration/conversion-workspaces/apply +++ b/gcloud/database-migration/conversion-workspaces/apply @@ -17,9 +17,8 @@ EXAMPLES $ gcloud database-migration conversion-workspaces apply \ my-conversion-workspace --region=us-central1 \ - --destination-connection-profile=projects/$$PROJECT_ID$$/\ - locations/us-central1/connectionProfiles/\ - destination-connection-profile-name + --destination-connection-profile=projects/1234/locations/\ + us-central1/connectionProfiles/destination-connection-profile-name POSITIONAL ARGUMENTS Conversion workspace resource - The conversion workspace to apply. The diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 06f324a1a..f7b18350a 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -55,6 +55,18 @@ EXAMPLES --region=us-central1 --type=CONTINUOUS --source=cp1 \ --destination=cp2 --conversion-workspace=cw + To create a continuous SQL Server to SQL Server homogeneous migration job: $ gcloud database-migration migration-jobs create my-migration-job \ + --region=us-central1 --type=CONTINUOUS --source=cp1 \ + --destination=cp2 --sqlserver-backup-file-pattern=pattern \ + --sqlserver-databases=db1,db2,db3 + + To create a continuous SQL Server to SQL Server homogeneous migration job + with encrypted databases: $ gcloud database-migration migration-jobs create my-migration-job \ + --region=us-central1 --type=CONTINUOUS --source=cp1 \ + --destination=cp2 --sqlserver-backup-file-pattern=pattern \ + --sqlserver-databases=db1,db2,db3 \ + --sqlserver-encrypted-databases=PATH/TO/ENCRYPTION/SETTINGS + POSITIONAL ARGUMENTS Migration job resource - The migration job to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) diff --git a/gcloud/datastream/streams/create b/gcloud/datastream/streams/create index d9b6b982f..6cd76d03c 100644 --- a/gcloud/datastream/streams/create +++ b/gcloud/datastream/streams/create @@ -97,11 +97,14 @@ REQUIRED FLAGS Exactly one of these must be specified: --backfill-none - Do not automatically backfill any objects. + Do not automatically backfill any objects. This flag is equivalent to + selecting the Manual backfill type in the Google Cloud console. --backfill-all Automatically backfill objects included in the stream source - configuration. Specific objects can be excluded. + configuration. Specific objects can be excluded. This flag is + equivalent to selecting the Automatic backfill type in the Google + Cloud console. At most one of these can be specified: diff --git a/gcloud/datastream/streams/update b/gcloud/datastream/streams/update index 03cb23a22..80a55c126 100644 --- a/gcloud/datastream/streams/update +++ b/gcloud/datastream/streams/update @@ -99,11 +99,14 @@ FLAGS At most one of these can be specified: --backfill-none - Do not automatically backfill any objects. + Do not automatically backfill any objects. This flag is equivalent to + selecting the Manual backfill type in the Google Cloud console. --backfill-all Automatically backfill objects included in the stream source - configuration. Specific objects can be excluded. + configuration. Specific objects can be excluded. This flag is + equivalent to selecting the Automatic backfill type in the Google + Cloud console. At most one of these can be specified: diff --git a/gcloud/edge-cloud/container/clusters/node-pools/create b/gcloud/edge-cloud/container/clusters/node-pools/create index f6fa371d1..b91ed64bb 100644 --- a/gcloud/edge-cloud/container/clusters/node-pools/create +++ b/gcloud/edge-cloud/container/clusters/node-pools/create @@ -8,7 +8,7 @@ SYNOPSIS --node-count=NODE_COUNT --node-location=NODE_LOCATION [--async] [--labels=[KEY=VALUE,...]] [--local-disk-kms-key=LOCAL_DISK_KMS_KEY] [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [GCLOUD_WIDE_FLAG ...] + [--node-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create an Edge Container node pool. @@ -111,6 +111,10 @@ OPTIONAL FLAGS pool. The filtering language accepts strings like "name=", and is documented in more detail at https://google.aip.dev/160. + --node-labels=[KEY=VALUE,...] + Comma-delimited list of key-value pairs that comprise labels for the + individual nodes in the node pool. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/edge-cloud/container/clusters/node-pools/update b/gcloud/edge-cloud/container/clusters/node-pools/update index fc9374587..15d2243de 100644 --- a/gcloud/edge-cloud/container/clusters/node-pools/update +++ b/gcloud/edge-cloud/container/clusters/node-pools/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud edge-cloud container clusters node-pools update (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] [--lro-timeout=LRO_TIMEOUT] [--machine-filter=MACHINE_FILTER] - [--node-count=NODE_COUNT] [--update-labels=[KEY=VALUE,...]] + [--node-count=NODE_COUNT] [--node-labels=[KEY=VALUE,...]] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +76,10 @@ FLAGS --node-count=NODE_COUNT Default nodeCount used by this node pool. + --node-labels=[KEY=VALUE,...] + Comma-delimited list of key-value pairs that comprise labels for the + individual nodes in the node pool. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/iam/roles/create b/gcloud/iam/roles/create index 840b1fcbb..5b2043e38 100644 --- a/gcloud/iam/roles/create +++ b/gcloud/iam/roles/create @@ -28,17 +28,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to create. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to create. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to create. + Organization of the role you want to create. --project=PROJECT_ID - The project of the role you want to create. + Project of the role you want to create. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/iam/roles/delete b/gcloud/iam/roles/delete index 9da234712..541813047 100644 --- a/gcloud/iam/roles/delete +++ b/gcloud/iam/roles/delete @@ -25,17 +25,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to delete. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to delete. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to delete. + Organization of the role you want to delete. --project=PROJECT_ID - The project of the role you want to delete. + Project of the role you want to delete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/iam/roles/describe b/gcloud/iam/roles/describe index 0c5fa7f79..a2ae73784 100644 --- a/gcloud/iam/roles/describe +++ b/gcloud/iam/roles/describe @@ -32,18 +32,18 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the role to describe. Curated roles example: roles/viewer. - Custom roles example: CustomRole. For custom roles, you must also - specify the --organization or --project flag. + ID of the role to describe. Curated roles example: roles/viewer. Custom + roles example: CustomRole. For custom roles, you must also specify the + --organization or --project flag. FLAGS At most one of these can be specified: --organization=ORGANIZATION - The organization of the role you want to describe. + Organization of the role you want to describe. --project=PROJECT_ID - The project of the role you want to describe. + Project of the role you want to describe. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/iam/roles/list b/gcloud/iam/roles/list index 9cc3c4c5a..d387de860 100644 --- a/gcloud/iam/roles/list +++ b/gcloud/iam/roles/list @@ -34,10 +34,10 @@ FLAGS At most one of these can be specified: --organization=ORGANIZATION - The organization of the role you want to list. + Organization of the role you want to list. --project=PROJECT_ID - The project of the role you want to list. + Project of the role you want to list. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/iam/roles/undelete b/gcloud/iam/roles/undelete index f8a2ddd3f..15adc34fc 100644 --- a/gcloud/iam/roles/undelete +++ b/gcloud/iam/roles/undelete @@ -27,17 +27,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to undelete. For example: CustomRole. You - must also specify the --organization or --project flag. + ID of the custom role to undelete. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to undelete. + Organization of the role you want to undelete. --project=PROJECT_ID - The project of the role you want to undelete. + Project of the role you want to undelete. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/iam/roles/update b/gcloud/iam/roles/update index 437191c2d..ede080a5e 100644 --- a/gcloud/iam/roles/update +++ b/gcloud/iam/roles/update @@ -25,17 +25,17 @@ EXAMPLES POSITIONAL ARGUMENTS ROLE_ID - The id of the custom role to update. For example: CustomRole. You must - also specify the --organization or --project flag. + ID of the custom role to update. You must also specify the + --organization or --project flag. REQUIRED FLAGS Exactly one of these must be specified: --organization=ORGANIZATION - The organization of the role you want to update. + Organization of the role you want to update. --project=PROJECT_ID - The project of the role you want to update. + Project of the role you want to update. The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be diff --git a/gcloud/iam/workforce-pools/create-cred-config b/gcloud/iam/workforce-pools/create-cred-config index 2467dd32f..a1d191842 100644 --- a/gcloud/iam/workforce-pools/create-cred-config +++ b/gcloud/iam/workforce-pools/create-cred-config @@ -85,13 +85,13 @@ REQUIRED FLAGS OPTIONAL FLAGS --credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME - The subject token field name (key) in a JSON credential source. + Subject token field name (key) in a JSON credential source. --credential-source-headers=[key=value,...] Headers to use when querying the credential-source-url. --credential-source-type=CREDENTIAL_SOURCE_TYPE - The format of the credential source (JSON or text). + Format of the credential source (JSON or text). --subject-token-type=SUBJECT_TOKEN_TYPE The type of token being used for authorization. This defaults to @@ -100,29 +100,29 @@ OPTIONAL FLAGS Arguments for an executable type credential source. --executable-interactive-timeout-millis=EXECUTABLE_INTERACTIVE_TIMEOUT_MILLIS - The timeout duration, in milliseconds, to wait for the executable to + Timeout duration, in milliseconds, to wait for the executable to finish when the command is running in interactive mode. --executable-output-file=EXECUTABLE_OUTPUT_FILE - The absolute path to the file storing the executable response. + Absolute path to the file storing the executable response. --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS - The timeout duration in milliseconds for waiting for the executable - to finish. + Timeout duration, in milliseconds, to wait for the executable to + finish. Service account impersonation options. --service-account=SERVICE_ACCOUNT - The email of the service account to impersonate. + Email of the service account to impersonate. This flag argument must be specified if any of the other arguments in this group are specified. --service-account-token-lifetime-seconds=SERVICE_ACCOUNT_TOKEN_LIFETIME_SECONDS - The desired lifetime duration of the service account access token in - seconds. This defaults to one hour when not provided. If a lifetime - greater than one hour is required, the service account must be added - as an allowed value in an Organization Policy that enforces the + Lifetime duration of the service account access token in seconds. + Defaults to one hour if not specified. If a lifetime greater than one + hour is required, the service account must be added as an allowed + value in an Organization Policy that enforces the constraints/iam.allowServiceAccountCredentialLifetimeExtension constraint. diff --git a/gcloud/iam/workload-identity-pools/create-cred-config b/gcloud/iam/workload-identity-pools/create-cred-config index 4f21ee779..f85201b36 100644 --- a/gcloud/iam/workload-identity-pools/create-cred-config +++ b/gcloud/iam/workload-identity-pools/create-cred-config @@ -106,13 +106,13 @@ OPTIONAL FLAGS The custom Application ID URI for the Azure access token. --credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME - The subject token field name (key) in a JSON credential source. + Subject token field name (key) in a JSON credential source. --credential-source-headers=[key=value,...] Headers to use when querying the credential-source-url. --credential-source-type=CREDENTIAL_SOURCE_TYPE - The format of the credential source (JSON or text). + Format of the credential source (JSON or text). --enable-imdsv2 Adds the AWS IMDSv2 session token Url to the credential source to @@ -125,25 +125,25 @@ OPTIONAL FLAGS Arguments for an executable type credential source. --executable-output-file=EXECUTABLE_OUTPUT_FILE - The absolute path to the file storing the executable response. + Absolute path to the file storing the executable response. --executable-timeout-millis=EXECUTABLE_TIMEOUT_MILLIS - The timeout duration in milliseconds for waiting for the executable - to finish. + Timeout duration, in milliseconds, to wait for the executable to + finish. Service account impersonation options. --service-account=SERVICE_ACCOUNT - The email of the service account to impersonate. + Email of the service account to impersonate. This flag argument must be specified if any of the other arguments in this group are specified. --service-account-token-lifetime-seconds=SERVICE_ACCOUNT_TOKEN_LIFETIME_SECONDS - The desired lifetime duration of the service account access token in - seconds. This defaults to one hour when not provided. If a lifetime - greater than one hour is required, the service account must be added - as an allowed value in an Organization Policy that enforces the + Lifetime duration of the service account access token in seconds. + Defaults to one hour if not specified. If a lifetime greater than one + hour is required, the service account must be added as an allowed + value in an Organization Policy that enforces the constraints/iam.allowServiceAccountCredentialLifetimeExtension constraint. diff --git a/gcloud/infra-manager/deployments/apply b/gcloud/infra-manager/deployments/apply index 1ade37e9c..926f79dcd 100644 --- a/gcloud/infra-manager/deployments/apply +++ b/gcloud/infra-manager/deployments/apply @@ -5,7 +5,10 @@ SYNOPSIS gcloud infra-manager deployments apply (DEPLOYMENT : --location=LOCATION) [--artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET] [--async] [--import-existing-resources] [--labels=[KEY=VALUE,...]] - [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] + [--quota-validation=QUOTA_VALIDATION] + [--service-account=SERVICE_ACCOUNT] + [--tf-version-constraint=TF_VERSION_CONSTRAINT] + [--worker-pool=WORKER_POOL] [--gcs-source=GCS_SOURCE | --git-source-directory=GIT_SOURCE_DIRECTORY --git-source-ref=GIT_SOURCE_REF --git-source-repo=GIT_SOURCE_REPO | --ignore-file=IGNORE_FILE @@ -115,11 +118,19 @@ FLAGS First, fetch the current labels using the `describe` command, then follow the preceding example for updating labels. + --quota-validation=QUOTA_VALIDATION + Input to control quota checks for resources in terraform configuration + files. There are limited resources on which quota validation applies. + Supported values are QUOTA_VALIDATION_UNSPECIFIED, ENABLED, ENFORCED + --service-account=SERVICE_ACCOUNT User-specified Service Account (SA) to be used as credential to manage resources. Format: projects/{projectID}/serviceAccounts/{serviceAccount} + --tf-version-constraint=TF_VERSION_CONSTRAINT + User-specified Terraform version constraint, for example "=1.3.10". + --worker-pool=WORKER_POOL User-specified Worker Pool resource in which the Cloud Build job will execute. Format: diff --git a/gcloud/infra-manager/deployments/delete b/gcloud/infra-manager/deployments/delete index 5b275f145..3c53662ff 100644 --- a/gcloud/infra-manager/deployments/delete +++ b/gcloud/infra-manager/deployments/delete @@ -44,7 +44,8 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument deployment on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. FLAGS --async diff --git a/gcloud/infra-manager/deployments/describe b/gcloud/infra-manager/deployments/describe index e34d34ec2..d3889d540 100644 --- a/gcloud/infra-manager/deployments/describe +++ b/gcloud/infra-manager/deployments/describe @@ -45,7 +45,8 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument deployment on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/infra-manager/deployments/list b/gcloud/infra-manager/deployments/list index ffa3e283b..c9c5d30c2 100644 --- a/gcloud/infra-manager/deployments/list +++ b/gcloud/infra-manager/deployments/list @@ -2,7 +2,7 @@ NAME gcloud infra-manager deployments list - list deployments SYNOPSIS - gcloud infra-manager deployments list --location=LOCATION + gcloud infra-manager deployments list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -14,7 +14,7 @@ EXAMPLES $ gcloud infra-manager deployments list --location=us-central1 -REQUIRED FLAGS +FLAGS Location resource - Location to list deployments This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -22,16 +22,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; + ◆ set the property infra-manager/location with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. - This must be specified. - --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/infra-manager/help b/gcloud/infra-manager/help index 2a1e0ea28..d72b0cfe9 100644 --- a/gcloud/infra-manager/help +++ b/gcloud/infra-manager/help @@ -26,3 +26,6 @@ GROUPS revisions Manage Revision resources. + + terraform-versions + Manage Terraform version resources. diff --git a/gcloud/infra-manager/previews/delete b/gcloud/infra-manager/previews/delete index a622daaa0..3044a7be7 100644 --- a/gcloud/infra-manager/previews/delete +++ b/gcloud/infra-manager/previews/delete @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument preview on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. FLAGS --async diff --git a/gcloud/infra-manager/previews/describe b/gcloud/infra-manager/previews/describe index b2c7c4be0..21b34376d 100644 --- a/gcloud/infra-manager/previews/describe +++ b/gcloud/infra-manager/previews/describe @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument preview on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/infra-manager/previews/list b/gcloud/infra-manager/previews/list index 9677977cb..937b0f6f2 100644 --- a/gcloud/infra-manager/previews/list +++ b/gcloud/infra-manager/previews/list @@ -2,7 +2,7 @@ NAME gcloud infra-manager previews list - list previews SYNOPSIS - gcloud infra-manager previews list --location=LOCATION + gcloud infra-manager previews list [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -14,7 +14,7 @@ EXAMPLES $ gcloud infra-manager previews list --location=us-central1 -REQUIRED FLAGS +FLAGS Location resource - Location to list previews This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -22,16 +22,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --location on the command line with a fully specified name; + ◆ set the property infra-manager/location with a fully specified name; ◆ set the property core/project; ◆ provide the argument --project on the command line. - This must be specified. - --location=LOCATION ID of the location or fully qualified identifier for the location. To set the location attribute: - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/infra-manager/resources/describe b/gcloud/infra-manager/resources/describe index be2abe2bb..812a0a478 100644 --- a/gcloud/infra-manager/resources/describe +++ b/gcloud/infra-manager/resources/describe @@ -56,7 +56,8 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument resource on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. --revision=REVISION revisions TBD diff --git a/gcloud/infra-manager/resources/list b/gcloud/infra-manager/resources/list index 43d2c068c..684cbd8c8 100644 --- a/gcloud/infra-manager/resources/list +++ b/gcloud/infra-manager/resources/list @@ -54,7 +54,8 @@ REQUIRED FLAGS To set the location attribute: ▸ provide the argument --revision on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/infra-manager/revisions/describe b/gcloud/infra-manager/revisions/describe index 12cce8f87..957e17f2b 100644 --- a/gcloud/infra-manager/revisions/describe +++ b/gcloud/infra-manager/revisions/describe @@ -54,7 +54,8 @@ POSITIONAL ARGUMENTS To set the location attribute: ▸ provide the argument revision on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/infra-manager/revisions/list b/gcloud/infra-manager/revisions/list index 01dc09980..6253b90ed 100644 --- a/gcloud/infra-manager/revisions/list +++ b/gcloud/infra-manager/revisions/list @@ -47,7 +47,8 @@ REQUIRED FLAGS To set the location attribute: ▸ provide the argument --deployment on the command line with a fully specified name; - ▸ provide the argument --location on the command line. + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/infra-manager/terraform-versions/describe b/gcloud/infra-manager/terraform-versions/describe new file mode 100644 index 000000000..a9aef4d3f --- /dev/null +++ b/gcloud/infra-manager/terraform-versions/describe @@ -0,0 +1,62 @@ +NAME + gcloud infra-manager terraform-versions describe - describe Terraform + versions + +SYNOPSIS + gcloud infra-manager terraform-versions describe + (TERRAFORM_VERSION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Terraform version + +EXAMPLES + To describe a Terraform version 1.5.7 in project p1 at location + us-central1, run: + + $ gcloud infra-manager terraform-versions describe \ + projects/p1/locations/us-central1/terraformVersions/1.5.7 + +POSITIONAL ARGUMENTS + TerraformVersion resource - The Terraform version to describe 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 terraform_version on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TERRAFORM_VERSION + ID of the terraformVersion or fully qualified identifier for the + terraformVersion. + + To set the terraform_version attribute: + ▸ provide the argument terraform_version on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument terraform_version on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. + +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 config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/infra-manager/terraform-versions/help b/gcloud/infra-manager/terraform-versions/help new file mode 100644 index 000000000..7ea647229 --- /dev/null +++ b/gcloud/infra-manager/terraform-versions/help @@ -0,0 +1,23 @@ +NAME + gcloud infra-manager terraform-versions - manage Terraform version + resources + +SYNOPSIS + gcloud infra-manager terraform-versions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Terraform version resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe Terraform versions. + + list + List Terraform versions. diff --git a/gcloud/infra-manager/terraform-versions/list b/gcloud/infra-manager/terraform-versions/list new file mode 100644 index 000000000..4a1082fab --- /dev/null +++ b/gcloud/infra-manager/terraform-versions/list @@ -0,0 +1,78 @@ +NAME + gcloud infra-manager terraform-versions list - list Terraform versions + +SYNOPSIS + gcloud infra-manager terraform-versions list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Terraform versions + +EXAMPLES + To list all Terraform versions at location us-central1, run: + + $ gcloud infra-manager terraform-versions list --location=us-central1 + +FLAGS + Location resource - Location to list Terraform versions This represents a + Cloud 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 --location on the command line with a fully + specified name; + ◆ set the property infra-manager/location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/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. + + --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 config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/metastore/services/create b/gcloud/metastore/services/create index d649c1dfc..f8d129f76 100644 --- a/gcloud/metastore/services/create +++ b/gcloud/metastore/services/create @@ -21,6 +21,7 @@ SYNOPSIS --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE | --enable-scheduled-backup --scheduled-backup-cron=SCHEDULED_BACKUP_CRON --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -329,6 +330,39 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + At most one of these can be specified: + + --scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE + Path to a JSON file containing a mapping of scheduled backup + configurations key-value pairs to apply to the scheduled backup. + + For example: + + backup_configs.json + { + "enabled": true, + "cron_schedule": "0 * * * *", + "backup_location": "gs://example-bucket", + "time_zone": "UTC" + } + + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + --enable-scheduled-backup + Enable or disable scheduled backups for the Metastore service. + + --scheduled-backup-cron=SCHEDULED_BACKUP_CRON + Specify the frequency of a scheduled backup of the metastore + service. + + --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION + Set the Cloud Storage URI to store the scheduled backups of the + metastore service. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/metastore/services/restore b/gcloud/metastore/services/restore index 2ea84b1a7..ca74449d2 100644 --- a/gcloud/metastore/services/restore +++ b/gcloud/metastore/services/restore @@ -3,12 +3,13 @@ NAME SYNOPSIS gcloud metastore services restore (SERVICE : --location=LOCATION) - --backup=BACKUP [--async] + (--backup=BACKUP | --backup-location=BACKUP_LOCATION) [--async] [--restore-type=RESTORE_TYPE; default="metadata-only"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Restore a Dataproc Metastore service from the given backup. + Restore a Dataproc Metastore service from the given backup or + backup-location If run asynchronously with --async, exits after printing an operation name that can be used to poll the status of the creation via: @@ -22,6 +23,12 @@ EXAMPLES $ gcloud metastore services restore my-service --backup=my-backup \ --restore-type=full + To restore a Dataproc Metastore service with the name my-service from the + backup-location gs://gcs_bucket with a FULL restore type, run: + + $ gcloud metastore services restore my-service \ + --backup-location=gs://gcs_bucket --restore-type=full + POSITIONAL ARGUMENTS Service resource - Arguments and flags that specify the Dataproc Metastore service you want to restore. The arguments in this group can be used to @@ -57,10 +64,20 @@ POSITIONAL ARGUMENTS ▸ set the property metastore/location. REQUIRED FLAGS - --backup=BACKUP - The backup resource to restore from. This can be the backup's ID, - fully-qualified URL, or relative name in the form - projects/{project_id}/locations/{location_id}/services/{service_id}/backups/{backup_id}. + The backup resource or the location of the backup artifacts to store from. + + Exactly one of these must be specified: + + --backup=BACKUP + The backup resource to restore from. This can be the backup's ID, + fully-qualified URL, or relative name in the form + projects/{project_id}/locations/{location_id}/services/{service_id}/backups/{backup_id}. + + --backup-location=BACKUP_LOCATION + The location of the backup artifacts to restore from. This should be + a Cloud Storage URI, contains backup avro files under "avro/", + backup_metastore.json and service.json, in the form + gs://. OPTIONAL FLAGS --async diff --git a/gcloud/metastore/services/update b/gcloud/metastore/services/update index 6e30cc6f1..b61041c0d 100644 --- a/gcloud/metastore/services/update +++ b/gcloud/metastore/services/update @@ -12,6 +12,7 @@ SYNOPSIS --keytab=KEYTAB --krb5-config=KRB5_CONFIG] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE | --enable-scheduled-backup --scheduled-backup-cron=SCHEDULED_BACKUP_CRON --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION] [--update-auxiliary-versions-from-file=UPDATE_AUXILIARY_VERSIONS_FROM_FILE | --add-auxiliary-versions=[ADD_AUXILIARY_VERSIONS, ...] --clear-auxiliary-versions] [--update-hive-metastore-configs-from-file=UPDATE_HIVE_METASTORE_CONFIGS_FROM_FILE | --update-hive-metastore-configs=[KEY=VALUE, @@ -199,6 +200,39 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + At most one of these can be specified: + + --scheduled-backup-configs-from-file=SCHEDULED_BACKUP_CONFIGS_FROM_FILE + Path to a JSON file containing a mapping of scheduled backup + configurations key-value pairs to apply to the scheduled backup. + + For example: + + backup_configs.json + { + "enabled": true, + "cron_schedule": "0 * * * *", + "backup_location": "gs://example-bucket", + "time_zone": "UTC" + } + + Scheduled backup configurations to enable a scheduled backup of the + metastore service. + + --enable-scheduled-backup + Enable or disable scheduled backups for the Metastore service. + + --scheduled-backup-cron=SCHEDULED_BACKUP_CRON + Specify the frequency of a scheduled backup of the metastore + service. + + --scheduled-backup-location=SCHEDULED_BACKUP_LOCATION + Set the Cloud Storage URI to store the scheduled backups of the + metastore service. + Auxiliary versions configuration for the Dataproc Metastore service. When specified, a secondary Hive metastore service is created along with the primary service. diff --git a/gcloud/notebooks/instances/create b/gcloud/notebooks/instances/create index e0c01692f..0b34b35e8 100644 --- a/gcloud/notebooks/instances/create +++ b/gcloud/notebooks/instances/create @@ -164,7 +164,7 @@ FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3. + TPU_V2, TPU_V3, NVIDIA_L4. Boot disk configurations. diff --git a/gcloud/notebooks/instances/update b/gcloud/notebooks/instances/update index f19504048..972d03dda 100644 --- a/gcloud/notebooks/instances/update +++ b/gcloud/notebooks/instances/update @@ -75,7 +75,7 @@ REQUIRED FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3. + TPU_V2, TPU_V3, NVIDIA_L4. --labels=[KEY=VALUE,...] Labels to apply to this instance. These can be later modified by the diff --git a/gcloud/projects/create b/gcloud/projects/create index 96ada175d..f21a809e9 100644 --- a/gcloud/projects/create +++ b/gcloud/projects/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud projects create [PROJECT_ID] [--no-enable-cloud-apis] [--folder=FOLDER_ID] [--labels=[KEY=VALUE,...]] [--name=NAME] [--organization=ORGANIZATION_ID] [--set-as-default] - [GCLOUD_WIDE_FLAG ...] + [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a new project with the given project ID. By default, projects are @@ -64,6 +64,12 @@ FLAGS --set-as-default Set newly created project as [core.project] property. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + "=". + + Example: 123/environment=production,123/costCenter=marketing + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/resource-manager/folders/create b/gcloud/resource-manager/folders/create index fb8a7c80c..339c4273b 100644 --- a/gcloud/resource-manager/folders/create +++ b/gcloud/resource-manager/folders/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud resource-manager folders create --display-name=DISPLAY_NAME [--async] [--folder=FOLDER_ID] [--organization=ORGANIZATION_ID] - [GCLOUD_WIDE_FLAG ...] + [--tags=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a new folder in the given parent folder or organization. @@ -37,6 +37,12 @@ OPTIONAL FLAGS --organization=ORGANIZATION_ID ID for the organization to use as a parent + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + "=". + + Example: 123/environment=production,123/costCenter=marketing + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/sql/backups/list b/gcloud/sql/backups/list index 400730032..2d359b5f5 100644 --- a/gcloud/sql/backups/list +++ b/gcloud/sql/backups/list @@ -3,7 +3,7 @@ NAME a given instance SYNOPSIS - gcloud sql backups list --instance=INSTANCE, -i INSTANCE + gcloud sql backups list [--instance=INSTANCE, -i INSTANCE] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -11,7 +11,7 @@ DESCRIPTION Lists all backups associated with the project or a given Cloud SQL instance and configuration in the reverse chronological order of the enqueued time. -REQUIRED FLAGS +FLAGS --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID or "-" for all instances. diff --git a/gcloud/sql/instances/acquire-ssrs-lease b/gcloud/sql/instances/acquire-ssrs-lease new file mode 100644 index 000000000..30a1d1317 --- /dev/null +++ b/gcloud/sql/instances/acquire-ssrs-lease @@ -0,0 +1,48 @@ +NAME + gcloud sql instances acquire-ssrs-lease - acquires a SQL Server Reporting + Services lease on a Cloud SQL instance + +SYNOPSIS + gcloud sql instances acquire-ssrs-lease INSTANCE + --report-database=REPORT_DATABASE --service-login=SERVICE_LOGIN + --setup-login=SETUP_LOGIN [--duration=DURATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Acquire a SQL Server Reporting Services lease on a Cloud SQL instance. + +EXAMPLES + To acquire a SQL Server Reporting Services lease on an instance: + + $ gcloud sql instances acquire-ssrs-lease instance-foo \ + --setup-login=setuplogin --service-login=reportuser \ + --report-database=ReportServer --duration=4h + +POSITIONAL ARGUMENTS + INSTANCE + Cloud SQL instance ID. + +REQUIRED FLAGS + --report-database=REPORT_DATABASE + Existing or new report database name in the Cloud SQL for SQL Server + instance that is used for SSRS setup. + + --service-login=SERVICE_LOGIN + Existing login in the Cloud SQL for SQL Server instance that is used as + the service login for SSRS setup. + + --setup-login=SETUP_LOGIN + Existing login in the Cloud SQL for SQL Server instance that is used as + the setup login for SSRS setup. + +OPTIONAL FLAGS + --duration=DURATION + Time duration, in hours, that the lease will be active to allow SSRS + setup. Default lease duration is 5 hours if this flag is not specified. + +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. diff --git a/gcloud/sql/instances/help b/gcloud/sql/instances/help index 97b66adec..ac786ccf2 100644 --- a/gcloud/sql/instances/help +++ b/gcloud/sql/instances/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + acquire-ssrs-lease + Acquires a SQL Server Reporting Services lease on a Cloud SQL instance. + clone Clones a Cloud SQL instance. @@ -54,6 +57,9 @@ COMMANDS reencrypt Reencrypts a Cloud SQL CMEK instance. + release-ssrs-lease + Releases a SQL Server Reporting Services lease on a Cloud SQL instance. + reset-ssl-config Deletes all client certificates and generates a new server certificate. diff --git a/gcloud/sql/instances/release-ssrs-lease b/gcloud/sql/instances/release-ssrs-lease new file mode 100644 index 000000000..2552f8560 --- /dev/null +++ b/gcloud/sql/instances/release-ssrs-lease @@ -0,0 +1,26 @@ +NAME + gcloud sql instances release-ssrs-lease - releases a SQL Server Reporting + Services lease on a Cloud SQL instance + +SYNOPSIS + gcloud sql instances release-ssrs-lease INSTANCE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Release a SQL Server Reporting Services lease on a Cloud SQL instance. + +EXAMPLES + To release a SQL Server Reporting Services lease on an instance: + + $ gcloud sql instances release-ssrs-lease instance-foo + +POSITIONAL ARGUMENTS + INSTANCE + Cloud SQL instance ID. + +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. diff --git a/gcloud/tasks/buffer b/gcloud/tasks/buffer new file mode 100644 index 000000000..d45abce01 --- /dev/null +++ b/gcloud/tasks/buffer @@ -0,0 +1,41 @@ +NAME + gcloud tasks buffer - buffers a task into a queue + +SYNOPSIS + gcloud tasks buffer --location=LOCATION --queue=QUEUE [--task-id=TASK_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Buffers a task into a queue. + +EXAMPLES + To buffer into a queue: + + $ gcloud tasks buffer --queue=my-queue --location=us-central1 + +REQUIRED FLAGS + --location=LOCATION + The location where the queue exists. + + --queue=QUEUE + The queue the task belongs to. + +OPTIONAL FLAGS + --task-id=TASK_ID + The task ID for the task being created. + +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 tasks buffer + + $ gcloud beta tasks buffer + diff --git a/gcloud/tasks/help b/gcloud/tasks/help index c8c11d822..f6d767a64 100644 --- a/gcloud/tasks/help +++ b/gcloud/tasks/help @@ -27,6 +27,9 @@ GROUPS COMMANDS COMMAND is one of the following: + buffer + Buffers a task into a queue. + create-app-engine-task Create and add a task that targets App Engine. diff --git a/gcloud/tasks/queues/create b/gcloud/tasks/queues/create index bc3fcaf92..997a9ffaf 100644 --- a/gcloud/tasks/queues/create +++ b/gcloud/tasks/queues/create @@ -2,14 +2,19 @@ NAME gcloud tasks queues create - create a Cloud Tasks queue SYNOPSIS - gcloud tasks queues create QUEUE [--location=LOCATION] + gcloud tasks queues create QUEUE + [--http-header-override=HEADER_FIELD: HEADER_VALUE] + [--http-method-override=HTTP_METHOD_OVERRIDE] + [--http-uri-override=KEY:VALUE,[KEY:VALUE,...]] [--location=LOCATION] [--log-sampling-ratio=LOG_SAMPLING_RATIO] [--max-attempts=MAX_ATTEMPTS] [--max-backoff=MAX_BACKOFF] [--max-concurrent-dispatches=MAX_CONCURRENT_DISPATCHES] [--max-dispatches-per-second=MAX_DISPATCHES_PER_SECOND] [--max-doublings=MAX_DOUBLINGS] [--max-retry-duration=MAX_RETRY_DURATION] [--min-backoff=MIN_BACKOFF] - [--routing-override=KEY:VALUE,[...]] [GCLOUD_WIDE_FLAG ...] + [--routing-override=KEY:VALUE,[...]] + [[--http-oauth-service-account-email-override=HTTP_OAUTH_SERVICE_ACCOUNT_EMAIL_OVERRIDE : --http-oauth-token-scope-override=HTTP_OAUTH_TOKEN_SCOPE_OVERRIDE] | [--http-oidc-service-account-email-override=HTTP_OIDC_SERVICE_ACCOUNT_EMAIL_OVERRIDE : --http-oidc-token-audience-override=HTTP_OIDC_TOKEN_AUDIENCE_OVERRIDE]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION The flags available to this command represent the fields of a queue that @@ -28,6 +33,28 @@ POSITIONAL ARGUMENTS The queue to create. FLAGS + --http-header-override=HEADER_FIELD: HEADER_VALUE + If provided, the specified HTTP headers override the existing headers + for all tasks in the queue. If a task has a header with the same Key as + a queue-level header override, then the value of the task header will + be overriden with the value of the queue-level header. Otherwise, the + queue-level header will be added to the task headers. Header values can + contain commas. This flag can be repeated. Repeated header fields will + have their values overridden. + + --http-method-override=HTTP_METHOD_OVERRIDE + If provided, the specified HTTP method type override is used for all + tasks in the queue, no matter what is set at the task-level. + + --http-uri-override=KEY:VALUE,[KEY:VALUE,...] + If provided, the specified HTTP target URI override is used for all + tasks in the queue depending on what is set as the mode. Allowed values + for mode are: ALWAYS, IF_NOT_EXISTS. If not set, mode defaults to + ALWAYS. + + KEY must be at least one of: [scheme, host, port, path, query, mode]. + Any missing keys will use the default. + --location=LOCATION The location where we want to manage the queue or task. If not specified, uses the location of the current project's App Engine app if @@ -87,6 +114,47 @@ FLAGS KEY must be at least one of: [service, version, instance]. Any missing keys will use the default. + If specified, all Authorization headers in the HttpRequest.headers field + will be overridden for any tasks executed on this queue. + + At most one of these can be specified: + + OAuth2 + + --http-oauth-service-account-email-override=HTTP_OAUTH_SERVICE_ACCOUNT_EMAIL_OVERRIDE + The service account email to be used for generating an OAuth2 + access token to be included in the request sent to the target when + executing the task. The service account must be within the same + project as the queue. The caller must have + 'iam.serviceAccounts.actAs' permission for the service account. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --http-oauth-token-scope-override=HTTP_OAUTH_TOKEN_SCOPE_OVERRIDE + The scope to be used when generating an OAuth2 access token to be + included in the request sent to the target when executing the task. + If not specified, 'https://www.googleapis.com/auth/cloud-platform' + will be used. + + OpenId Connect + + --http-oidc-service-account-email-override=HTTP_OIDC_SERVICE_ACCOUNT_EMAIL_OVERRIDE + The service account email to be used for generating an OpenID + Connect token to be included in the request sent to the target when + executing the task. The service account must be within the same + project as the queue. The caller must have + 'iam.serviceAccounts.actAs' permission for the service account. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --http-oidc-token-audience-override=HTTP_OIDC_TOKEN_AUDIENCE_OVERRIDE + The audience to be used when generating an OpenID Connect token to + be included in the request sent to the target when executing the + task. If not specified, the URI specified in the target will be + used. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/tasks/queues/update b/gcloud/tasks/queues/update index d7f7b67d6..c8d990260 100644 --- a/gcloud/tasks/queues/update +++ b/gcloud/tasks/queues/update @@ -3,6 +3,20 @@ NAME SYNOPSIS gcloud tasks queues update QUEUE [--location=LOCATION] + [--clear-http-header-override + | --http-header-override=HEADER_FIELD: HEADER_VALUE] + [--clear-http-method-override + | --http-method-override=HTTP_METHOD_OVERRIDE] + [--clear-http-oauth-service-account-email-override + | --http-oauth-service-account-email-override=HTTP_OAUTH_SERVICE_ACCOUNT_EMAIL_OVERRIDE] + [--clear-http-oauth-token-scope-override + | --http-oauth-token-scope-override=HTTP_OAUTH_TOKEN_SCOPE_OVERRIDE] + [--clear-http-oidc-service-account-email-override + | --http-oidc-service-account-email-override=HTTP_OIDC_SERVICE_ACCOUNT_EMAIL_OVERRIDE] + [--clear-http-oidc-token-audience-override + | --http-oidc-token-audience-override=HTTP_OIDC_TOKEN_AUDIENCE_OVERRIDE] + [--clear-http-uri-override + | --http-uri-override=KEY:VALUE,[KEY:VALUE,...]] [--clear-log-sampling-ratio | --log-sampling-ratio=LOG_SAMPLING_RATIO] [--clear-max-attempts | --max-attempts=MAX_ATTEMPTS] [--clear-max-backoff | --max-backoff=MAX_BACKOFF] @@ -39,6 +53,90 @@ FLAGS specified, uses the location of the current project's App Engine app if there is an associated app. + At most one of these can be specified: + + --clear-http-header-override + Clear the field corresponding to --http-header-override. + + --http-header-override=HEADER_FIELD: HEADER_VALUE + If provided, the specified HTTP headers override the existing headers + for all tasks in the queue. If a task has a header with the same Key + as a queue-level header override, then the value of the task header + will be overriden with the value of the queue-level header. + Otherwise, the queue-level header will be added to the task headers. + Header values can contain commas. This flag can be repeated. Repeated + header fields will have their values overridden. + + At most one of these can be specified: + + --clear-http-method-override + Clear the field corresponding to --http-method-override. + + --http-method-override=HTTP_METHOD_OVERRIDE + If provided, the specified HTTP method type override is used for all + tasks in the queue, no matter what is set at the task-level. + + At most one of these can be specified: + + --clear-http-oauth-service-account-email-override + Clear the field corresponding to + --http-oauth-service-account-email-override. + + --http-oauth-service-account-email-override=HTTP_OAUTH_SERVICE_ACCOUNT_EMAIL_OVERRIDE + The service account email to be used for generating an OAuth2 access + token to be included in the request sent to the target when executing + the task. The service account must be within the same project as the + queue. The caller must have 'iam.serviceAccounts.actAs' permission + for the service account. + + At most one of these can be specified: + + --clear-http-oauth-token-scope-override + Clear the field corresponding to --http-oauth-token-scope-override. + + --http-oauth-token-scope-override=HTTP_OAUTH_TOKEN_SCOPE_OVERRIDE + The scope to be used when generating an OAuth2 access token to be + included in the request sent to the target when executing the task. + If not specified, 'https://www.googleapis.com/auth/cloud-platform' + will be used. + + At most one of these can be specified: + + --clear-http-oidc-service-account-email-override + Clear the field corresponding to + --http-oidc-service-account-email-override. + + --http-oidc-service-account-email-override=HTTP_OIDC_SERVICE_ACCOUNT_EMAIL_OVERRIDE + The service account email to be used for generating an OpenID Connect + token to be included in the request sent to the target when executing + the task. The service account must be within the same project as the + queue. The caller must have 'iam.serviceAccounts.actAs' permission + for the service account. + + At most one of these can be specified: + + --clear-http-oidc-token-audience-override + Clear the field corresponding to --http-oidc-token-audience-override. + + --http-oidc-token-audience-override=HTTP_OIDC_TOKEN_AUDIENCE_OVERRIDE + The audience to be used when generating an OpenID Connect token to be + included in the request sent to the target when executing the task. + If not specified, the URI specified in the target will be used. + + At most one of these can be specified: + + --clear-http-uri-override + Clear the field corresponding to --http-uri-override. + + --http-uri-override=KEY:VALUE,[KEY:VALUE,...] + If provided, the specified HTTP target URI override is used for all + tasks in the queue depending on what is set as the mode. Allowed + values for mode are: ALWAYS, IF_NOT_EXISTS. If not set, mode defaults + to ALWAYS. + + KEY must be at least one of: [scheme, host, port, path, query, mode]. + Any missing keys will use the default. + At most one of these can be specified: --clear-log-sampling-ratio diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index 4633c88ff..23e899fd4 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -10,9 +10,10 @@ SYNOPSIS [--container-env=[CONTAINER_ENV,...]] [--container-run-as-user=CONTAINER_RUN_AS_USER] [--container-working-dir=CONTAINER_WORKING_DIR] - [--disable-public-ip-addresses] [--disable-ssh-to-vm] - [--disable-tcp-connections] [--enable-audit-agent] - [--enable-confidential-compute] [--enable-nested-virtualization] + [--disable-public-ip-addresses] [--disable-tcp-connections] + [--enable-audit-agent] [--enable-confidential-compute] + [--enable-nested-virtualization] + [--ephemeral-directory=[PROPERTY=VALUE,...]] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--network-tags=[NETWORK_TAGS,...]] @@ -136,10 +137,6 @@ FLAGS Default value is false. If set, instances will have no public IP address. - --disable-ssh-to-vm - Default value is False. If set, workstations disable SSH connections to - the root VM. - --disable-tcp-connections Default value is false. If set, workstations don't allow plain TCP connections. @@ -157,6 +154,9 @@ FLAGS Default value is false. If set, instances will have nested virtualization enabled. + --ephemeral-directory=[PROPERTY=VALUE,...] + Ephemeral directory which won't persist across workstation sessions. + --idle-timeout=IDLE_TIMEOUT; default=7200 How long (in seconds) to wait before automatically stopping an instance that hasn't received any user traffic. A value of 0 indicates that this diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 95e9e457b..693030437 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -21,7 +21,6 @@ SYNOPSIS [--shielded-vtpm] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] - [--disable-ssh-to-vm | --enable-ssh-to-vm] [--disable-tcp-connections | --enable-tcp-connections] [GCLOUD_WIDE_FLAG ...] @@ -229,14 +228,6 @@ FLAGS webstorm WebStorm - At most one of these can be specified: - - --disable-ssh-to-vm - If set, workstations disable SSH connections to the root VM. - - --enable-ssh-to-vm - If set, workstations enable SSH connections to the root VM. - At most one of these can be specified: --disable-tcp-connections