gcloud developer-connect insights-configs delete - delete insightsConfigs

gcloud 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 beused to specify the attributes of this resource. (NOTE) Some attributes are notgiven arguments in this group but can be set in other ways.

To set theproject attribute:

• provide the argumentinsights_config on the command line with afully specified name;
• provide the argument--project on the command line;
• set the propertycore/project.

This must be specified.

INSIGHTS_CONFIG

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

To set theinsights_config attribute:

• provide the argumentinsights_config on the command line.

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

--location=LOCATION

The location id of the insightsConfig resource.

To set thelocation attribute:

• provide the argumentinsights_config on the command line with afully 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, andmay be sent on update and delete requests to ensure the client has an up-to-datevalue before proceeding.

--request-id=REQUEST_ID

An optional request ID to identify requests. Specify a unique request ID so thatif you must retry your request, the server will know to ignore the request if ithas already been completed. The server will guarantee that for at least 60minutes after the first request.

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

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

--validate-only

If set, validate the request, but do not actually post it.

Run$gcloud help for details.