vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Config field details 



Table 4. Available fields and data types in Config

 Field Type Description 

 ArgsEscaped Boolean Displays true if the command is already escaped (Windows® specific). 
 AttachStderr Boolean Displays true if the standard error stream is attached to the container and false if not. 
 AttachStdin Boolean Displays true if the standard input stream is attached to the container and false if not. 
 AttachStdout Boolean Displays true if the standard output stream is attached to the container and false if not. 
 Cmd Array of strings Describes the commands and arguments that are passed to a container to run when the container is started. 
 Domainname String Displays the fully qualified domain name of the container. 
 Entrypoint Array of strings Describes the command that is run when the container starts. 
 Env Array of strings Displays the list of environment variables in the form of key-value pairs. 
 ExposedPorts Key-value map Displays the list of exposed ports in the format [123:,456:]. 
 Healthcheck Object Describes how to check that the container is working correctly. For more information, see [Healthcheck field details](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imageinspect_healthcheck). 
 Hostname String Displays the hostname of the container. 
 Image String Displays the name of the image that was passed by the operator. 
 Labels Key-value map Displays the list of labels that were added to the image as key-value pairs. 
 MacAddress String Displays the MAC address that is assigned to the container. 
 NetworkDisabled Boolean Displays true if the networking is disabled for the container and false if the networking is enabled for the container. 
 OnBuild Array of strings Displays the ONBUILD metadata that was defined on the image Dockerfile. 
 OpenStdin Boolean Displays true if the standard input stream is opened and false if the standard input stream is closed. 
 Shell Array of strings Displays the shell-form of RUN, CMD, ENTRYPOINT.
"updated": "2016-06-01T18:45:11.737Z",
"language": "en-US",
"dialect": "en-US",
"owner": "297cfd08-330a-22ba-93ce-1a73f454dd98",
"name": "Example model",
"description": "Example custom language model",
"base_model_name": "en-US_BroadbandModel",
"status": "training",
"progress": 0
}

The response includes status and progress fields that report the state of the custom model. The meaning of the progress field depends on the model's status. The status field can have one of the following values:



* pending indicates that the model was created but is waiting either for valid training data to be added or for the service to finish analyzing data that was added. The progress field is 0.
* ready indicates that the model contains valid data and is ready to be trained. The progress field is 0.

If the model contains a mix of valid and invalid resources (for example, both valid and invalid custom words), training of the model fails unless you set the strict query parameter to false. For more information, see [Training failures for custom language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-languageCreatefailedTraining-language).
* training indicates that the model is being trained. The progress field is 0. The field changes from 0 to 100 when training is complete.
* available indicates that the model is trained and ready to use. The progress field is 100.
* upgrading indicates that the model is being upgraded. The progress field is 0.
* failed indicates that training of the model failed. The progress field is 0. For more information, see [Training failures for custom language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-languageCreatefailedTraining-language).
Under supported_features, the speaker_labels field indicates whether you can use the speaker_labels parameter with a model. At this time, the field returns true for all models.

However, speaker labels are supported as beta functionality only for US English, Australian English, German, Japanese, Korean, and Spanish (both broadband and narrowband models) and UK English (narrowband model only). Speaker labels are not supported for any other models. Do not rely on the field to identify which models support speaker labels.

For more information about speaker labels and supported models, see [Speaker labels](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-speaker-labels).





 Issue: The progress field for custom models is not continuous 

The following methods include a progress field in the information that they return for a custom model:



* GET /v1/customizations
* GET /v1/customizations/{customization_id}
* GET /v1/acoustic_customizations
* GET /v1/acoustic_customizations/{customization_id}



The field returns the progress for a training or upgrade operation. Currently, the value of the field is 100 if the status is available; otherwise, it is 0.

When you monitor the training or upgrading of a custom model, poll the value of the status field, not the value of the progress field. If the operation fails for any reason, the value of the status field changes to reflect the failure; the value of the progress field remains 0.
* The requestData.initialValue.PolicyKCIAAttrCSK field includes if your key creation and importation policy previously allowed the creation of standard keys.
* The requestData.newValue.PolicyKCIAAttrCSK field includes if your key creation and importation policy allows the creation of standard keys.
* The requestData.initialValue.PolicyKCIAAttrIRK field includes if your key creation and importation policy previously allowed imported root keys.
* The requestData.newValue.PolicyKCIAAttrIRK field includes if your key creation and importation policy allows imported root keys.
* The requestData.initialValue.PolicyKCIAAttrISK field includes if your key creation and importation policy previously allowed imported standard keys.
* The requestData.newValue.PolicyKCIAAttrISK field includes if your key creation and importation policy allows imported standard keys.
* The requestData.initialValue.PolicyKCIAAttrET field includes if your key creation and importation policy previously required keys to be imported via import token.
* The requestData.newValue.PolicyKCIAAttrET field includes if your key creation and importation policy requires keys to be imported via import token.











 Import token events 



 Create import token 

The following fields include extra information:



* The responseData.expirationDate field includes the expiration date of the import token.
* The responseData.maxAllowedRetrievals field includes the maximum amount of times the import token can be retrieved within its expiration time before it is no longer accessible.







 Retrieve import token 

The following fields include extra information:



* The responseData.maxAllowedRetrievals field includes the maximum amount of times the import token can be retrieved within its expiration time before it is no longer accessible.
* The responseData.remainingRetrievals field includes the number of times the import token can be retrieved within its expiration time before it is no longer accessible.







 Completed action of a key rotation 

The following fields include extra information:



* The responseData.eventAckData.eventId field includes the unique identifier that is associated with the event.
The [Compliance assessment report (by Cohasset)](https://www.veeam.com/wp-compliance-assessment-report-cohasset.html) describes the settings that must be configured to become compliant with the following regulations:



* FINRA Rule 4511.
* SEC Rule 17a-4(f).
* CFTC Rule 1 .31 (c)-(d).



The previous assessment report considers the following details as best practice for a Linux hardened repository:



* The Linux hardened repository can be independent or Scale-out backup repository. A repository that retains immutable backup files for compliance with SEC 17a-4(f) must be configured as a stand-alone backup repository as a Veeam Scale-Out backup Repository is not compliant with this rule.
* It is recommended that the name and description attributes for the repository include the word “immutable" when the Linux hardened repository feature is enabled.
* To protect against the possibility of premature deletion of backup files that can result from accelerating the system time clock, Linux OS must be configured to synchronize with a secure time source. For example, with a network time protocol (NTP) clock.
* Ensure separation of duties by assigning management of Linux hardened repositories to a team other than backup administrators.
* Veeam recommends XFS for performance and space efficiency reasons (block cloning support). Due to the requirement for periodic full backups, means that due to fast cloning, synthetic full backups take no physical disk space, except for metadata.
* Only backup job configurations with forward incremental with synthetic or active full are supported. Forward incremental with synthetic full is the default backup job setting.
* For backup copy jobs, GFS must be enabled.
* Encryption of backup files is available as follows:



* When configured in a backup job, Veeam Backup and Replication can use 256-bit AES block cypher encryption.
* For data in transit, a global network traffic rule can be configured to enable all traffic to be encrypted through 256-bit AES encryption. When enable and two backup infrastructure components need to communicate, a dynamic key is generated by the backup server and communicated to each node over a secure channel.
* proto - Protocol type: UDP or TCP
* family - Transport family: IPv4 or IPv6
* accountid - ID of the account which owns the DNS Service instance configured for this query
* zoneid - ID of the zone for which the DNS query is configured for
* zonename - Name of the zone for which the DNS query is configured for
* instanceid - ID of the DNS Service instance configured for this query
* vpcid - ID of the VPC from which this query originates from
* mtype - Metric type: public or private
* cachehit - True or false depending on if the response was served from cache







 Custom resolver summary metrics 

The custom resolver summary provides custom resolver location health.



Table 4. Custom resolver summary metrics

 Metric name Labels 

 ibm_dns_svcs_cr_location_health crid, accountid, instanceid, locationip 



The labels correspond to the following definitions:



* crid - The ID of the custom resolver
* accountid - The ID of the account which owns the DNS Service instance
* instanceid - The ID of the DNS Service instance
* locationip - The IP address of the virtual server instance appliance acting as a custom resolver location







 Custom resolver total platform metrics 

The set of metrics associates with DNS resolution through custom resolvers:



Table 5. Custom resolver platform metrics

 Metric Name Label 

 ibm_dns_svcs_cr_dns_requests_total server, zone, proto, family, type, crid, accountid, instanceid 
 ibm_dns_svcs_cr_dns_responses_total server, zone, rcode, crid, accountid, instanceid 
 ibm_dns_svcs_cr_cache_requests_total server, crid, accountid, instanceid 
 ibm_dns_svcs_cr_cache_hits_total server, type, crid, accountid, instanceid 
 ibm_dns_svcs_cr_cache_misses_total server, crid, accountid, instanceid
Update a rule of a load balancer listener policy.

ibmcloud is load-balancer-listener-policy-rule-update LOAD_BALANCER LISTENER_ID POLICY RULE_ID [--vpc VPC] [--condition contains | equals | matches_regex] [--type header | hostname | path | query | body] [--value VALUE] [--field FIELD] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is load-balancer-listener-policy-rule-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 70294e14-4e61-11e8-bcf4-0242ac110004 --condition equals --type header --field my-app-header --value match-value --output JSON
* ibmcloud is load-balancer-listener-policy-rule-update my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 my-policy 70294e14-4e61-11e8-bcf4-0242ac110004 --condition equals --type header --field my-app-header --value match-value --output JSON







 Command options 



* LOAD_BALANCER: ID or name of the load balancer.
* LISTENER_ID: ID of the listener.
* POLICY: ID or name of the policy.
* RULE_ID: ID of the rule.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --condition: The condition of the rule. One of: contains, equals, matches_regex.
* --type: The type of the rule.
"source": "234-rwekj-55bbc6-980c3ab2:scc",
"ibmensourceid": "91f18cee-7d23-4895-a3ba-0c26696d9d96:api",
"specversion": "1.0",
"type": "com.acme.flightbooking.complete"
}
Show more



* target field is replaced by ibmenpushto
* message field is removed. The alert, url fields are part of the ibmenfcmbody
* settings->gcm is replaced by ibmenfcmbody



The ibmenpushto fields can take four values same as target of push API



1. tags –array of tag names
2. user_ids –array of user ids
3. fcm_devices –array of device Ids
4. platforms –the target device platform



The ibmenfcmbody field contains every field in the settings-> gcmfield of service, but with the following changes:



1. All fields are in snake case instead of camel case. For example, interactiveCategory is interactive_category.
2. Channels and channel groups Push Notificationsare not supported.









 Step 6: Migrate the data from Push Notifications service to IBM Cloud® Event Notifications service 

You can use the [push-en-migration-tool](https://github.com/Event-Notifications/push-en-migration-tool) to migrate the devices and tag subscriptions data from Push Notifications service to the IBM Cloud® Event Notifications service.





 Step 7: Release a new version of the app 

After the integration is complete, release the new version of the app. In the new version, ask the user's permission to send a notification and register the device again. In the overlapping window when the user population is migrating from the old version of the app to the new version, the notifications might have to be sent to the existing Push Notifications environment and the new IBM Cloud® Event Notifications environment.
* The requestData.adminId field includes the SHA-256 hash of the signature key file that is associated with the administrator to be added.
* The responseData.adminIds field lists the SHA-256 hashes of the signature key files associated with all the administrators that are added to the crypto unit.







 Remove a crypto unit administrator 



* The requestData.adminId field includes the SHA-256 hash of the signature key file that is associated with the administrator to be removed.
* The responseData.adminIds field lists the SHA-256 hashes of the signature key files that are associated with all the administrators that are added to the crypto unit.







 Set the signature thresholds 



* The requestData.signatureThreshold field includes the [main signature threshold](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-understand-conceptssignature-thresholds-concept) that you set on the crypto unit.
* The requestData.revocationSignatureThreshold field includes the [revocation signature threshold](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-understand-conceptssignature-thresholds-concept) that you set on the crypto unit.
* The responseData.signatureThreshold field includes the [main signature threshold](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-understand-conceptssignature-thresholds-concept) that is successfully set on the crypto unit.
* The responseData.revocationSignatureThreshold field includes the [revocation signature threshold](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-understand-conceptssignature-thresholds-concept) that is successfully set on the crypto unit.







 Load the new master key register 



* The requestData.masterKeyIds field lists the SHA-256 hashes of all the master key parts files that you select to load to the crypto unit.
All other Object Storage management events are forwarded to the IBM Cloud Activity Tracker instance that is associated with the bucket.

To view events, you must access the web UI of the IBM Cloud Activity Tracker instance in the location that is associated with the bucket.





 Data events 

Object Storage data events are forwarded to the IBM Cloud Activity Tracker instance that is associated with the bucket.

To view events, you must access the web UI of the IBM Cloud Activity Tracker instance in the location that is associated with the bucket.







 Analyzing events 



 Identifying the COS instance ID that generates the event 

In the IBM Cloud, you can have 1 or more COS instances.

To quickly identify the COS instance ID in your account that has generated an event, check the field responseData.serviceInstanceId that is set in the responseData field.





 Identifying the bucket location 

To quickly identify the bucket location, check the field responseData.bucketLocation that is set in the responseData field.





 Getting the unique ID of a request 

Each action that a user performs on a COS resource has a unique ID.

To get the unique ID of a request to a COS resource, check the field responseData.requestId that is set in the responseData field.





 Getting all events for a multipart upload operations 

When you upload a large object by using multipart upload operations, each operation generates an event. In each event, the field responseData.uploadId is set to the same value.

To search for all events that are part of a multipart upload operation, you can search for a specific responseData.uploadId value.





 Getting all events that are generated for a restore request 

A request to restore an object from an archive generates multiple events in COS:



1. A read action of the source object. This action generates an event with action cloud-object-storage.object-restore.read.
2. A create action of the object into a bucket. This action generates an event with action cloud-object-storage.object-restore.create.



You can use the responseData.requestId field to identify the events that are generated when you restore an object.
You can choose from Equals, Not Equals, Equals Ignore Case, Not Equals Ignore Case, In, and Contains. Use the Contains option when the attribute statement has an array type. You can enter more than one value to be matched by using the In option.

Values
: An attribute value that is used by the comparator to evaluate against the Allow users when attribute name.

You can think of a dynamic rule or trusted profile condition as a key:value pair. The key is what you add in the Allow users when field, and the value is what you enter in the Values field.





 Available comparators for conditions 



Table 1. Available comparators for conditions

 Comparator Description Sample condition 

 Equals Case-sensitive string comparison. Boolean or number values are converted into a string before comparison. primaryGroup Equals “Admins” 
 Not Equals Negated case-sensitive string comparison. Boolean or number values are converted into a string before comparison. primaryGroup NotEquals “Admins” 
 Equals Ignore Case Case-insensitive string comparison. Boolean or number values are converted into a string before comparison. isManager EqualsIgnoreCase “tRuE” 
 Not Equals Ignore Case Negated case-insensitive string comparison. Boolean or number values are converted into a string before comparison. is_teamlead NotEqualsIgnoreCase “TrUe” 
 Contains If the attribute is an array of strings, numbers, or Booleans, Contains determines by using the comparator Equals if the value that is provided is part of the array in the login message. If the attribute is a single string instead, Contains determines whether the value that is provided is contained in the string attribute in the login message. group contains “Admins” 
 In Short notation for multiple Equal operators. Compares the value in the login message attribute with the list of potential values in this rule. Boolean or numbers are converted to a string before comparison. jobRole in [“Manager”,”Director”,”Team-Lead”] 







 Example 

The following table includes values for each of the fields for a dynamic rule or a trusted profile condition.
By default, the service spells out individual characters at the same rate at which it synthesizes text for a language. You can use the parameter to direct the service to spell out individual characters more slowly, in groups of one (singles), two (pairs), or three (triples). For more information, see [Specifying how strings are spelled out](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-synthesis-paramsparams-spell-out-mode).

X-Watson-Metadata (request header, optional string)
: Associates a customer ID with data that is passed with a request. For more information, see [Information security](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-information-security).

X-Watson-Learning-Opt-Out (request header, optional boolean)
:
IBM Cloud

Indicates whether the service logs request and response data to improve the service for future users. To prevent IBM from accessing your data for general service improvements, specify true for the parameter. Opting out directs IBM to write to disk no user data (text or audio) for your request. You can also opt out at the account level. For more information, see [Request logging](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-data-securitydata-security-request-logging).

If you specify an invalid query parameter or JSON field as part of the input to the /v1/synthesize method, the service returns a Warnings response header that describes and lists each invalid argument. The request succeeds despite the warnings.





 Specifying input text 

Both the POST and GET /v1/synthesize methods accept plain input text or text that is annotated with SSML. The two versions differ primarily in how you specify the text that is to be synthesized. The following examples both pass the plain text Hello world.



* The POST /v1/synthesize method accepts input text in the body of the request.
Instead, the resource group ID can be found in the target.resourceGroupId field.
* The reason.reasonCode field is now formatted as an integer (int) instead of string (string).
* The requestData field is now formatted as a JSON object instead of a JSON string.
* The responseData field is now formatted as a JSON object instead of string.
* The target.typeURI values are updated for consistency. All values now have a prefix of containers-kubernetes/ instead of container/. For example, container/cluster is now containers-kubernetes/cluster and container/worker is now containers-kubernetes/worker.







 16 March 2021 

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





 12 March 2021 

Worker node versions
: Worker node fix pack update change log documentation is available for version [1.20.4_1532](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1201204_1532), [1.19.8_1539](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1191198_1539), [1.18.16_1545](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11816_1545), and [1.17.17_1556](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1556).





 10 March 2021 

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





 9 March 2021 

Cluster autoscaler add-on