gcloud developer-connect connections git-repository-links delete

NAME
gcloud developer-connect connections git-repository-links delete - delete a single git repository link
SYNOPSIS
gcloud developer-connect connections git-repository-links delete (GIT_REPOSITORY_LINK : --connection=CONNECTION --location=LOCATION) [--async] [--etag=ETAG] [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
Delete a single git repository link.
EXAMPLES
To delete a git repository link my-git-repository-link in a connection my-comection in location us-central1 run: 
gcloud developer-connect connections git-repository-links delete my-git-repository-link --connection=my-connection --location=us-central1
POSITIONAL ARGUMENTS
GitRepositoryLink resource - Name of the 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 git_repository_link 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.

ID of the gitRepositoryLink or fully qualified identifier for the gitRepositoryLink.

To set the git_repository_link attribute:

  • provide the argument git_repository_link on the command line.

This positional argument must be specified if any of the other arguments in this group are specified.

--connection=CONNECTION
The connection id of the gitRepositoryLink resource.

To set the connection attribute:

  • provide the argument git_repository_link on the command line with a fully specified name;
  • provide the argument --connection on the command line.
--location=LOCATION
The location id of the gitRepositoryLink resource.

To set the location attribute:

  • provide the argument git_repository_link 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.
--etag=ETAG
This checksum is computed by the server based on the value of other fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding.
--request-id=REQUEST_ID
An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request.

For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.

The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

--validate-only
If set, validate the request, but do not actually post it.
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 developerconnect/v1 API. The full documentation for this API can be found at: http://cloud.google.com/developer-connect/docs/overview
NOTES
These variants are also available: 
gcloud alpha developer-connect connections git-repository-links delete
 
gcloud beta developer-connect connections git-repository-links delete