vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Make sure that the JSON file follows the structure as outlined in this command. Also ensure the location and the url endpoint are pointing to the same region when you create or update workspaces and actions. For more information about location and endpoint, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location).

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).

Syntax

ibmcloud schematics workspace new --file FILE_NAME --state STATE_FILE_PATH [--agent-id AGENT_ID] [--github-token GITHUB_TOKEN] [--output OUTPUT] [--json]

Command options



Schematics Workspaces create flags

 Flag Required / Optional Description 

 --file or -f Optional The relative path to a JSON file on your local machine that is used to configure your workspace. For more information about the sample JSON file with the details, see [JSON file create template](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencejson-file-create-template). 
 --state Optional The relative path to an existing Terraform state file on your local machine. To create the Terraform state file: <br>1. Show the content of an existing Terraform state file by using the [ibmcloud schematics state pull](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencestate-pull) command. <br>2. Copy the content of the state file from your command-line output in to a file on your local machine that is named terraform.tfstate. <br>3.
For more information, see the [Block Storage for VPC add-on change log](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog).

Reminder: VPC Gen 1 deprecation
: You can continue to use VPC Gen 1 resources only until 26 February 2021, when all service for VPC Gen 1 ends. On 01 March 2021, any remaining VPC Gen 1 worker nodes are automatically deleted. To ensure continued support, [create new VPC clusters on Generation 2 compute only](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=ui), and move your workloads from existing VPC Gen 1 clusters to VPC Gen 2 clusters.





 25 January 2021 

Istio add-on
: [Version 1.8.2 of the Istio managed add-on](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog182) is released.

New! Private service endpoint allowlists
: You can now control access to your private cloud service endpoint by [creating a subnet allowlist](https://cloud.ibm.com/docs/containers?topic=containers-access_clusterprivate-se-allowlist). Only authorized requests to your cluster master that originate from subnets in the allowlist are permitted through the cluster's private cloud service endpoint.

Private Kubernetes Ingress
: Added steps for [privately exposing apps with ALBs that run the Kubernetes Ingress image](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-setup).





 19 January 2021 

Ingress ALB change log
: Updated the [nginx-ingress build to 2424](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for the IBM Cloud Kubernetes Service Ingress image.

Master versions
* UI
* CLI
* API
* Terraform







 Displaying workspaces 

List the workspaces in your IBM Cloud® account and optionally, show the details for your workspace.

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).



 Before you begin 

Ensure the location and the url endpoint are pointing to the same region when you list the Schematics workspaces and actions. For more information about location and endpoint, see [Where is your information stored](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location)?





 Displaying the workspace through UI 



1. Log in to [IBM Cloud](https://cloud.ibm.com/).
2. Access Schematics > Workspaces > [workspace](https://cloud.ibm.com/schematics/workspaces).
3. Search with name for required workspace with specific to location selecting North America or Europe.





 Verifying workspace display 



1. Click your workspace that is listed in the [IBM Cloud console](https://cloud.ibm.com/schematics/workspaces) to view the results of the workspace details.









 Displaying the workspace through CLI 



1. List the workspaces in your IBM Cloud account and optionally, show the details for your workspace. For more configuration options when listing the workspace, see the [ibmcloud schematics workspace list command](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-list).

Syntax

ibmcloud schematics workspace list [--limit LIMIT] [--offset OFFSET] [--output] [--region] [--json]
ibmcloud resource service-instance-update <instance-name> --service-endpoints public

To migrate from public-and-private to private endpoints:

ibmcloud resource service-instance-update <instance-name> --service-endpoints private

Switching directly from public to private endpoints or from private to public endpoints is not supported. The switch disables all public endpoints and your applications loses access to the cluster. To avoid this, first enable both public and private endpoints, then reconfigure applications to use private endpoints, and finally switch to private only endpoints.

For example, to migrate directly from public to public-and-private endpoints:

First, enable both public and private endpoints:

ibmcloud resource service-instance-update <instance-name> --service-endpoints public-and-private

Next, create a new credential that contains private endpoints and a new API key, as follows:

ibmcloud resource service-key-create <private-key-name> <role> --instance-name <instance-name> --service-endpoint private

Then, update any applications that use the instance with the new endpoint details.

Finally, after applications are migrated to the private endpoints, run the following command to turn off the public endpoints:

ibmcloud resource service-instance-update <instance-name> --service-endpoints private





 Specifying an IP allowlist (deprecated) 

This feature is now deprecated, instead use context-based restrictions [Configuring CBR](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-restrict_accessconfiguring_cbr).

When you provision an instance of the Enterprise plan, select private endpoints and want to further restrict access to only known VSIs with specific VPCs, you can add an IP allowlist by using the CLI and appending as follows:

ibmcloud resource service-instance-create <instance-name> <plan-name> <region> --service-endpoints private -p '{"private_ip_allowlist":["CIDR1","CIDR2"]}' "
* Existing clusters with ALBs that run the custom IBM Ingress image continue to operate as-is.
* Support for the custom IBM Ingress image ended on 02 June 2021.
* You must move to the new Kubernetes Ingress by migrating any existing Ingress setups. Your existing ALBs and other Ingress resources are not automatically migrated to the new Kubernetes Ingress image.
* Any ALBs with the unsupported image continue to run, but are not supported by IBM.



When you [create a new ALB](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_create), [enable an ALB](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_configure) that was previously disabled, or [manually update(update-alb) an ALB], you can specify an image version for your ALB with the --version option. If you omit the --version option when you enable or update an existing ALB, the ALB runs the default version of the same image that the ALB previously ran; either the Kubernetes Ingress image or the IBM Cloud Kubernetes Service Ingress image.

Automatic updates only apply the default version. To specify a version other than the default, you must [disable automatic updates](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-manageautoupdate) by running the [ibmcloud ks ingress alb autoupdate disable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_autoupdate_disable) command.





 Viewing supported image versions 

To list the latest three versions that are supported for each type of image, run the following command.

ibmcloud ks ingress alb versions

Example output

Kubernetes Ingress versions
1.1.2_2507_iks (default)
1.2.1_2506_iks
You can check the status of the deployment by viewing the deployment history on the instance details page.
2. When the cluster is ready to use, its status changes to Available. The newly added cluster is enabled with vSphere High Availability (HA) and vSphere Distributed Resource Scheduler (DRS).



You cannot change the cluster name. Changing the cluster name might cause the add or delete ESXi servers operations in the cluster to fail.





 Related links 



* [Viewing vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewinginstances)
* [Expanding and contracting capacity for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)
29 August 2019 

Updated Web crawl connector status : The Web crawl connector moved from beta status to GA status. See [Web crawl](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesconnectwebcrawl) for more information about this connector.





 4 June 2019 

Change to Preview API : The Preview API is deprecated and is no longer available, effective 30 September 2019.





 30 April 2019 

New management of Query expansion and Stopword from Search settings : [Query expansion](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptsquery-expansion) and [Stopword](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptsstopwords) lists can now be uploaded or deleted using the Search settings screen in the Discovery tooling. Previously, these lists could only be managed using the API.

Update to version string : The version string for all API calls changed to 2019-04-30 from 2019-03-25.





 26 April 2019 

Improved accuracy of scoring algorithms : The IBM Watson™ Discovery update announced on [April 2, 2019](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notes2apr19) is complete. This upgrade included changes to improve the accuracy of the scoring algorithms used in Discovery for ranking documents and passages. It is likely that the changes to your score and confidence are small, and there might also be some small changes to the ranking order. If your applications make use of the score or confidence fields directly, it is recommended that you update your applications, as necessary.

New multi-token query expansion support : Multi-token query expansion is now supported. See [Query expansion](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptsquery-expansion) for more information.





 17 April 2019 

Deprecated Data Crawler : The Data Crawler is no longer available for download and is no longer supported. See [Connecting to Data Sources](https://cloud.ibm.com/docs/discovery?topic=discovery-sources) for other connectivity options.





 2 April 2019
Watson IoT Platform troubleshooting 

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

Here are the answers to common troubleshooting questions about using IBM Watson® IoT Platform on IBM Cloud.



 Problem accessing your Watson IoT Platform organization 

You cannot log in to a Watson IoT Platform organization that you own.

You cannot log in to your Watson IoT Platform organization directly by using the organization URL or by using https://internetofthings.ibmcloud.com.

Your access to your Watson IoT Platform organization might have expired. Watson IoT Platform organizations that were created by using IBM Cloud® use temporary user profiles by default.

You can resolve this problem by accessing your Watson IoT Platform organization by using IBM Cloud and changing the expiration setting for your user profile. To change your user expiration settings:



1. From your IBM Cloud dashboard, open your Watson IoT Platform service.
2. Click Members from the navigation bar.
3.
You can find a summary of all user-initiated jobs when you click the User tab on the action's Jobs page.



Review the following status that can be assigned to a job:



Job status

 Status Description 

 ok The total number of target hosts where the Ansible playbook ran. 
 changed The total number of target hosts that were accessed and changed. 
 failed The total number of target hosts where the Ansible playbook might not be successfully ran. 
 skipped The total number of target hosts that were accessed but might not be updated as changes are applied to the hosts. 
 unreachable The total number of target hosts that might not be found or reached. 



When the action job execution displays DEPRECATION WARNING message, you need to set the input variable as ansible_python_interpreter = auto as shown in the screen capture to avoid DEPRECATION WARNING message in the job.

Zoom

![Configuring input variable to silence warning message](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/advanced_inputvariable.png)

Configuring input variable to silence warning message
<-- </section "id="section-http-request-analytics-examples" "> --><-- </section "id="section-http-request-analytics" "> --><-- <section "id="section-web-analytics" "> --> ibmcloud cis web-analytics (Deprecated) Web analytics will be deprecated on November 2, 2020. Use ibmcloud cis http-request-analytics]ibmcloud cis http-request-analytics] instead. Get analytics of the DNS domain. ibmcloud cis web-analytics DNS_DOMAIN_ID --recent DURATION] -t, --table requests | bandwidth | uniques | threats | status_code] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-web-analytics-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--recent: The beginning of the requested time frame. Valid values are: 6h (6 hours ago), 12h, 1d (1 day ago), 1w (1 week ago), 1m (1 month ago), 2m, 3m. The default value is 1w.-t, --table: Output table. Valid values are requests, bandwidth, uniques, threats and status_code. If not set, it outputs all the tables.-i, --instance: Instance name or ID. 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-web-analytics-options" "> --><-- <section "id="section-web-analytics-examples" "> --> Examples Get web analytics for domain 31984fea73a15b45779fa0df4ef62f9b.
The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
4.4 stable true
4.2 deprecated false

The IBM Cloud Databases API deployables endpoint returns all deployable databases. Use the version parameter to return the version number.

GET /v5/ibm/deployables







 Minor versions 

IBM Cloud is committed to providing secure, up-to-date versions of databases. As updates are released by database project maintainers, they are tested, evaluated, and released to Cloud Databases deployments. Your deployment's minor version and patch updates are handled automatically and are not user configurable.
Debugging the cluster autoscaler 

Review the options that you have to debug your cluster autoscaler and find the root causes for failures.

Before you begin: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



 Step 1: Check the version 



1. Verify that the cluster autoscaler add-on is installed and ready.

ibmcloud oc cluster addon ls --cluster <CLUSTER_NAME>

Example output

Name Version Health State Health Status
cluster-autoscaler 1.0.4 normal Addon Ready
2. Compare the version that runs in your cluster against the latest version in Cluster autoscaler add-on [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).
3. If your version is outdated, deploy the latest cluster autoscaler version to your cluster.



Deprecated You can install the cluster autoscaler Helm chart, but the helm chart is deprecated and becomes unsupported tentatively 15 September 2020. You can't install the add-on and the Helm chart in the same cluster at the same time.





 Step 2: Check the configuration 

Check that the cluster autoscaler is configured correctly.



1. Get the YAML configuration file of the cluster autoscaler ConfigMap.

oc get cm iks-ca-configmap -n kube-system -o yaml > iks-ca-configmap.yaml
2. In the data.workerPoolsConfig.json field, check that the correct worker pools are enabled with the minimum and maximum size per worker pool.



* "name": "<worker_pool_name>": The name of your worker pool in the ConfigMap must be exactly the same as the name of the worker pool in your cluster. Multiple worker pools must be comma-separated.
Debugging the cluster autoscaler 

Review the options that you have to debug your cluster autoscaler and find the root causes for failures.

Before you begin: [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



 Step 1: Check the version 



1. Verify that the cluster autoscaler add-on is installed and ready.

ibmcloud oc cluster addon ls --cluster <CLUSTER_NAME>

Example output

Name Version Health State Health Status
cluster-autoscaler 1.0.4 normal Addon Ready
2. Compare the version that runs in your cluster against the latest version in Cluster autoscaler add-on [change log](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog).
3. If your version is outdated, deploy the latest cluster autoscaler version to your cluster.



Deprecated You can install the cluster autoscaler Helm chart, but the helm chart is deprecated and becomes unsupported tentatively 15 September 2020. You can't install the add-on and the Helm chart in the same cluster at the same time.





 Step 2: Check the configuration 

Check that the cluster autoscaler is configured correctly.



1. Get the YAML configuration file of the cluster autoscaler ConfigMap.

kubectl get cm iks-ca-configmap -n kube-system -o yaml > iks-ca-configmap.yaml
2. In the data.workerPoolsConfig.json field, check that the correct worker pools are enabled with the minimum and maximum size per worker pool.



* "name": "<worker_pool_name>": The name of your worker pool in the ConfigMap must be exactly the same as the name of the worker pool in your cluster. Multiple worker pools must be comma-separated.
: Add a warning to the _find endpoint if multiple document scans were required to generate a result.

_find endpoint error
: Fix a bug in the _find endpoint whereby an error would be returned if a document matched by a text index was deleted while the query was being processed.







 January 2020 



 15 January 2020 

The following changes were made in build 8126:

Improvements
: Internal bug fixes.

Replication error reports
: Improvements to replication error reporting - instead of a function_clause, human-readable markers are returned, for example, bulk_docs_failed. Stack traces are no longer included.

Replication job statistics
: Replication job statistics, such as docs_read, docs_written, and doc_write_failures are preserved when replication jobs restart.

Replication jobs
: Replication jobs to a target endpoint by using IAM Writer permissions no longer crash and continuously restart when they write design documents. Instead, the doc_write_failures statistic is incremented for each failed design document write. This behavior is consistent with replicating by using the legacy API-key-based authentication.







 November 2019 



 1 November 2019 

The following changes were made in build 8111:

Improvements
: Internal bug fixes.

Replication statistics
: The _scheduler/docs endpoint now includes more detailed replication statistics to match _active_tasks output. It also includes details on replications that started with _replicate.

Replication error
: Fix an instance where the replicator failed a replication but the error was recoverable.

Empty payload
: Fix a bug introduced in recent builds where sending an empty payload to _bulk_docs would result in a 400 response status code rather than accepting the no-op operation.







 October 2019 



 21 October 2019 

Multiple restrictions employed for performance gains
: IBM released exciting new capabilities for IBM Cloudant that are available now. IBM Cloudant documented the deprecation of some functionality, and also, new restrictions for other processes. A communication was released that details the exact timeline when these restrictions go into effect. If you use any of the following functions or are concerned about how to make the necessary application changes, reach out to support by email.
ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
4.4 stable true
4.2 deprecated false

The IBM Cloud Databases API deployables endpoint returns all deployable databases. Use the version parameter to return the version number.

GET /v5/ibm/deployables







 Minor versions 

IBM Cloud is committed to providing secure, up-to-date versions of databases. As updates are released by database project maintainers, they are tested, evaluated, and released to Cloud Databases deployments. Your deployment's minor version and patch updates are handled automatically and are not user configurable.