gcloud beta source project-configs update - update the Cloud Source Repositories configuration of the current project
gcloud beta source project-configs update (--disable-pushblock | --enable-pushblock | --message-format=MESSAGE_FORMAT --service-account=SERVICE_ACCOUNT --topic-project=TOPIC_PROJECT --add-topic=ADD_TOPIC | --remove-topic=REMOVE_TOPIC | --update-topic=UPDATE_TOPIC) [GCLOUD_WIDE_FLAG ...]
To enable PushBlock for all repositories under current project, run:
$ gcloud beta source project-configs update --enable-pushblock
To associate a Cloud Pub/Sub topic to receive repository update notifications, run:
$ gcloud beta source project-configs update --add-topic=TOPIC_NAME \ --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json
- Exactly one of these must be specified:
- --disable-pushblock
Disable PushBlock for all repositories under current project. PushBlock allows repository owners to block git push transactions containing private key data.
- --enable-pushblock
Enable PushBlock for all repositories under current project. PushBlock allows repository owners to block git push transactions containing private key data.
- Manage Cloud Pub/Sub topics associated with the Cloud project.
- --message-format=MESSAGE_FORMAT
The format of the message to publish to the topic. MESSAGE_FORMAT must be one of: json, protobuf.
- --service-account=SERVICE_ACCOUNT
Email address of the service account used for publishing Cloud Pub/Sub messages. This service account needs to be in the same project as the project. When added, the caller needs to have iam.serviceAccounts.actAs permission on this service account. If unspecified, it defaults to the Compute Engine default service account.
- --topic-project=TOPIC_PROJECT
Cloud project for the topic. If not set, the currently set project will be used.
- At most one of these can be specified:
- Topic resource - The Cloud Pub/Sub topic to add to the project. 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 --add-topic on the command line with a fully specified name;
provide the argument --topic-project on the command line;
set the property core/project.
- --add-topic=ADD_TOPIC
ID of the topic or fully qualified identifier for the topic. To set the topic attribute:
- —
provide the argument --add-topic on the command line.
- Topic resource - The Cloud Pub/Sub topic to remove from the project. 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 --remove-topic on the command line with a fully specified name;
provide the argument --topic-project on the command line;
set the property core/project.
- --remove-topic=REMOVE_TOPIC
ID of the topic or fully qualified identifier for the topic. To set the topic attribute:
- —
provide the argument --remove-topic on the command line.
- Topic resource - The Cloud Pub/Sub topic to update in the project. 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 --update-topic on the command line with a fully specified name;
provide the argument --topic-project on the command line;
set the property core/project.
- --update-topic=UPDATE_TOPIC
ID of the topic or fully qualified identifier for the topic. To set the topic attribute:
- —
provide the argument --update-topic on the command line.
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.
This command is currently in beta and might change without notice. These variants are also available:
$ gcloud source project-configs update
$ gcloud alpha source project-configs update