vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Why is Schematics not able to clone the private GitHub repository?](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-create-failstsg-privategithub)
* [Why is Schematics not able to clone the public GitHub repository?](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-create-failstsg-publicgithub)



[blueprint create fails in the create_init step](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-create-init-failsbp-create-init-fails)

[Blueprint apply fails](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails)



* [Blueprint apply fails with message "Install of module Failed"](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails1)
* [Blueprint apply failure due to Terraform config coding error](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails2)
* [Blueprint apply failure due to Terraform timeouts or transient failures](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails3)
* [Blueprint apply failures that require changes to values in input files](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails4)
* [Blueprint apply failures that require changes to dynamic inputs](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-apply-failsbp-apply-fails5)







 Troubleshooting Agents
This gives direct control, but it makes the producer code more complex because it takes on the responsibility for managing the partition selection. For more information, see the method call Producer.partitionsFor. For example, the call is described for [Kafka version 2.2.0](https://kafka.apache.org/22/javadoc/org/apache/kafka/clients/producer/KafkaProducer.html).

If the producer does not specify a partition number, the selection of partition is made by a partitioner. The default partitioner that is built into the Kafka producer works as follows:



* If the record does not have a key, select the partition in a round-robin fashion.
* If the record does have a key, select the partition by calculating a hash value for the key. This has the effect of selecting the same partition for all messages with the same key.



You can also write your own custom partitioner. A custom partitioner can choose any scheme to assign records to partitions. For example, use just a subset of the information in the key or an application-specific identifier.





 Message ordering 

Kafka generally writes messages in the order that they are sent by the producer. However, in certain situations retries can cause messages to be duplicated or reordered. If you want a sequence of messages to be sent in order, it is important to ensure that they are all written to the same partition because this is the only way to guarantee message ordering.

The producer is also able to retry to send messages automatically. It is a good idea to enable this retry feature because the alternative is that your application code must perform any retries itself. The combination of batching in Kafka and automatic retries can have the effect of duplicating messages and reordering them.

For example, if you publish a sequence of three messages <M1, M2, M3> on a topic. The records might all fit within the same batch, so they're all sent to the partition leader together. The leader then writes them to the partition and replicates them as separate records.
* UI
* CLI
* API







 Applying a plan 

When you apply a plan, the IBM Cloud® resources are deployed to build a Slurm cluster instance on your IBM Cloud account with your specific choice of configuration properties.



 Applying a plan using the UI 



1. After you generate a plan in the IBM Cloud console, click Apply plan. This action generates a new log that can be viewed in the Jobs tab.
2. Review the log file for any errors, fix the errors, and then click Apply plan again.
3. After you successfully apply a plan, you can review all of the resources that are deployed under this workspace by clicking the Resources tab.







 Applying a plan using the CLI 

Run the following command to apply a plan to your workspace:

ibmcloud schematics apply --id <WORKSPACE_ID>

While the resources are being deployed, you can monitor the log files for errors or confirm that the action was completed successfully. This step can take some time based on how many virtual servers are being provisioned as part of your configuration file. Run the following command to monitor your log files:

ibmcloud schematics logs --id <WORKSPACE_ID>

Sample response:

2021/04/05 09:44:54 Terraform apply | Apply complete! Resources: 14 added, 0 changed, 0 destroyed.
2021/04/05 09:44:54 Terraform apply 
2021/04/05 09:44:54 Terraform apply | Outputs:
2021/04/05 09:44:54 Terraform apply 
2021/04/05 09:44:54 Terraform apply | sshcommand = ssh -J root@52.116.124.67  root@10.241.0.6
2021/04/05 09:44:54 Command finished successfully.
2021/04/05 09:45:00 Done with the workspace action

After the plan is successfully applied, it generates an sshcommand in the Outputs section in the Terraform code. You can use this command to log in to the Slurm cluster.
This method is not optimal because it causes the Edge server to contact the origin server for content that is already cached, but that uses a different cache key. You can use the Cache Key Optimization feature to specify which query args to include or ignore when generating a Cache Key. This feature applies to any create or update of a CDN-Mapping configuration, as well as any create or update of an origin path.

You can configure the value of Cache Key Optimization from the Settings tab after creation of a CDN mapping. An origin path can be configured during the create or update operations of an origin path.





 Content Compression 

By default, Content Compression is enabled in Akamai CDN for the following content types:



* text/html*
* text/css*
* text/xml*
* text/json
* text/javascript*
* text/plain*
* application/x-javascript*
* application/json
* application/xml*



When compression is handled by the Edge server, then the content must be at least 10 KB. In some cases, compression is taken care of by the origin server, and in those cases, there is no limit on the size of the files to be compressed. If the content is already being compressed by the origin server, it is not compressed again. To enable Content Compression, the request header must define Accept-Encoding: gzip.





 Dynamic Content Acceleration 

You can configure IBM Cloud CDN to serve content with Dynamic Content Acceleration (DCA) optimization. The performance of web pages with dynamic content can be measurably improved. For more information, see [Configuring Dynamic Content Acceleration](https://cloud.ibm.com/docs/CDN?topic=CDN-dynamic-content-acceleration).





 Geographical access control 

Geographical access control is a rule-based behavior that enables you set the access-type parameter for a group of users, based on their geographical location. Two types of behaviors are available: ALLOW and DENY.

The access-typeALLOW lets you specifically allow traffic to selected regions, based on the type of region. Allowing traffic for specific regions implicitly blocks traffic for all others.
[Image showing the rule type and address for a channel auth record](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_webconsole_qm_securitytab_channelauthrecord2.png)
8. You should now see a new channel authentication record with your channel name.









 MQRCCF_ACCESS_BLOCKED (3382) when attempting to administer queue manager 

While attempting to define, delete or alter objects in your IBM MQ on Cloud queue manager your administration client receives an MQRCCF_ACCESS_BLOCKED (3382) return code. With clients running versions of IBM MQ v9.0.3 or below you might receive a return code of MQRC_UNEXPECTED_ERROR (2195)

Additionally, an error message is outputted with title AMQ7355E: Object <Object name>, object type <Object type>, is locked to remote users.



 Explanation 

Certain features of IBM MQ have been disabled for users of IBM MQ on Cloud. These features are disabled either to prevent accidentally disabling the queue manager or potential misuse of the service. You might see that some of the locked attributes have values assigned to them, these are assigned automatically and cannot be changed.

If you try to define, alter or delete an object or attribute that has been disabled, your queue manager blocks this action with the return code MQRCCF_ACCESS_BLOCKED (3382). This return code was added at version 9.0.3 of IBM MQ, clients that are older than version 9.0.3 will not recognize this return code and so are likely to return MQRC_UNEXPECTED_ERROR (2195) instead.

The following features have been disabled:



* The following queue manager attributes: CONNAUTH, CHADEXIT, CLWLEXIT, CLWLDATA, SSLCRYP, SSLKEYR
* Authentication information objects of type IDPWOS & IDPWLDAP
Troubleshooting Citrix DaaS for IBM Cloud VPC 

Use this information when troubleshooting Citrix DaaS for IBM Cloud® on VPC.



 The VDA is not registering 

When you create a Machine Catalog, the VDA shows as Unregistered. This error happens because the VDA security group was not selected when the Machine Catalog was created. The create defaults to the first security group in the list, you must select the VDA security group instead of using the default.

Zoom

![Security Group](https://cloud.ibm.com/docs-content/v1/content/e9cda99c64ea1ee68cf0eda257d6a1de69ddbc4e/citrix-daas/images/machine-catalog-vda-sg.png)

Figure 1. Machine Catalog VDA Security Group

Either modify the existing Machine Catalog to use the VDA security group or create a new Machine Catalog and specify the VDA security group.





 Profile with instance storage error 

In the Schematics window, during the Terraform Apply, you see an error that is similar to this message:

022/02/24 22:25:59 Terraform apply | Error: users are restricted from accessing generic profiles with instance storage
2022/02/24 22:25:59 Terraform apply 
2022/02/24 22:25:59 Terraform apply | with ibm_is_instance.custom_image_instance[0],
2022/02/24 22:25:59 Terraform apply | on main.tf line 335, in resource "ibm_is_instance" "custom_image_instance":
2022/02/24 22:25:59 Terraform apply | 335: resource "ibm_is_instance" "custom_image_instance" {
2022/02/24 22:25:59 Terraform apply 
2022/02/24 22:25:59 [ 1m31mTerraform APPLY error: Terraform APPLY errorexit status 139m0m
When the solution was provisioned, a profile with instance storage was selected. However, instance storage is not supported for VPC.
* UI
* CLI
* API







 Applying a plan 

When you apply a plan, the IBM Cloud® resources are deployed to build a Red Hat® OpenShift® cluster instance on your IBM Cloud account with your specific choice of configuration properties.



 Applying a plan using the UI 



1. After you generate a plan in the IBM Cloud console, click Apply plan. This action generates a new log that can be viewed in the Jobs tab.
2. Review the log file for any errors, fix the errors, and then click Apply plan again.
3. After you successfully apply a plan, you can review all of the resources that are deployed under this workspace by clicking the Resources tab.







 Applying a plan using the CLI 

Run the following command to apply a plan to your workspace:

ibmcloud schematics apply --id <WORKSPACE_ID>

While the resources are being deployed, you can monitor the log files for errors or confirm that the action was completed successfully. This step can take some time based on how many virtual servers are being provisioned as part of your configuration file. Run the following command to monitor your log files:

ibmcloud schematics logs --id <WORKSPACE_ID>

Sample response:

2021/04/05 09:44:54 Terraform apply | Apply complete! Resources: 14 added, 0 changed, 0 destroyed.
2021/04/05 09:44:54 Terraform apply 
2021/04/05 09:44:54 Terraform apply | Outputs:
2021/04/05 09:44:54 Terraform apply 
2021/04/05 09:44:54 Terraform apply | sshcommand = ssh -J root@52.116.124.67  root@10.241.0.6
2021/04/05 09:44:54 Command finished successfully.
2021/04/05 09:45:00 Done with the workspace action

After the plan is successfully applied, it generates an sshcommand in the Outputs section in the Terraform code. You can use this command to log in to the Red Hat OpenShift cluster.
ibmcloud ac feature delete 

You can delete a feature, by using the command:

ibmcloud ac feature delete --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID





 Example 

To delete a feature with ID ibm-discount, run the following command:

ibmcloud ac feature delete --environment_id "production" --feature_id ibm-discount



 Output 

The command returns the following output:

OK









 ibmcloud ac feature toggle 

You can toggle a feature value, by using the command:

ibmcloud ac feature toggle --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID --enabled ENABLED



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID

--enabled ENABLED
: The state of the feature flag.





 Example 

To toggle a feature value with ID ibm-discount, run the following command:

ibmcloud ac feature toggle --environment_id "production" --feature_id ibm-discount --enabled false



 Output 

The command returns the following output:

name type disabled_value updated_time feature_id description enabled_value created_time order rules value
IBMers BOOLEAN false 2021-02-02T17:52:46Z ibm-discount Discount given to IBM employees true 2021-02-02T17:52:46Z 1 <Array> true









 ibmcloud ac segment list 

You can list all segments, by using the command:

ibmcloud ac segment list [--limit LIMIT] [--offset OFFSET] [--sort SORT] [--tags TAGS] [--expand EXPAND] [--include INCLUDE]



 Command options 

--limit LIMIT (optional)
: Used for pagination. The number of records to retrieve.

--include INCLUDE (optional)
: Segment details to include the associated rules in the response.

--offset OFFSET (optional)
FAQ extraction was a beta feature that captured question-and-answer pairs from the data source as it was crawled. FAQ extraction generated a new subdocument for each pair and stored the question in the title field and the answer in the text field.

You cannot apply FAQ extraction to new collections.

Any existing collections with FAQ extraction enabled retain FAQ documents in their indexes until the collection is reprocessed. At that time, most of the question-and-answer pair subdocuments are deleted. However, any FAQ subdocuments that were generated from HTML or TXT source files remain. If you want to remove these subdocuments, go to the Manage data page to delete them. Subdocuments that are generated from one parent document all have the same metadata.parent_document_id value.

If you need a way to extract question-and-answer pairs from source documents that use a consistent style and formatting for questions and answers, you can use the Smart Document Understanding tool to annotate the pairs instead. For more information, see [Using Smart Document Understanding](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-configuring-fields).





 25 January 2023 

Set up a Microsoft SharePoint Online data store connector that has Read permission
: When you create a Microsoft SharePoint Online connector to crawl a SharePoint data source by using Open Authentication v2, the enterprise application that is created by Discovery to make the connection requires Read permission only. The enterprise application that was configured for you previously required Write permission.

If you want to update an existing connector so that you can use the new Read permission configuration, you must delete your existing enterprise application first.

For more information, see [Microsoft SharePoint Online connector](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-sharepoint-online-cloud).





 FAQ extraction deprecation announcement 

The beta FAQ extraction feature that detects and extracts question-and-answer pairs from documents is being removed. Support for the feature will end in 1Q 2023.





 6 December 2022 

Now you can stop a data source crawl
Parallelism Parallel execution, flexible Low to medium parallel execution High parallel execution 
 Scale-out Based on number of requests Based on job workload definition Based on events or direct invocations 
 Optimized for Long running highly complex workload and on-demand scale-out Scheduled/planned workloads with high resource demands Startup time and rapid scale-out 







 What are the key features of working with Code Engine applications? 

Review the following topics to learn more about working with applications in Code Engine.



* [Isolation](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-isolation)
* [Logging](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-logging)
* [Running applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-runapp)
* [Scaling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-scaling)
* [Security](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-security)
* [Triggering applications with events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-eventing)
* [Visibility](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ceapplicationsceapp-visibility)





 Isolation 

Code Engine is a multi-tenant, regional service where tenants share the same network and compute infrastructure. In particular, the network and compute infrastructure are shared resources and some management components are common to all tenants. However, tenants and their workloads are isolated from each other by using Code Engine projects. Code Engine prevents communication between projects, providing isolation to your applications inside a multi-tenant environment.
kubectl apply -f ingress-ibmsubdomain.yaml
6. Open your application in a browser at https://<myapp>.<ingress-subdomain>/ or run the below command to see the HTTP output:

curl -I https://$MYAPP.$INGRESS_SUBDOMAIN







 Step 5: Use your own custom subdomain 

This section requires you to own a custom domain. You will need to create a CNAME record pointing to the IBM-provided ingress subdomain for the cluster. If your domain is example.com then the CNAME will be <myapp>.<example.com> pointing to <myapp>.<ingress-subdomain>.



 with HTTP 



1. Create an environment variable pointing to your custom domain:

export CUSTOM_DOMAIN=<example.com>
2. Create an Ingress file ingress-customdomain-http.yaml pointing to your domain from the template file ingress-customdomain-http-template.yaml:

./ingress.sh customdomain_http
3. Deploy the Ingress:

kubectl apply -f ingress-customdomain-http.yaml
4. Access your application at http://<myapp>.<example.com>/.







 with HTTPS 

If you were to try to access your application with HTTPS at this time https://<myapp>.example.com/, you will likely get a security warning from your web browser telling you the connection is not private.

In this section we will use Secrets Manager. With Secrets Manager, you can create, lease, and centrally manage secrets that are used in IBM Cloud services or your custom-built applications. Secrets are stored in a dedicated Secrets Manager instance and you can use built in features to monitor for expiration, schedule or manually rotate your secrets. In this tutorial, we will use a Kubernetes Operator to retrieve the TLS certificate from Secrets Manager and inject into a Kubernetes secret.
If you apply the join() method to the values in the returned array, the flight codes are displayed in a comma-separated list. For example, you can use the following syntax in a response:

The flights that fit your criteria are:
<? T(String).join(",", $flights_found. ?>flight_code]

Result: The flights that match your criteria are: OK123,LH421,TS4156.







 JSONArray.joinToArray(template) 

This method applies the format that you define in a template to the array, and returns an array that is formatted according to your specifications. This method is useful for applying formatting to array values that you want to return in a dialog response, for example.

The template can be specified as a String, JSON Object, or JSON Array. To reference values from the array that you are editing in the template, follow these syntax conventions:



* %: Represents the start or end of an element or element property that you want to return from the array being edited.
* e: Temporarily represents the array element to which you want to apply the formatting. This temporary variable name cannot be changed from e.



For example, you have a context variable that contains an array with a list of flight details for three flights.

"flights": [!
{
"flight": "DL1040",
"origin": "JFK",
"carrier": "Alitalia",
"duration": 485,
"destination": "FCO",
"arrival_date": "2019-02-03",
"arrival_time": "07:00",
"departure_date": "2019-02-02",
"departure_time": "16:45"
},
{
"flight": "DL1710",
"origin": "JFK",
"carrier": "Delta",
"duration": 379,
"destination": "LAX",
"arrival_date": "2019-02-02",
: All users and service IDs are members of the Public Access group by default, which provides unauthenticated access to the resources that the group can access. You can now disable public access at the account level for cases in which you might want to prevent policies that could publicly expose resources from being created. For more information, see [Managing public access to resources](https://cloud.ibm.com/docs/account?topic=account-public).







 November 2019 



 26 November 2019 

Delete resource groups
: Besides the default resource group that's automatically created for you when create your IBM Cloud account, you can now delete any resource group that doesn't contain any resources. For more information, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs).





 04 November 2019 

Bitnami Helm charts
: IBM and VMware are partnering to provide the [Bitnami Application Catalog](https://bitnami.com/stacks) to IBM Cloud customers. The first set of offerings available in the IBM Cloud catalog are the Bitnami Helm charts, which Bitnami has created and validated to work on the IBM Cloud Kubernetes Service. Kubernetes developers typically install Helm charts manually from the CLI by using the helm command. However, this installation process has been simplified by building an auto-installation feature in the IBM Cloud catalog. Check out these offerings today by selecting Bitnami from the Provider filter.







 October 2019 



 18 October 2019 

Apply promo codes to your account and services
: IBM Cloud now has promo codes that you can use to get credit toward your account and services. Promo codes are provided by IBM Cloud sales on a limited basis to customers with billable accounts. You can apply promo codes from a new Promotions page or from the catalog when you create a resource in the IBM Cloud console. For more information, see [Applying promo codes](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-applying-promo-codes).

Download access reports for specific resources