vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Change the template_source_data_request_model['type'] variable to the Terraform version that you are using to create IBM Cloud resources such as terraform_v0.14. Ensure that your Terraform templates are compatible with the version that you are mentioning in this field.
* Provide your GitHub or GitLab Repository HTTPS URL where your Terraform files reside in the template_repo_request_model['url'] variable. If you are using the [public repository](https://github.com/IBM-Cloud/hpc-cluster-slurm) that is provided by IBM Cloud, then set this variable as template_repo_request_model['url'] = 'https://github.com/IBM-Cloud/hpc-cluster-slurm'; otherwise, set it to the private repository you are using.



4. Inside the schematics_service.create_workspace function, provide the following parameters:



* Provide an optional description.
* Provide a name to identify your Schematics workspace, for example, terraform-dev-workspace.
* Change the type parameter to the Terraform version that you are using to create IBM Cloud resources, for example, terraform_v0.14.
* Change the location to a region where your Schematics workspace needs to be created, for example, us-south.
* Change the resource group to the resource group where your resources should be grouped, for example, Default for a default resource group.
* If you are using a private GitHub repository, provide your personal GitHub access token that you set up in [Setting up the IBM Cloud Schematics](https://cloud.ibm.com/docs/ibm-slurm?topic=ibm-slurm-setting-up-api) prerequisites in the x_github_token= "<github-api-token>" parameter. If you are using the public repository that is provided by IBM Cloud, you do not need to specify this parameter.
* Optional: Provide the tags if you want to filter resources by using the tag.



5.
You can create virtual server instances and bare metal servers with a mix of RSA and Ed25519 SSH keys.



* For Windows or VMware images, you must use the RSA SSH key type. The Ed25519 SSH key type can't be used with Windows or VMware images.
* For Linux images, the Ed25519 SSH key type can be used only if the SSH server for the operating system supports that key type.



You can't create SSH keys within the API, you can import only an existing SSH key. You can create an SSH key within the UI. You have the option when you create an SSH key to copy the API code snippet for that key.

In the API, you can specify which type of key by using the type variable. The default type is RSA. If you try to import a Ed25519 SSH key and don't specify the ed25519 key type, the process fails.

"type":"ed25519"





 Before you begin 

You can generate an SSH key in IBM Cloud® Virtual Private Cloud when you create the SSH key on the SSH keys for VPC page. However, if you choose to import an existing SSH key file, keep the following limitations in mind.



* Your SSH key must be an RSA or Ed25519 key type with a key size of either 2048 bits or 4096 bits.
* If your Mac system generates a key size of 3072 bits (by default), run one of the following commands to make sure that the generated key is a supported size.



* For RSA SSH key type, issue: ssh-keygen -t rsa -b 4096 -C "user_ID"
* For Ed25519 SSH key type, issue: ssh-keygen -t ed25519 -b 4096 -C "user_ID"



* SSH keys are generated as key pairs; one is a public key, and the other is a private key. Select the public key when you import an SSH key to your VPC. The corresponding private key remains on your local workstation and is not imported.
For more information, see [Using imported ML models to find custom terms](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-domain-ml).





 Using a corpus as training data 

Discovery has an entity extractor tool that you can use to define a type system. The entity extractor user interface is similar to the Knowledge Studio user interface that is used to annotate documents that you add to corpus for a machine learning model. However, in Knowledge Studio, you define root-level entities only, not subtypes or relationships.

As an alternative to importing a Knowledge Studio model as is and applying it as an enrichment, you can also import a Knowledge Studio corpus. When you add a Knowledge Studio corpus to the Discovery entity extractor tool, any root-level entities from the corpus are represented as new entities in the Discovery entity extractor workspace. Entity subtypes are not recognized. Although, you can take extra steps to [retain subtype information](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-wksmigrate-wks-subtypes).

Relations and coreferences from the Knowledge Studio machine learning model are not represented, neither are any custom dictionaries that are associated with the model.

Things to consider when choosing whether to import a model or import a corpus:



* You can continue to edit the type system when you import the corpus. When you import a trained model, you cannot subsequently edit it in Discovery.
* An imported model that you apply to a collection as an enrichment can recognize any entity subtype, relation, and coreference information that the original model was trained to recognize in addition to root-level entities. An entity extractor enrichment can find and tag entities only.



For more information, see [Importing a Knowledge Studio corpus](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-entity-extractorentity-extractor-import-wks).





 Retaining subtype information 

When you import a Knowledge Studio model to Discovery, any subtypes that were defined in the model are identified as mentions of the parent entity type. The subtype entities themselves are not preserved.
Creating custom categories models (Beta) 

The custom categories feature is Beta. It is in a trial stage of development and is not recommended for production use.

Do not input any sensitive or personal information when you use the custom categories feature. The Beta release might not be compatible with legislation such as GDPR. For more information, see [Information security](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-information-security).

[Learn at-a-glance](https://github.com/watson-developer-cloud/doc-tutorial-downloads/blob/master/natural-language-understanding/Explainers/Custom%20Categories%20One%20Pager-2023.pdf) how the custom categories feature works, and best practices for training your model.

The custom categories feature allows you to train custom English categories models with service instances deployed in the Dallas location. A custom categories model can be trained when no data is available; the only fields required for training categories models are labels and key_phrases.



 Creating categories training data 



 Categories training data requirements 

Create and train a custom categories model using the Natural Language Understanding training API. You can also view an example [Python notebook](https://github.com/watson-developer-cloud/doc-tutorial-downloads/blob/master/natural-language-understanding/custom_categories_example.ipynb) that shows how to create and train a custom categories model.



1. Training data must be JSON format, with application/json content type. Each training data file needs to contain a list of JSON objects, and each of these objects needs to have labels and key_phrases defined:



* labels: These are the lists of category labels, in the order of their hierarchy. For example, if you want to add labels with a hierarchy where B is a child of A, the list of labels here would be:

"labels": ["A", "B"]
* key_phrases: These are lists of phrases that can uniquely identify the corresponding labels, for example:

"key_phrases": ["films", "action movies"]



2.
type string type MUST be string. 
 format date-time format MUST be date-time. 
 minLength 20 minLength MUST be present. 
 maxLength 29 maxLength MUST be present. 









 CRN 

The CRN type provides for a Cloud Resource Name. CRN values MUST conform to the CRN specification and MUST uniquely identify a resource among all resources.

It is not required that all models have CRN fields. However, a model which has an associated CRN SHOULD include it in a field named crn. Any other field SHOULD NOT contain a CRN.

CRN fields MUST NOT be used in place of identifiers and MUST NOT be used to identify a resource in a URI path segment.



 Response format 

For responses, a CRN field SHOULD have a documented maximum length of 512 characters. A CRN field SHOULD have a permissible character set limited to printable ASCII and SHOULD have a documented regular expression pattern which CRNs are guaranteed to match.

A CRN value MUST be returned as a JSON string and MUST be returned in consistent case. Individual segments which might otherwise be case-insensitive (such as UUIDs) SHOULD be returned in lowercase.



Schema guidance for CRNs in responses

 Constraint Recommended value Description 

 type string type MUST be string. 
 format crn format MUST be crn. 
 minLength 9 minLength SHOULD be present. 
 maxLength 512 maxLength SHOULD be present. 
 pattern ^crn:v[0-9](:([!A-Za-z0-9-._$&'()+,;=@/] %[0-9A-Z]{2})){8}$ pattern SHOULD be present. 







 Request formats 

For requests, a CRN field MUST have a documented maximum length of 512 characters. A CRN field MUST have a permissible character set limited to printable ASCII and SHOULD have a documented regular expression pattern which CRNs are required to match.

Length, character set, and pattern constraints MUST be checked prior to any other processing of CRNs included in requests.
ibmcloud cbr rule-create --api-types crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster --description "privateAccess=allowAll, publicAccess=oneIP" --service-name containers-kubernetes --service-instance CLUSTER-ID --context-attributes endpointType=private --context-attributes endpointType=public,networkZoneId=allow-client-ip





 Creating rules from the console 



1. [Review the available contexts](https://cloud.ibm.com/docs/containers?topic=containers-cbrcbr-overview) and determine the rules you want to create.
2. Follow the steps to [create context-based restrictions in the console](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-create).









 Limitations 



* After you create a rule, it might take up to 10 minutes for the rule to take effect.
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API types must not reference network zones that contain IPv6 addresses. The APIs included in the cluster type don't support IPv6.
* If you add IBM Cloud Kubernetes Service resources to private-only network zones, the APIs for getting and listing clusters are still accessible over the public network.
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API types must not reference other services like IBM Cloud Object Storage or Key Protect
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API type do not support Report-only enforcement for the cluster API type.
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API types are limited to no more than 20 IPs/subnets for private rules, and 200 IPs/subnets for public rules. These limits are expected to increase after the backend scalability of our implementation of Red Hat OpenShift on IBM Cloud CBR is updated.
See [ibmcloud ce secret](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-secret-create) commands. Use the --format option to specify the category of secret, such as basic_auth, generic, ssh, tls, or registry. The default value for the --format option is generic.

By using the secret create command, you can create and manage various secret formats. For descriptions of the various secret formats, see [What kind of secrets can I create in Code Engine?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-categories)

Learn how to create the following types of secrets with the CLI,



* [Basic authentication](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-cli-basicauth)
* [Generic](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-cli-generic)
* [Registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-cli-registry)
* [SSH](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-cli-ssh)
* [TLS](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-cli-tls)





 Creating a basic authentication secret with the CLI 

A basic authentication secret contains a username and password key and is used to access a service that requires basic HTTP authentication. The following example creates a basic authentication secret with credentials for myusername and the associated password is provided in a file on the local workstation

ibmcloud ce secret create --name mysecret-basicauth --format basic_auth --username myusername --password-from-file ./password.txt
--content-type, --ct
: The media type of the --data or --data-base64 option. Examples include application/json, application/x-www-form-urlencoded, text/html, and text/plain. This value is optional.

--da, --data
: The data to send to the destination; for example, '{ "message": "Hello world!" }'. If you specify the --data option, do not use the --data-base64 option.

This value is optional.

--data-base64, --db
: The base64-encoded data to send to the destination; for example, Q29kZSBFbmdpbmU=. If you specify the --data-base64 option, do not use the --data option. This value is optional.

--destination-type, --dt
: The type of the destination. Valid values are app and job. This value is optional. The default value is app.

--extension, --ext
: Set CloudEvents extensions to send to the destination. Must be in NAME=VALUE format. This action adds a new CloudEvents extension or overrides an existing CloudEvent attribute. Specify one extension per --extension option; for example, --ext extA=A --ext extB=B. This value is optional.

--force, -f
: Force to create a cron event subscription. This option skips the validation of the specified destination. This value is optional. The default value is false.

--no-wait, --nw
: Create the cron event subscription and do not wait for the subscription to be ready. If you specify the --no-wait option, the subscription create begins and does not wait. Use the subscription cron get command to check the subscription status. This value is optional. The default value is false.

--output, -o
: Specifies the format of the command output.
! |<-- </table ""> -->Pseudo data types are not actual data types, but are placeholders that are used by the documentation to represent any of several time series data types.<-- <table> -->Table 2. Pseudo data types| Placeholder | Description || ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- || TimeSeries | Represent any of the following data types: - DoubleTimeSeries<br><br><-- <ul> --><br><br> * DoubleArrayTimeSeries<br> * DoubleSegmentTimeSeries<br> * DoubleArraySegmentTimeSeries
A custom operation SHOULD use a POST or a GET method, following [the requirements for those methods](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-methods).







 Examples 

Each media type definition within an operation's request body and a successful response body definitions MUST include at least one example. A single example can be provided within the media type's example property. Multiple, named examples can be provided in the (mutually exclusive) examples property.

If multiple examples are provided in a media type's examples object, one of the examples MUST be provided in a property named primary. Other properties in the examples object SHOULD have lower snake case names.

The single example in a media type's example property or the primary example in a media type's examples object SHOULD represent only common-case properties and values. All examples provided MUST be realistic and representative of possible real-world values.
Creates an anchor that sets an anchor point when an observation value is greater than or equal to (>=) the input value.

TS_ANCHOR_LT(Double) Output: AnchorType
Creates an anchor that sets an anchor point when an observation value is less than (<) the input value.

TS_ANCHOR_LTE(Double) Output: AnchorType
Creates an anchor that sets an anchor point when an observation value is less than or equal to (<=) the input value.

TS_ANCHOR_DIVISIBLE_BY(Double) Output: AnchorType
Creates an anchor that sets an anchor point when an observation value is evenly divisible (that is, divisible with no remainder) by the input value.

TS_ANCHOR_AND(AnchorType, AnchorType) Output: AnchorType
Creates an anchor that sets an anchor point only when both of the specified anchors would set an anchor point independently.

TS_ANCHOR_OR(AnchorType, AnchorType) Output: AnchorType
Creates an anchor that sets an anchor point only when either of the specified anchors would set an anchor point independently.

TS_ANCHOR_NOT(AnchorType) Output: AnchorType
Creates an anchor that sets an anchor point when the specified anchor would not.

TS_ANCHOR_INDEX(AnchorType, Integer) Output: AnchorType
Creates, for use by an array time series, an anchor of the specified type (first parameter) for a specified index (second parameter) of the series.





 Forecasting model creation functions 

Each of these functions creates a forecasting model artifact, which is used by other functions for forecasting and anomaly detection.

TS_FORECAST_BATS(Integer, Boolean) Output: ForecastingModel
Creates a forecasting model with Box-Cox, ARMA, trend, and seasonal (BATS) components. The value of the first parameter specifies the minimum number of training observations. The value of the second parameter specifies whether the Box-Cox transformation is to be used:



* Specify true if the Box-Cox transformation is to be used.
* Specify false if the Box-Cox transformation is not to be used.



TS_FORECAST_HWS(Integer, Integer) Output: ForecastingModel
Refer to the section [Customizing environments with inputs](https://cloud.ibm.com/docs/schematics?topic=schematics-define-blueprintsdefine-templates-input) for guidance on defining inputs.

Template inputs follow the same type convention as Terraform HCL. The supported types are the same as the [Terraform variable types](https://developer.hashicorp.com/terraform/language/expressions/types). If the type is omitted the default is string. For an example showing data types represented in YAML, see [blueprint complex inputs](https://github.com/Cloud-Schematics/blueprint-complex-inputs) and the code snippet below.

inputs:
  - name: list_any_flow_scalar
type: list(any)
- name: docker_ports
type: 
list(object({
internal = number
external = number
protocol = string
})





 Template outputs 

Values to be returned from a template are defined by [output statements](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-template-schema-yamlbp-outputs) and use the same interpolation syntax as module inputs.

outputs:
  - name: cos_id
    value: $module.basic-cos-storage.outputs.cos_id





 Module definitions 

Templates support the use of both Terraform [root modules](https://developer.hashicorp.com/terraform/language/modulesthe-root-module) and Terraform [child](https://developer.hashicorp.com/terraform/language/moduleschild-modules) modules. See the section [Using Terraform modules with blueprint templates](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-terraform).
if (err == nil) {
enabled := feature.IsEnabled()
featureValue := feature.GetCurrentValue(entityId, entityAttributes)
}









 Supported data types 

You can configure feature flags and properties with App Configuration, supporting the following data types: Boolean, Numeric, String, and SecretRef. The String data type can be a text string, JSON, or YAML. The SDK processes each format as shown in the table.



Table 1. Example outputs

 Feature or Property value Data type Data format Type of data returned by GetCurrentValue() Example output 

 true BOOLEAN not applicable bool true 
 25 NUMERIC not applicable float64 25
ibmcloud cbr rule-create --api-types crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster --description "privateAccess=allowAll, publicAccess=oneIP" --service-name containers-kubernetes --service-instance CLUSTER-ID --context-attributes endpointType=private --context-attributes endpointType=public,networkZoneId=allow-client-ip





 Creating rules from the console 



1. [Review the available contexts](https://cloud.ibm.com/docs/containers?topic=containers-cbr&interface=uicbr-overview) and determine the rules you want to create.
2. Follow the steps to [create context-based restrictions in the console](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-create).









 Limitations 



* After you create a rule, it might take up to 10 minutes for the rule to take effect.
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API types must not reference network zones that contain IPv6 addresses. The APIs included in the cluster type don't support IPv6.
* If you add IBM Cloud Kubernetes Service resources to private-only network zones, the APIs for getting and listing clusters are still accessible over the public network.
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API types must not reference other services like IBM Cloud Object Storage or Key Protect
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API type do not support Report-only enforcement for the cluster API type.
* IBM Cloud Kubernetes Service CBR rules that apply to all API types or the cluster API types are limited to no more than 20 IPs/subnets for private rules, and 200 IPs/subnets for public rules. These limits are expected to increase after the backend scalability of our implementation of Red Hat OpenShift on IBM Cloud CBR is updated.