vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Since the old Default Contract Configuration file needs to be deleted from your environment before the new one is used, use the API [Delete configuration](/apidocs/discoverydelete-a-configuration){: external} to delete the current Default Contract Configuration associated with any of your collections. Also delete any configurations based on the old Default Contract Configuration.
1. Now you can use the new Default Contract Configuration file. For each collection using one of those configurations, create a new collection. Apply the new Default Contract Configuration or create a new custom configuration based on the new Default Contract Configuration using the notes you made in step 2.
1. Upload the files previously ingested to the original collections.
1. Delete the old collections.





 15 August 2018 

New query operators : Two new query operators are available. Exists (:) can be used to return all results where the specified field exists. Does not exist (!) can be used to return all results that do not include the specified field. See [Query operators](https://cloud.ibm.com/docs/discovery?topic=discovery-query-operators) for more information.





 2 August 2018 

New multiple language support for connecting and syncing to Box, Salesforce, and SharePoint Online : IBM Watson™ Discovery now supports Arabic, English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish language collections when connecting and syncing to Box, Salesforce, and SharePoint Online with the Discovery tooling.





 31 July 2018 

New Pricing structure : Beginning August 1, 2018, IBM Watson™ Discovery has a new pricing structure. It features a simpler pricing model (document hours are no longer part of the calculation) and tiered pricing for IBM Watson™ Discovery News queries. In addition, the Standard plan is retired, and the Lite plan has reduced document and Discovery News query limits. The pricing changes require no action by current Discovery News users. For details, see [Discovery Pricing Plans](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans).

Update to version string : The version date of the API is updated to 2018-08-01.
1 June 2022 

As of 1 June 2022, the Security Insights component of Security and Compliance Center is deprecated and support was removed. A replacement has not yet been found. Please note, this discontinuation does not affect the other features in Security and Compliance Center. If you have comments, questions, or concerns, please reach out to Jessica Doherty by email at jpbonner@us.ibm.com.





 27 May 2022 

Profiles are constantly expanding and are not an exhaustive list of all the controls that might be required for every organization. Users can validate the available goals and determine where a need to supplement their workloads with other security and compliance measures exists.

Now available: IBM Cloud Security Best Practices Controls profile
: Released today, the IBM Cloud Security Best Practices profile is a collection of goals that can help an organization to ensure that they are adhering to best practices as defined by IBM Cloud security.

Now available: The IBM Cloud Control Library profile
: As part of this release the IBM Cloud Best Practices Controls 1.0 profile was renamed to the IBM Cloud Control Library. The IBM Cloud Control Library is a profile that contains all the available controls and goals that are available for IBM Cloud. The library cannot be used to scan your resources directly, but you are able to create a custom profile from the library.

Now available: New version of the IBM Cloud for Financial Services profile
: Version 0.3.0 of the IBM Cloud for Financial Services profile is now available with new goals and controls. For more information, see the [IBM Cloud for Financial Services profile change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 13 May 2022 

New pricing plans available
: The Posture Management component of the Security and Compliance Center is now a paid component. For more information about how pricing works and the available plans, see [How does Security and Compliance Center calculate pricing?](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-scc-pricing)
Activity Tracker integration 

IBM® Db2® on Cloud deployments are integrated with Activity Tracker events in [IBM Cloud Activity Tracker with IBM Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started), so you can view service-level events.

Currently, Activity Tracker with IBM Log Analysis integration is available for Db2 on Cloud deployments in the regions according to the following table:



Table 1. Activity Tracker regions

 Deployment region Activity Tracker region 

 Dallas us-south 
 Washington us-east 
 Frankfurt eu-de 
 London eu-gb 
 Sydney au-syd 
 Tokyo jp-tok 





 Activity Tracker through Log Analysis 

After you provision the service, events are automatically forwarded from all of your Db2 on Cloud deployments in the same region.

The service can be provisioned from its [catalog page](https://cloud.ibm.com/catalog/services/logdnaat?callback=%2Fobserve%2Factivitytracker%2Fcreate) or from an existing [Observability Dashboard](https://cloud.ibm.com/observe/activitytracker).

The Activity Tracker with Log Analysis service has a Lite plan that is free to use, but it only offers streaming events. To take advantage of the tagging, export, retention, and other features, you need to use one of the [paid plans](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).



 Using the Log Analysis Activity Tracker 

You can access Activity Tracker with Log Analysis through the Observability tab of your deployment's Manage page. The Manage Activity Tracker button links to the main list of all Activity Tracker instances in your IBM Cloud account. Select the instance where you set your database logs to be forwarded. Click View Activity Tracker to view the events.

After the event activity is forwarded to the service, each event can be expanded to a detailed view by clicking the arrow to the left of the time stamp.
Available speeds are based on your provider's location. Direct Link Connect supports the following speeds: 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps. (Speeds of 25 Gbps, 40 Gbps, 50 Gbps, and 100 Gbps are available on 100G NNIs only.)

The routing option that you select determines the reachability of the resources in the selected location. If you select the Global routing option along with your location selections, the Region menu list displays all the regions that are globally available in the specific account. After selecting a region, you can select any VPC from the Available connections menu. If you select Local routing, then only the region that corresponds to the selected location is available to select. When selected, the VPCs available in the local region for your account are shown.
7. In the Billing section, select Metered or Unmetered. Metered pricing is paying only for what you use; unmetered is unlimited access, for a predicable, monthly fee. Keep in mind that pricing is determined by the routing option and speed that you choose.

Unmetered billing is only available for specific speeds.
8. In the BGP section, complete the following information:



* Select the IBM cross-connect router for the Direct Link connection. The number of direct links associated with your account for each router is shown next to the router name.
* Select a BGP peering subnet for the Direct Link connection. There are two choices for BGP subnets:



* Select Manual-select IP to specify two of your own IP addresses (in CIDR format) from the ranges 10.254.0.0/16, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16, or Public (a public IP address that you own). Manual-select is useful when trying to avoid conflicts with an existing subnet that is in use.
* Select Auto-select IP for IBM to assign an IP address from IP range 169.254.0.0/16.
8 CLI Delete the authorization policy between COS and KP 
 9 CLI Delete the COS and KP instances 



These commands show COS and Key Protect service plans. The ibmcloud resource service-instance-create command requires a service plan name and a location, which is in the catalog.

 show the catalog offerings for cloud object storage (COS) and Key Protect
$ ibmcloud catalog service cloud-object-storage

$ ibmcloud catalog service kms

The example covers multiple steps and should be performed in consultation with the summary provided.

 create a Cloud Object Storage (COS) instance
 "lite" is the pricing plan and "global" is the region
$ COS_NAME=my-cos-1

$ ibmcloud resource service-instance-create $COS_NAME cloud-object-storage lite global

Creating service instance my-cos-1 in resource group Default of account <account name> as <email address>...
OK
Service instance my-cos-1 was created.
Name: my-cos-1
ID: crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8::
GUID: 4b636e74-f3ca-40bb-80b8-3bd21801ccb8
Location: global
State: active
Type: service_instance
Sub Type:
Allow Cleanup: false
Locked: false
Created at: 2020-06-15T16:03:39Z
Updated at: 2020-06-15T16:03:39Z
Last Operation: Status create succeeded Message Completed create instance operation

 capture the COS instance id (GUID)
$ COS_INSTANCE_ID=4b636e74-f3ca-40bb-80b8-3bd21801ccb8

 create a Key Management Service (KMS) service instance
Log in to the [IBM Cloud account](https://cloud.ibm.com/login) where you created your Kubernetes cluster.
2. Click Catalog. A list of IBM Cloud services opens.
3. To filter the list of services that is displayed, select the Logging and Monitoring category.
4. Click IBM Log Analysis. The Observability dashboard opens.
5. Select Create instance.
6. Enter a name for the service instance and a location.
7. Select the resource group that your cluster is in. By default, the Default resource group is set for you.
8. Choose a service plan for your service instance. By default, the Lite plan is selected for you. For more information about other service plans, see [Pricing plans](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).
9. To provision the IBM Log Analysis service in the IBM Cloud resource group where you are logged in, click Create. The Observability dashboard opens and shows the details for your service.



To provision an instance through the CLI, see [Provisioning an instance through the IBM Cloud CLI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provisionprovision_cli).





 Step 2. Get the ingestion key 

Complete the following steps to get the ingestion key:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in, the IBM Cloud UI opens.
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/icon_hamburger.svg) > Observability to access the Observability dashboard.
3. Select Logging.
Subscribing to Object Storage events 

With this tutorial, you can learn how to subscribe to Object Storage events by using the IBM Cloud® Code Engine CLI.

Oftentimes in distributed environments you want your applications or jobs to react to messages (events) that are generated from other components, which are usually called event producers. With Code Engine, your applications or jobs can receive events of interest by subscribing to event producers. Event information is received as POST HTTP requests for applications and as environment variables for jobs.

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



All Code Engine users are required to have a Pay-as-you-Go account. Tutorials might incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage. For more information, see [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).



 Step 1: Determine your Object Storage bucket and region 

The Object Storage event producer generates events based on operations on objects in IBM Cloud Object Storage buckets.



1. Install the Object Storage plug-in CLI.

ibmcloud plugin install cloud-object-storage
2. Create an Object Storage resource instance. For example, create an Object Storage resource that is named mycloud-object-storage that uses the IBM Cloud Lite service plan.

ibmcloud resource service-instance-create mycloud-object-storage cloud-object-storage lite global
3. Display the details of the Object Storage resource instance that you created. Use the details to get the CRN (Cloud Resource Name) from your Object Storage instance. The CRN identifies which Object Storage instance you want to use. The CRN is the value of the ID field in the output of the ibmcloud resource service-instance COS_INSTANCE_NAME command.
Language model customization is available for both previous- and next-generation models, though it works differently for the two types of models.
* [Custom acoustic models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-acoustic) let you adapt a base model for the acoustic characteristics of your environment and speakers. Custom acoustic models improve the service's ability to recognize speech with distinctive acoustic characteristics. Acoustic model customization is available only for previous-generation models.
* [Grammars](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-grammars) let you restrict the phrases that the service can recognize to those defined in a grammar's rules. By limiting the search space for valid strings, the service can deliver results faster and more accurately. Grammars are created for and used with custom language models. The service generally supports grammars for languages and models for which it supports language model customization.



You can use a custom language model (with or without a grammar), a custom acoustic model, or both for speech recognition with any of the service's interfaces.



* For more information about customization and an overview of its capabilities, see [Understanding customization](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-customization).
* For more information about which languages support customization, see [Language support for customization](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-support).



IBM Cloud

You must have the Plus, Standard, or Premium pricing plan to use language model or acoustic model customization. Users of the Lite plan cannot use the customization interface, but they can upgrade to the Plus plan to gain access to customization. For more information, see the [Pricing FAQs](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-faq-pricing).





 Using software development kits 

SDKs are available for the Speech to Text service to simplify the development of speech applications.
: Upgraded to [GitLab 11.11.8](https://about.gitlab.com/releases/2019/08/12/critical-security-release-gitlab-12-dot-1-dot-6-released/).





 5 September 2019 

Develop and test microservices with Kubernetes and Helm template doesn't support API keys that aren't bound to a specific account.
: When a Delivery Pipeline stage attempts to run the ibmcloud login command, it fails because no account is specified. To work around this limitation, in the Delivery Pipeline within the Develop and test microservices with Kubernetes and Helm template, create a pipeline property that is called ACCOUNTID and add the account that you want to use with the pipeline. In each pipeline stage, add -c $ACCOUNTID to each instance of the ibmcloud login command.





 4 September 2019 

Git Repos and Issue Tracking
: Upgraded to [GitLab 11.10.8](https://about.gitlab.com/releases/2019/07/03/security-release-gitlab-12-dot-0-dot-3-released/).





 3 September 2019 

Delivery Pipeline events are not translated.
: Events that are triggered by the Delivery Pipeline send Slack messages. Since Slack APIs do not support multi-language message payload, these Slack messages cannot be translated.





 28 August 2019 

Git Repos and Issue Tracking
: Upgraded to [GitLab 11.9.12](https://about.gitlab.com/releases/2019/06/03/security-release-gitlab-11-dot-11-dot-1-released/).





 24 June 2019 

Stricter enforcement of service plans
: A toolchain must be linked to a CD service in order for the Delivery Pipeline run.
: Users of the CD service are automatically added to the list of "Authorized Users."
: If you are using the Lite plan with more than five authorized users, the pipelines no longer run, pushes to Git Repos are unavailable, and DevOps Insights is unavailable.
Simulating device data 

IBM Watson® IoT Platform is deprecated. As of 30 April 2023, only subscribers on paid plans will be able to deploy new instances. The service will be fully withdrawn on 1 December 2023. Any instances that still exist on 1 December 2023 will be deleted. For more information, see [the deprecation details](https://cloud.ibm.com/docs/IoT?topic=IoT-deprecation).

This IBM Cloud® documentation collection pertains to the IBM Watson® IoT Platform Lite pricing plan and includes basic getting started information, API references, and general troubleshooting information. For the full Watson IoT Platform feature documentation, see the [Watson IoT Platform product documentation ![External link icon](https://cloud.ibm.com/docs-content/v1/content/dc2670e9228a1dbe562d3d2c7ee63f7a48ba27c3/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/overview/overview.html) on IBM Knowledge Center. More information about the various plans can be found in [Watson IoT Platform service plans](https://cloud.ibm.com/docs/services/IoT?topic=IoT-plans_overviewplans_overview).

Use the IBM Watson® IoT Platform device simulator to set up simulated events for devices to learn about, test, and demonstrate fully functioning Watson IoT Platform features without having to register and connect actual devices.

By using the device simulator, you can create simulated devices for existing device types or create new device types and devices. Each simulated device can use unique event details, but you can also create a default configuration that is applied to all devices.



 Before you begin 

Enable device simulation for your user ID.



1. Log in to Watson IoT Platform.
2. From the main navigation pane, select Settings.
3. In the Data and Devices section, activate the device simulator.
* Select a geography, followed by a market, type, site, and routing option.

Local and global routing options are supported. When you select a routing option, the location details with reachable sites are displayed.

* Choose a connection speed. The speeds supported for the Direct Link Dedicated offering are 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps.

Speeds greater than 1 Gbps require 10 Gbps service from the client's carrier and equipment. If you intend to upgrade the speed for this gateway, select 2 Gbps to start with; otherwise, you will not be able to upgrade to a higher speed on this gateway.
* Choose an IBM cross-connect router, if available.



The routing option that you select determines the reachability of the resources in the selected location. If you select the Global routing option along with your location selections, the Region menu list displays all the regions that are globally available in the specific account. After selecting a region, you can select any VPC from the Available connections menu. If you select Local routing, then only the region that corresponds to the selected location is available to select. When selected, the VPCs available in the local region for your account are shown.
7. In the Billing section, select Metered or Unmetered. Metered pricing is paying only for what you use. Unmetered is unlimited access, for a predicable, monthly fee.
8. In the BGP section, complete the following information:



* Select the IBM cross-connect router for the Direct Link connection. The number of direct links associated with your account for each router is shown next to the router name.
* Select a BGP peering subnet for the Direct Link connection. There are two choices for BGP subnets:



* Select Manual-select IP to specify two of your own IP addresses (in CIDR format) from the ranges 10.254.0.0/16, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16, or Public (a public IP address that you own). Manual-select is useful when trying to avoid conflicts with an existing subnet that is in use.
Cloud Identity and Access Management authentication and authorization for Watson IoT Platform (Beta) 

IBM Watson® IoT Platform is deprecated. As of 30 April 2023, only subscribers on paid plans will be able to deploy new instances. The service will be fully withdrawn on 1 December 2023. Any instances that still exist on 1 December 2023 will be deleted. For more information, see [the deprecation details](https://cloud.ibm.com/docs/IoT?topic=IoT-deprecation).

This IBM Cloud® documentation collection pertains to the IBM Watson® IoT Platform Lite pricing plan and includes basic getting started information, API references, and general troubleshooting information. For the full Watson IoT Platform feature documentation, see the [Watson IoT Platform product documentation ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/overview/overview.html) on IBM Knowledge Center. More information about the various plans can be found in [Watson IoT Platform service plans](https://cloud.ibm.com/docs/services/IoT?topic=IoT-plans_overviewplans_overview).

IBM Watson® IoT Platform APIs support the authentication and authorization of users by using Cloud Identity and Access Management (IAM).

The IBM Cloud® Identity and Access Management authentication and authorization for Watson IoT Platform is available only as part of a limited beta program. Future updates might include changes that are incompatible with the current version of this feature.

Cloud Identity and Access Management is built into IBM Cloud and is used for authenticating and authorizing administrative and developer users that need to configure and manage their IBM services. Users who need access to the Watson IoT Platform dashboard are authenticated by using Cloud Identity and Access Management. The source of identity for Cloud Identity and Access Management can be registered IBMid users, or it can be a customer’s directory service that supports SAML.

Watson IoT Platform also supports authenticating users through App ID.