vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-command-options-logpush-job-delete" "> --><-- <section "id="section-command-example-logpush-job-delete" "> --> Examples Delete http_requests log push job for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis logpush-job-delete 31984fea73a15b45779fa0df4ef62f9b --dataset http_requests -i cis-demo --force
<-- </section "id="section-command-example-logpush-job-delete" "> --><-- </section "id="section-logpush-job-delete" "> --><-- <section "id="section-get-log-push-available-fields" "> --> ibmcloud cis logpush-available-fields Get all available fields for a data set (Enterprise plan only). ibmcloud cis logpush-available-fields DNS_DOMAIN_ID --dataset DATASET] -i, --instance INSTANCE] ! ! ! ! ! ! ! !
<-- <section "id="section-command-options-logpush-available-fields" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--dataset value: The category of logs you want to receive. This value cannot be changed after the job is created. Valid values: http_requests, range_events, firewall_events. The default value is http_requests.-i , --instance value: Instance name or ID.
Delete a certificate uploaded to CIS edge DELETE /v1/{crn}/zones/{domain_id}/custom_certificates/{cert_id} internet-svcs.security.manage internet-svcs.custom-certificates.delete 
 Get origin certificate issued by CIS GET /v1/{crn}/zones/{domain_id}/origin_certificates internet-svcs.security.read internet-svcs.origin-certificates.read 
 Create an origin certificate issued by CIS POST /v1/{crn}/zones/{domain_id}/origin_certificates internet-svcs.security.manage internet-svcs.origin-certificates.create 
 Revoke an origin certificate issued by CIS DELETE /v1/{crn}/zones/{domain_id}/origin_certificates/{cert_id} internet-svcs.security.manage internet-svcs.origin-certificates.delete 







 Edge Functions 



Table 15. Edge Functions

 Action Method IAM ACTION AT ACTION 

 Get edge function scripts GET /v1/{crn}/workers/scripts internet-svcs.performance.read internet-svcs.edge-functions-scripts.read 
 Create edge function script POST /v1/{crn}/workers/scripts internet-svcs.performance.manage internet-svcs.edge-functions-scripts.create 
 Update edge function script PUT /v1/{crn}/workers/scripts/{script_name} internet-svcs.performance.update internet-svcs.edge-functions-scripts.update 
 Delete edge function script DELETE /v1/{crn}/workers/scripts/{script_name} internet-svcs.performance.manage internet-svcs.edge-functions-scripts.delete 
 Get edge function routes GET /v1/{crn}/zones/{domain_id}/workers/routes internet-svcs.performance.read internet-svcs.edge-functions-routes.read 
 Create edge function route POST /v1/{crn}/zones/{domain_id}/workers/routes internet-svcs.performance.manage internet-svcs.edge-functions-routes.create
curl -X DELETE "$rias_endpoint/v1/load_balancers/$lbid?version=$version&generation=2" 
-H "Authorization:$iam_token"

The status of the load balancer changes to deleting immediately, but it is still returned when you do a list query. The deletion of a load balancer can take up to 30 minutes. You can request other subnet resources to be deleted in parallel while you wait for the load balancer to be deleted. However, the subnet can't be deleted until the load balancer and all other resources in the subnet no longer appear in the list queries.





 Delete all network interfaces in the subnet, if any 

An instance can have multiple network interfaces, and those network interfaces can belong to multiple subnets of the VPC. Before a subnet can be deleted, any network interface in the subnet must be deleted first. The only way to delete a network interface in a subnet is to delete the instance.

To list all network interfaces of an instance, run the following command:

curl -X GET "$vpc_api_endpoint/v1/instances/$vsi/network_interfaces?version=$version&generation=2" 
-H "Authorization:$iam_token"

If a secondary network interface exists in the subnet you are trying to delete, you need to delete the instance. A network interface cannot be deleted from the instance without deleting the instance.

To list all instances in your account, run the following command:

curl -X GET "$vpc_api_endpoint/v1/instances?version=$version&generation=2" 
-H "Authorization:$iam_token"

If you are deleting all instances in the VPC, you can run the following command for each instance in the VPC, where $vsi is the ID of the instance you want to delete. When the instance is deleted, all network interfaces in other subnets, if any, are deleted automatically.

Instances must be stopped before you can delete them.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-show-ratelimit-rule-options" "> --><-- <section "id="section-show-ratelimit-rule-examples" "> --> Examples Get the details of rate limiting rule 372e67954025e0ba6aaa6d586b9e0b59. ibmcloud cis ratelimit-rule 31984fea73a15b45779fa0df4ef62f9b 372e67954025e0ba6aaa6d586b9e0b59 -i "cis-demo"
<-- </section "id="section-show-ratelimit-rule-examples" "> --><-- </section "id="section-show-ratelimit-rule" "> --><-- <section "id="section-delete-ratelimit-rule" "> --> ibmcloud cis ratelimit-rule-delete Delete a rate limiting rule by ID. ibmcloud cis ratelimit-rule-delete DNS_DOMAIN_ID RATELIMIT_RULE_ID --instance INSTANCE] ! ! ! ! ! ! ! !
<-- <section "id="section-delete-ratelimit-rule-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.RATELIMIT_RULE_ID: The ID of rate limit rule. Required.-i, --instance: Instance name or ID.
Adding, viewing, and deleting clusters for Security and Compliance Readiness Bundle instances 

New deployments of Security and Compliance Readiness Bundle instances are no longer supported. You can still add or delete clusters, add or delete VMware ESXi™ servers or NFS storage, and add or remove services for existing instances. You can also view and delete your Security and Compliance Readiness Bundle instances.

You can add your own clusters to Security and Compliance Readiness Bundle instances to expand the compute and storage capacity. Within a cluster, you can manage VMware ESXi servers for better resource allocation and high availability. When no longer needed, delete the added clusters from your instances.

The procedures to add, view, and delete clusters for Security and Compliance Readiness Bundle instances are similar to the procedures for VMware vCenter Server® instances. For more information, see the following topics:



*  [Adding clusters to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters)
*  [Viewing clusters in vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewingclusters)
*  [Deleting clusters from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingclusters)
* If you delete the vCenter Server instance A with Caveonix RiskForesight installed, and you used the IP addresses of the dedicated private subnet that was ordered for the service in the vCenter Server instance B, the dedicated private subnet is canceled upon deletion of the vCenter Server instance A.



* If you installed the Caveonix RiskForesight service before VMware Solutions v4.0, and you then delete that service, you must manually remove the DNS entries. For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Ordering Caveonix RiskForesight](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix_ordering)
* [Managing Caveonix RiskForesight](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingcaveonix)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
Alternatively, if you are using an SDK, [obtain an IAM API key](https://cloud.ibm.com/iam/apikeys) and set the client options by using environment variables.

export CD_TOOLCHAIN_AUTH_TYPE=iam && export CD_TOOLCHAIN_APIKEY={iam_api_key} && export CD_TOOLCHAIN_URL={base_url}
2. Delete the toolchain that you want to remove.



* Curl
* Java
* Node
* Python
* Go



curl -X DELETE "{base_url}/toolchains/{toolchain_id}" -H 'Authorization: Bearer {token}'

import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.CdToolchain;
import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.model.;
...
CdToolchain toolchainService = CdToolchain.newInstance();
DeleteToolchainOptions deleteToolchainOptions = new DeleteToolchainOptions.Builder()
.toolchainId({toolchain_id})
.build();
Response<Void> response = toolchainService.deleteToolchain(deleteToolchainOptions).execute();

const CdToolchainV2 = require('@ibm-cloud/continuous-delivery/cd-toolchain/v2');
const toolchainService = CdToolchainV2.newInstance();
...
(async() => {
const response = await toolchainService.deleteToolchain({
toolchainId: {toolchain_id}
});
})();

from ibm_continuous_delivery.cd_toolchain_v2 import CdToolchainV2
...
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/icons/action-menu-icon.svg) > Remove.
4. Select Remove.



If the source service is removed from the account, any policies that are created by that service for its dependent services are deleted automatically. Similarly, if the dependent service is removed from the account, any access policies that are delegated to that service are also deleted.





 Removing an authorization by using the CLI 

You can remove any authorization between services in the account if you are assigned the Administrator role on the target service. If you remove any access policies created by the source service for its dependent services, the source service is unable to complete the workflow or access the target service.

The following sample deletes an authorization policy:

ibmcloud iam authorization-policy-delete 12345678-abcd-1a2b-a1b2-1234567890ab

For more information about all of the parameters that are available for this command, see [ibmcloud iam authorization-policy-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_authorization_policy_delete).

If the source service is removed from the account, any policies that are created by that service for its dependent services are deleted automatically. Similarly, if the dependent service is removed from the account, any access policies that are delegated to that service are also deleted.





 Removing an authorization by using the API 

You can remove any authorization between services in the account if you are assigned the Administrator role on the target service. If you remove any access policies created by the source service for its dependent services, the source service is unable to complete the workflow or access the target service.

To delete an authorization policy, use the [IAM Policy Management API](https://cloud.ibm.com/apidocs/iam-policy-managementdelete-policy) as in the following sample request:



* Curl
* Java
To delete the Kubernetes cluster, click on Actions in the top right in the browser tab cluster overview, then Delete cluster.
2. In the tab IAM trusted profiles with the trusted profile TPwithCR, click on Actions and Remove to delete the trusted profile.



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content 



* The source code for the app and the configuration is in the [GitHub repository trusted-profile-enterprise-security](https://github.com/IBM-Cloud/trusted-profile-enterprise-security)
* Blog post [Turn Your Container Into a Trusted Cloud Identity](https://www.ibm.com/cloud/blog/turn-your-container-into-a-trusted-cloud-identity)
* Blog post [Secure Onboarding for Your Workshops and Hackathons](https://www.ibm.com/cloud/blog/secure-onboarding-for-your-workshops-and-hackathons)
[overflow icon](https://cloud.ibm.com/docs-content/v1/content/cb1eb27836421578019401fa7556779109430b29/cis//images/horizontal-overflow-icon.png) of the webhook you want to delete, and select Delete. Select Delete in the confirmation box to confirm, or Cancel to close the confirmation box without completing the delete operation.







 Configuring webhooks using the CLI 



 Creating a webhook using the CLI 

To create a webhook using the CLI, run the following command.

ibmcloud cis alert-webhook-create --name NAME --url URL [--secret SECRET] [-i, --instance INSTANCE] [--output FORMAT]

Where:



* --name valueis the name of the webhook.
* --url value is the POST endpoint to call when dispatching an alert.
* --secret value is the secret that will be passed in the webhook auth header when dispatching a webhook alert.
* -i, --instance value is the instance name or ID. If not set, the context instance specified by 'cis instance-set INSTANCE' is used.
* --output value specifies output format; only JSON is supported.







 Listing all webhooks using the CLI 

To list a webhook using the CLI, run the following command.

ibmcloud cis alert-webhooks [-i, --instance INSTANCE] [--output FORMAT]

Where:



* -i, --instance value is the instance name or ID. If not set, the context instance specified by 'cis instance-set INSTANCE' is used.
* --output value specifies output format; only JSON is supported.







 Getting details for a webhook using the CLI 

To get a webhook using the CLI, run the following command.

ibmcloud cis alert-webhook WEBHOOK_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:
The following example shows a query that you can use to remove a DNS provider configuration from your instance. When you call the API, replace {config_name} with the name of the configuration that you want to delete.

After you delete a configuration, the certificates that are associated with the DNS provider can no longer be rotated automatically. Do not delete configurations that are associated with certificates in your production apps or services.

curl -X DELETE
--H "Authorization: Bearer {iam_token}" "https://{instance_ID}.{region}.secrets-manager.appdomain.cloud/api/v2/configurations/{name}"

A successful response removes the configuration from your service instance. For more information about the required and optional request parameters, see [Remove a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2delete-config-element).





 Next steps 



* [Order a certificate](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-public-certificatesorder-public-certificates).
Optional: Remove your Hyper Protect Crypto Services service instance.

ibmcloud resource service-instance-delete import-keys-demo

If you created more test keys in your service instance, be sure to [remove all encryption keys from your service instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-keysdelete-keys) before you deprovision the instance.







 Next steps 

In this tutorial, you learned how to set up the Hyper Protect Crypto Services key management service API, create an encryption key, and securely import an encrypted key into your Hyper Protect Crypto Services service instance.



* Learn more about [using your root key to protect data at rest](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-envelope-encryptionenvelope-encryption).
* Deploy your root key across [supported cloud services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-integrate-servicesintegrate-services).
* Learn more about the [key management service API](https://cloud.ibm.com/apidocs/hs-crypto).
Then, you must [open the IBM Cloud Activity Tracker UI](https://cloud.ibm.com/docs/atracker?topic=atracker-launchlaunch_cloud_ui).





 Analyzing events 



 Action service_name.instance.delete 

When a service instance is deleted, consider the following information:



* Other actions are automatically triggered to clean up IAM permissions. These actions remove policies that are configured for users and service IDs in the account to work with the service instance.
* The initiator of these actions is an IBM service ID.



When the service instance that is deleted does not have IAM policies configured for users and service IDs, the events that are automatically generated for any of these resources report an outcome offailure with a 404 outcome code. The following sample shows the events that are generated when a service instance that does not have policies configured in the account is deleted:

Apr 30 09:04:16 cloudcerts: delete instance Certificate Manager-v1
Apr 30 09:41:20 IAM Access Management: delete policy -failure
Apr 30 09:41:20 IAM Access Management: delete policy -failure
To delete the watsonx.data instance, see [Deleting watsonx.data instance](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-delete_lh).
* How can I manage IAM access for watsonx.data?

IBM Cloud® Identity and Access Management (IAM) controls access to watsonx.data service instances for users in your account. Every user that accesses the watsonx.data service in your account must be assigned an access policy with an IAM role. For more information about IAM access for watsonx.data, see [Managing IAM access for watsonx.data](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-iam).
* How can I add and remove the users?

To add or remove users in a component, see [Managing user access](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-manage_access).
* How is the access control for users provided?

To provide access control for users to restrict unauthorized access, see [Managing data policy rules](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-data_policy).



Developer tools App Configuration



* How to create an App Configuration instance?



1. Log in to your IBM Cloud account.
2. In the IBM Cloud catalog, search App Configuration and select App Configuration. The service configuration screen opens.
3. In the Create tab, select the location that represents the geographic area (Region) where you want to provision your instance.
4. Select a Pricing plan.
5. Configure your resource by providing a Service name for your instance, or use the preset name.
6. Select a Resource group.
7. Optional: Add Tags to help you to identify and organize the instance in your account. If your tags are billing related, consider writing tags as key: value pairs to help group-related tags, such as costctr: 124.
8.
ibmcloud is instance-delete $vsi

The status of the instance changes to deleting immediately, but it still appears in a list query result. The deletion of an instance can take up to 30 minutes.

You can request other subnet resources to be deleted in parallel while you wait for the instance to be deleted. However, the subnet cannot be deleted until the instance and all other resources in the subnet no longer appear in the list query results.

If a secondary network interface exists in the subnet you are trying to delete, you must delete the instance. A network interface cannot be deleted from the instance without deleting the instance.





 Delete the subnet 

After all the resources inside the subnet were deleted, which means that they are not returned in a list query result, run the following command to delete the subnet:

ibmcloud is subnet-delete $subnet

The status of the subnet changes to deleting immediately, but it might take a few minutes until the subnet is deleted and no longer appears in the list query results.







 Step 3: Delete all public gateways in the VPC, if any 

To list all public gateways in your account, run the following command:

ibmcloud is public-gateways

For each public gateway in the VPC you want to delete, run the following command to delete the public gateway, where $gateway is the public gateway ID.

ibmcloud is public-gateway-delete $gateway





 Step 4: Delete the VPC 

After all subnets and public gateways in the VPC are deleted, run the following command to delete the VPC, where $vpc is the ID of the VPC you are deleting.

ibmcloud is vpc-delete $vpc

The status of the VPC changes to deleting immediately, but it might take a few minutes until the VPC is deleted and no longer appears in the list query results.







 Deleting a VPC by using the REST APIs
The following sections provide some example API calls that you can run to delete a VPC.



 Step 1: Find all subnets in the VPC that you want to delete 

Before a VPC can be deleted, each of its subnets must be deleted. Get the ID of the VPC that you want to delete by running the following command and looking at the id value:

Add | json_pp or | jq after the curl command to get a readable JSON string.

curl -X GET "$vpc_api_endpoint/v1/vpcs?version=$version&generation=2" -H "Authorization:$iam_token"

Save the ID of the VPC in a variable so you can use it later, for example:

vpc="0738-3524fef5-da35-4622-bf9a-31614964649d"

To get the list of all subnets in your account, run the following command:

curl -X GET "$vpc_api_endpoint/v1/subnets?version=$version&generation=2" 
-H "Authorization:$iam_token"

Look at the vpc value to determine the subnets that need to be deleted. Save the ID of the subnet in a variable for later use, for example:

subnet="0738-d31ce469-9b0f-44e1-87ce-0fc77d8b0e53"

If the VPC you want to delete has multiple subnets, repeat the steps to delete each subnet.





 Step 2: Delete each subnet in the VPC 



 Delete all VPN gateways in the subnet, if any 

To list all VPN gateways in your account, run the following command:

curl -X GET "$rias_endpoint/v1/vpn_gateways?version=$version&generation=2" -H "Authorization:$iam_token"

Run the following command for each VPN gateway in the subnet that you want to delete, where $vpnid is the ID of the VPN gateway.
Alternatively, you can click the row containing the CIS instance on the resource list main page and copy the GUID for the service instance ID.
* Does CIS compress resources?

Yes, CIS applies "gzip" and "brotli" compression to some types of content. CIS also compresses items based on the browser's UserAgent to speed up page loading time.

If you're already using gzip CIS honors your gzip settings as long as you're passing the details in a header from your web server for the files.

CIS only supports the content type "gzip" towards your origin server and can also only deliver content either gzip-compressed, brotli-compressed, or not compressed.

CIS's reverse proxy is also able to convert between compressed formats and uncompressed formats, meaning that it can pull content from a customer's origin server via gzip and serve it to clients uncompressed (or vice versa). This is done independently of caching.

The Accept-Encoding header is not respected and is removed.



Content Delivery Network (CDN)



* How does the CDN edge server retrieve content from the origin server?

 How does the CDN edge server retrieve content from the origin server? 



* For the Server type of origin, the CDN keeps the origin path in the URL. For example, if you add origin origin.example.com in path /example/, when a user opens the CDN URL cdn.example.com/example/, the CDN edge server retrieves the content from origin.example.com/example/.
* For the Object Storage type of origin, the CDN makes a URL transformation. For example, if object storage origin s3-example.object-storage.com with bucket name xyz-bucket-name is added in path /example-cos/, when a user opens the CDN URL cdn.example.com/example-cos/, the CDN edge server retrieves the content from s3-example.object-storage.com/xyz-bucket-name/.



* What's the difference between the origin on the Settings page and the origins on the Origins page?