gcloud alpha developer-connect insights-configs delete

Stay organized with collections Save and categorize content based on your preferences.

gcloud alpha developer-connect insights-configs delete - delete insightsConfigs

gcloud alpha developer-connect insights-configs delete (INSIGHTS_CONFIG : --location=LOCATION) [--async] [--etag=ETAG] [--request-id=REQUEST_ID] [--validate-only] [GCLOUD_WIDE_FLAG …]

InsightsConfig resource - Value for parent. 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 insights_config 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.

INSIGHTS_CONFIG

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

To set the insights_config attribute:

• provide the argument insights_config on the command line.

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

--location=LOCATION

The location id of the insightsConfig resource.

To set the location attribute:

• provide the argument insights_config on the command line with a fully specified name;
• provide the argument --location on the command line.

--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.

Run $ gcloud help for details.