vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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-command-options-origin-certificates" "> --><-- <section "id="section-command-example-origin-certificates" "> --> Examples List all origin certificates for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis origin-certificates 31984fea73a15b45779fa0df4ef62f9b -i cis-demo --output JSON
<-- </section "id="section-command-example-origin-certificates" "> --><-- </section "id="section-origin-certificates" "> --><-- <section "id="section-origin-certificate-create" "> --> ibmcloud cis origin-certificate-create Create a CIS-signed certificate. ibmcloud cis origin-certificate-create DNS_DOMAIN_ID --request-type REQUEST_TYPE] --hostnames HOST_NAME1] --hostnames HOST_NAME2] --requested-validity DAYS] --csr CSR] --instance INSTANCE_NAME] --output FORMAT]
ibmcloud cis origin-certificate-create DNS_DOMAIN_ID (--json @JSON_FILE | JSON_STRING) -i, --instance INSTANCE] --output FORMAT]
Deprecated] ibmcloud cis origin-certificate-create DNS_DOMAIN_ID --json-str JSON_STR -i, --instance INSTANCE] --output FORMAT]
Deprecated] ibmcloud cis origin-certificate-create DNS_DOMAIN_ID --json-file JSON_FILE -i, --instance INSTANCE] --output FORMAT] ! !!!!!!
<-- <section "id="section-command-options-origin-certificate-create" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain.
A pipeline cannot exist outside of a toolchain. If you delete a toolchain, all of the pipelines that are associated with the toolchain are also deleted. If you plan to delete an entire toolchain, you do not need to delete each pipeline individually. Instead, go to the "Modifying and deleting toolchains and tool integrations" section, and follow the steps to delete a toolchain.





 Classic pipelines 

Classic pipeline stages might include personal data such as credentials in the form of environment properties, and a pipeline definition that shows the current state of the pipeline. Stages might also include scripts inside jobs that you want to modify or delete, and artifacts and logs for the most recent pipeline runs that you want to export. Use the Configure Stage or Delete Stage actions to modify or delete a stage. Use the Download action to export artifacts or logs from a stage.

Zoom

![Stages menu](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/pipeline_stages.png)

Figure 1. Stages menu



 Modifying a Classic pipeline stage 

To modify a pipeline stage:



1. On the Pipeline page, click the Settings icon.
2. Click Configure Stage.
3. On the ENVIRONMENT PROPERTIES tab, edit or delete properties.
4. Modify a job script within the pipeline stage. Select the job and change the values that are part of the Build, Deploy, or Test Configuration.

Zoom

![Modify job script](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/job_script.png)

Figure 2. Modify job script
5. Delete a job from the pipeline stage.
To delete an alert policy by using the CLI, run the following command:

ibmcloud cis alert-policy delete POLICY_ID [-i, --instance INSTANCE] [-f, --force]

Where:



* POLICY_ID is the id of alert policy.
* -f, --force attempts to delete alert policy without prompting for confirmation.
* -i, --instance value is the instance name or ID.









 Creating an alert policy by using the API 

To create an email alert, take the following steps:



1. Log in to your IBM Cloud account.
2. Get a token.
3. Using that token, run one of the following commands:



* DDoS attack layer 7
* Pool toggle alert
* Security (WAF) alert
* Advanced security (WAF) alert







 Alert commands 



 DDoS attack layer 7 command 

curl -X POST https://api.cis.cloud.ibm.com/v1/:crn/alerting/policies -H 'content-type: application/json' -H 'x-auth-user-token: Bearer xxxxxx' -d '{"name":"Example Policy","enabled":true,"alert_type":"dos_attack_l7","mechanisms":{"email":[{"id":"cistestemail@ibm.com"}],"webhooks":[]}}'

Where:



* -d is the array of attributes that are required to create the alert.



* name is the name of the alert.
* enabled is the state of the alert (one of true, false).
* alert_type is the type of the alert (one of dos_attack_l7, load_balancing_pool_enablement_alert, clickhouse_alert_fw_anomaly, clickhouse_alert_fw_ent_anomaly, dedicated_ssl_certificate_event_type, universal_ssl_event_type, or load_balancing_health_alert).
* mechanisms are at least one of email, webhooks.
* UI
* CLI
* API







 Removing trusted profiles 

When you remove trusted profiles, compute resources and federated users are unlinked from the profile and can no longer apply the trusted profile identity.

To remove trusted profiles, you must be assigned the administrator or operator role within the account, or on the IAM Identity Service.

When you remove trusted profiles, you revoke all active sessions. Users are immediately logged out and the removed profiles are no longer available to connect to the target account. API calls that use access tokens might be successful until the access token expires.



 Removing trusted profiles in the console 



1. To see the full list of trusted profiles in your account, go to Manage > Access (IAM) in the IBM Cloud console, and select Trusted profiles.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/action-menu-icon.svg) next to the trusted profile you want to remove, and select Remove.







 Removing trusted profiles by using the CLI 

You can remove a trusted profile from your account by using the CLI. For more information, see the [IBM Cloud CLI](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases).



1. Log in, and select the account.

ibmcloud login
2. Check the list of trusted profiles for the current account and select the one that you want to remove. The following command shows the list of trusted profiles for your IBM Cloud account:

ibmcloud iam trusted-profiles
3. Remove the trusted profile from your account by running the following command. Specify the ID or the name of the trusted profile that you would like to remove.

ibmcloud iam trusted-profile-delete <IDorName>



For example, the following command removes a trusted profile that is named Test trusted profile.
resource "ibm_sm_public_certificate_configuration_ca_lets_encrypt" "my_lets_encrypt_config" {
instance_id = local.instance_id
region = local.region
name = "lets-encrypt-config"
lets_encrypt_environment = "production"
lets_encrypt_private_key = var.my_lets_encrypt_private_ley
}





 Deleting a certificate authority configuration in the UI 

If you no longer need a configuration, you can delete it by using the Secrets Manager UI.

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



1. In the console, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/icon_hamburger.svg)> Resource List.
2. From the list of services, select your instance of Secrets Manager.
3. In the Secrets engines page, click the Public certificates tab.
4. Use the Certificate authorities table to view the configurations in your instance.
5. In the row for the configuration that you want to delete, click the Actions menu ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/actions-icon-vertical.svg)> Delete.
6. Enter the name of the configuration to confirm its deletion.
7. Click Delete.







 Deleting a certificate authority configuration with the API 

You can delete configurations by calling the Secrets Manager API.

The following example shows a query that you can use to remove a certificate authority configuration from your instance.
Getting CIS running with a new subdomain 

Follow these steps to practice using CIS with a subdomain or CNAME. This example uses the GoDaddy domain registrar. Your case might be different, depending on which registrar you use.



1.  Deploy a CIS instance by using the IBM Cloud console or API.

It is recommended that you mirror the name of your CIS instance with the domain or subdomain.
2.  Click Let’s get started.
3.  Enter the subdomain in the Domain name field and click Connect and continue.
4.  For new subdomains click Next Step, for existing subdomains click Import records.
5.  Make note the New NS records for entry into the GoDaddy DNS Management system.
6.  Log in to GoDaddy domain Registrar.
7.  Navigate to the DNS Management page for the candidate CIS domain. IBM Cloud® must be updated through the API.
8.  Click ADD to create an NS Host record for each name server entry provided from CIS.
9.  Set up a DNS record with the supplied CIS NS Records



*  Type Nameserver
*  Host subdomain (the name of the subdomain, for example, subdomain.example.com)
*  Points to ns004.name.cloud.ibm.com
*  TTL ½ hour



10. The DNS Management page now reflects the two new NS records for the subdomain.
11. Go back to the IBM Cloud Internet Services instance.
12. After the NS Records are DNS propagated, it is reflected in the DNS tools, and you are ready to proceed.
13. With completed NS propagation, click Check name servers.
14. CIS starts checking NS configuration for the subdomain and might be in a Pending State.

Any typographical errors in can produce a "silent" failure. If your subdomain is in the pending state for more than 30 minutes, you might have an error.



Upon successful subdomain name server and NS record confirmation, the CIS instance reports Active. Customers are now ready to start configuring the service and routing traffic to their services.
! ! ! ! ! ! !
<-- <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. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-delete-ratelimit-rule-options" "> --><-- <section "id="section-delete-ratelimit-rule-examples" "> --> Examples Delete rate limiting rule 372e67954025e0ba6aaa6d586b9e0b60. ibmcloud cis ratelimit-rule-delete 31984fea73a15b45779fa0df4ef62f9b 372e67954025e0ba6aaa6d586b9e0b60 -i "cis-demo"
<-- </section "id="section-delete-ratelimit-rule-examples" "> --><-- </section "id="section-delete-ratelimit-rule" "> --><-- </section "id="section-ratelimit" "> --><-- <section "id="section-resource-instance" "> --> Resource instance Manipulate CIS Service instances by using the following instance commands.<-- <section "id="section-list-cis-service-instances" "> --> ibmcloud cis instances List all CIS service instances. ibmcloud cis instances --output FORMAT] ! ! ! ! ! !
apiconnect.configured_gateway_service_clearCatalogScope.delete Clear the Configured Gateway Service objects 
 apiconnect.configured_gateway_service_delCatalogScope.delete Delete the Configured Gateway Service object by name or ID 
 apiconnect.configured_gateway_service_createSpaceScope.create Create a Configured Gateway Service object 
 apiconnect.configured_gateway_service_clearSpaceScope.delete Clear the Configured Gateway Service objects 
 apiconnect.configured_gateway_service_delSpaceScope.delete Delete the Configured Gateway Service object by name or ID 
 apiconnect.configured_catalog_user_registry_create.create Create a Configured Catalog User Registry object 
 apiconnect.configured_catalog_user_registry_del.delete Delete the Configured Catalog User Registry object by name or ID 
 apiconnect.configured_catalog_user_registry_search.create Search for users in the catalog user registry 
 apiconnect.configured_api_user_registry_createCatalogScope.create Create a Configured API User Registry object 
 apiconnect.configured_api_user_registry_clearCatalogScope.delete Clear the Configured API User Registry objects 
 apiconnect.configured_api_user_registry_delCatalogScope.delete Delete the Configured API User Registry object by name or ID 
 apiconnect.configured_api_user_registry_createSpaceScope.create Create a Configured API User Registry object 
 apiconnect.configured_api_user_registry_clearSpaceScope.delete Clear the Configured API User Registry objects 
 apiconnect.configured_api_user_registry_delSpaceScope.delete Delete the Configured API User Registry object by name or ID 
 apiconnect.configured_tls_client_profile_createCatalogScope.create Create a Configured TLS Client Profile object 
 apiconnect.configured_tls_client_profile_clearAllCatalogScope.delete Clear all Configured TLS Client Profile objects in all collections 
 apiconnect.configured_tls_client_profile_clearCatalogScope.delete Clear the Configured TLS Client Profile objects
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/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.

To authorize a source service to access a target service, run the ibmcloud iam authorization-policy-create command.

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.
Uninstalling through IBM Cloud Catalog 

If you no longer need to use Data Security Broker, you can uninstall all the workloads that are associated with the Data Security Broker using the [IBM Cloud Schematics workspace](https://cloud.ibm.com/schematics/workspaces).



  Pre-requisite 

The user must be aware of the workspace name which is provided during the Data Security Broker Manager and Data Security Broker Shield installation process.





  Uninstalling Data Security Broker Manager 

Log into IBM Cloud Schematics workspace and follow the steps below to uninstall the Data Security Broker Manager:



1.  Search for the workspace name that you provided during the Data Security Broker Manager install and click on the workspace to open it.

Zoom

![IBM Schematics Workspace](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/schematics_workspace.svg)

IBM Schematics Workspace
2.  Select Actions -> Destroy Resources to destroy the workloads associated with the Data Security Broker Manager.

Zoom

![Uninstall Data Security Broker Manager](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/uninstall_dsb_manager.svg)

Uninstall Data Security Broker Manager
3.  Follow the same process for the Data Security Broker Shield to uninstall the workloads associated with the Data Security Broker Shield. Remember to work with the correct workspace name, which is provided during the Data Security Broker Shield install.



Once you uninstall the Data Security Broker Manager and Data Security Broker Shield workloads, you can see that the pods are being terminated and you can monitor the successfull uninstall operation through the logs.
To learn how IAM roles map to Hyper Protect Crypto Services actions, check out [Service access roles](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-accessservice-access-roles).
2. Copy the ID of the key that you want to unset or deauthorize for deletion.
3. Remove an existing authorization to delete the key.

curl -X POST 
'https://api.<region>.hs-crypto.cloud.ibm.com:<port>/api/v2/keys/<key_ID>/actions/setKeyForDeletion' 
-H 'accept: application/vnd.ibm.kms.key_action+json' 
-H 'authorization: Bearer <IAM_token>' 
-H 'bluemix-instance: <instance_ID>' 
-H 'content-type: application/vnd.ibm.kms.key_action+json'

Replace the variables in the example request according to the following table.



Table 2. Describes the variables needed to unset a key for deletion

 Variable Description 

 region Required. The region abbreviation, such as us-south or eu-de, that represents the geographic area where your Hyper Protect Crypto Services instance resides. For more information, see [Regional service endpoints](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-regionsservice-endpoints). 
 key_ID Required. The unique identifier for the root key that you want to delete. 
 IAM_token Required. Your IBM Cloud access token. Include the full contents of the IAM token, including the Bearer value, in the cURL request. For more information, see [Retrieving an access token](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-retrieve-access-token). 
 instance_ID Required. The unique identifier that is assigned to your Hyper Protect Crypto Services instance.
Activating the domain before migrating from CIS can cause your domain to changed to a [Moved state](https://cloud.ibm.com/docs/cis?topic=cis-domain-moved-status).
* I added a user to my account and gave that user permission to manage Internet Services instance(s). Why is that user facing authentication issues?

It's possible that you did not assign "service access roles" to the user. Note that there are two separate sets of roles:



* Platform access
* Service access



You need platform access roles to create and manage service instances, while service access roles perform service-specific operations on service instances. In the console, these settings can be updated by selecting Manage > Security > Identity and Access.
* Why is my domain in Pending state? How do I activate it?

When you add a domain to CIS, we give you a couple of name servers to configure at your registrar (or at your DNS provider, if you are adding a subdomain). The domain or subdomain remains in pending state until you configure the name servers correctly. Make sure you add both the name servers to your registrar or DNS provider. We periodically scan the public DNS system to check whether the name servers have been configured as instructed. As soon as we are able to verify the name server change (which can take up to 24 hours), we activate your domain. You can submit a request to recheck name servers by clicking on Recheck name servers in the overview page.
* Who is the registrar for my domain?

Consult [https://whois.icann.org/](https://whois.icann.org/) for this information.

You must have the administrator privilege to edit your domain's configuration at the registrar in order to update or add the name servers provided for your domain when you add it to CIS. If you don't know who the registrar is for the domain you're trying to add to CIS, it is unlikely you have the permission to update your domain's configuration at the registrar. Work with the owner of the domain in your organization to make the necessary changes.
This will also delete all of the artifacts associated with a node including your ledger data in persistent storage and the keys that are stored as secrets. Deleting a peer will not, however, delete any smart contract pods associated with it. These must be deleted separately. Deleting a component is usually achieved by logging onto the console where a component was created or installed, clicking on the component and finding the related trash can icon. You will typically be prompted to type the name of the component and to confirm your decision. You can also delete nodes by using the IBM Blockchain Platform APIs.

However, there are cases in which this type of deletion will not be successful. For example, occasionally when a node fails to deploy it will not be possible to delete it using the console. The same can be true if the console loses connection with the cluster for some reason.

In these cases, it will be necessary to use the Kubernetes dashboard or delete the node or relevant pods manually. If you attempt to delete pods that contain deployments such as peers, CAs, or ordering nodes, the pod will automatically restart and not be permanently deleted.

Because smart contracts installed on a 2.x peer are deployed into their own pods and not directly into the peer container, they will not be deleted when a peer is deleted. They will have to be deleted either using the UI of your cluster or by issuing kubectl commands. Smart contracts installed on a v1.4.x peer will be deleted when the peer is deleted.

Because deployments are organized in Kubernetes by their "namespace", you need to know your Kubernetes cluster namespace before you can delete components using the kubectl CLI. From the console, open any CA node and click the Info and Usage icon. View the value of the API URL. For example: https://nf85a2a-soorg10524.ibpv2-cluster.us-south.containers.appdomain.cloud:7054. The namespace is the first part of the URL beginning with the letter n and followed by a random string of six alphanumeric characters.
Canceling bare metal servers 



  Citrix Hypervisor 

If you want to cancel one or more of your Citrix DaaS for IBM Cloud®bare metal servers, complete the following steps.



1.  Log in to the [IBM Cloud® console](https://cloud.ibm.com/login) by using your unique credentials.
2.  Navigate to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/icons/icon_hamburger.svg) > Classic Infrastructure > Device List.
3.  In the Actions menu of the bare metal server that you want to cancel, select Cancel Device.







  VMware ESXi 

When you add or delete a service or infrastructure component, you must wait until the modification is complete before you can add or delete another service or infrastructure component.

You can cancel one or more ESXi hosts from your cluster. You should have three hosts with NFS storage.



1.  Log in to the [IBM Cloud® console](https://cloud.ibm.com/login) by using your unique credentials.
2.  Navigate to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/icons/icon_hamburger.svg) > VMware > Resources.
3.  Select your vCenter Instance.
4.  Click the Infrastructure tab.
5.  Select your cluster.
6.  Select the ESXi hosts you would like to delete.
7.  Click Delete.