vania-janet/multiturn-rag-retrieval-data huggingface dataset:
GET /v1/{crn}/zones/{domain_id}/setting/origin_error_page_pass_thru internet-svcs.zones.update internet-svcs.origin-error-page-pass-thru-setting.update 
 Get brotli compression settings. GET /v1/{crn}/zones/{domain_id}/setting/brotli internet-svcs.performance.read internet-svcs.brotli-setting.read 
 Update brotli compression settings. PUT /v1/{crn}/zones/{domain_id}/setting/brotli internet-svcs.performance.update internet-svcs.brotli-setting.update 
 Get Email obfuscation settings. GET /v1/{crn}/zones/{domain_id}/setting/email_obfuscation internet-svcs.security.read internet-svcs.email-obfuscation-setting.read 
 Update Email obfuscation settings. PUT /v1/{crn}/zones/{domain_id}/setting/email_obfuscation internet-svcs.security.update internet-svcs.email-obfuscation-setting.update 
 Get ciphers settings. GET /v1/{crn}/zones/{domain_id}/setting/ciphers internet-svcs.security.read internet-svcs.ciphers-setting.read 
 Update ciphers settings. PUT /v1/{crn}/zones/{domain_id}/setting/ciphers internet-svcs.security.update internet-svcs.ciphers-setting.update 







 Bot Management 



Table 22. Bot Management

 Action Method IAM ACTION AT ACTION 

 Get Bot Management settings. GET /v1/{crn}/zones/{domain_id}/bot_management} internet-svcs.reliability.read internet-svcs.bot-management.read 
 Update Bot Management settings. PUT /v1/{crn}/zones/{domain_id}/bot_management} internet-svcs.reliability.update internet-svcs.bot-management.update 
 Get Bot Analytics Score Source.
Airline: Virgin Atlantic
Departure date: 2019-02-02
Departure time: 21:40
Arrival time: 09:05

The advantage of using this method is that it doesn't matter how often the values in the array change or whether the number of elements in the array increases. As long as each array element contains at least the subset of properties that are referenced by the template, then the expression works.





 JSON Object template example 

In this example, the template context variable is defined as a JSON object that extracts the flight number, and arrival and departure dates and times from each of the flight elements specified in the array in the $flights context variable. You could use this approach to apply standard formatting to flight details for flights that are managed by two different carriers, and who format flight information differently in their web services, for example.

"template": {
"departure": "Flight %e.flight% departs on %e.departure_date% at %e.departure_time%.",
"arrival": "Flight %e.flight% arrives on %e.arrival_date% at %e.arrival_time%."
}

You might want to design your custom client application to read the objects from the returned array, and format the values properly for your chat bot's response. Your dialog node response can return the flight arrival details object as an array by using this expression:

<? $flights.joinToArray($template) ?>

This is the dialog node response:

[
{
"arrival":"Flight DL1040 arrives on 2019-02-03 at 07:00.",
"departure":"Flight DL1040 departs on 2019-02-02 at 16:45."
},
{
"arrival":"Flight DL1710 arrives on 2019-02-02 at 10:19.",
"departure":"Flight DL1710 departs on 2019-02-02 at 07:00."
},
{
"arrival":"Flight DL4379 arrives on 2019-02-03 at 09:05.",
The payload JSON object for a call detail record event contains the following keys:



Keys for the payload object

 Key Type Description 

 primary_phone_number string The phone number that was called. 
 global_session_id string The unique session identifier. 
 failure_occurred Boolean Indicates whether a failure occurred during the call. 
 failure_details string Details about a failure. 
 transfer_occurred Boolean Indicates whether an attempt was made to transfer a call 
 active_calls Number Number of active calls when the call started. 
 x-global-sip-trunk-call-id string The value of the SIP trunk call ID header extracted from the initial SIP INVITE request. The following SIP trunk call ID headers are supported: <br>X-Twilio-CallSid <br>X-SID <br>X-Global-SIP-Trunk-Call-ID 
 call JSON object Contains information about the call. 
 session_initiation_protocol JSON object SIP protocol related details. 
 max_response_milliseconds JSON object Maximum latency for various services used during the call. 
 assistant_interaction_summaries JSON array Details about the Watson Assistant transactions that took place during the call. 
 injected_custom_data JSON object A JSON object that contains a set of key/value pairs. Extracted from the cdr_custom_data context variable. 
 warnings_and_errors JSON array An array of warnings and errors that were logged during the call. 
 realtime_transport_network_summary JSON object When RTCP is enabled, the realtime_transport_network_summary object provides statistics for the inbound stream in the inbound_stream object and statistics for the outbound stream in the outbound_stream object. 



The call object contains the following keys:



Keys for the call object

 Key Type Description 

 start_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the call started. 
 stop_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the call ended. 
 milliseconds_elapsed number Length of the call in milliseconds.
"name": "Root-key-2",
"description": "example-key",
"extractable": false
}
]
}'
Show more



 JSON response 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Bad Request: Key could not be created. Please see reasons for more details.",
"reasons":
{
"code": "BAD_BODY_ERR",
"message": "Invalid body data was passed. Please ensure the data passed had valid formatting with no invalid characters: Only creation of one key per request is supported",
"status": 400,
"moreInfo": "https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}







 Example 3 

This create key request fails because the metadata is empty.

 this request fails because the metadata is empty
$ curl -X POST "https://us-south.kms.cloud.ibm.com/api/v2/keys" -H "authorization: Bearer $ACCESS_TOKEN" -H "bluemix-instance: $KP_INSTANCE_ID" -H "content-type: application/vnd.ibm.kms.key+json" -d '{
"metadata": {},
"resources": [
{
"type": "application/vnd.ibm.kms.key+json",
"name": "Root-key-1",
"description": "example-key",
"extractable": false
}
]
}'
Show more



 JSON response 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
Python packages 

Ensure that your action uses only the packages that are mentioned in the following table. \n While other Python packages might be part of the runtime, they are included only as indirect dependencies of the other listed packages. These unlisted packages are candidates to be removed as soon as they are not required by the referring package.

Python 3.11 packages

Python 3.9 packages

Python 3.7 packages



Table 1. Python 3.11 packages

 Python 3.9 packages 

 beautifulsoup4 
 botocore 
 cassandra-driver 
 ibmcloudant 
 elasticsearch 
 etcd3 
 flask 
 gevent 
 httplib2 
 ibm-cos-sdk 
 ibm_db 
 ibmcloudsql 
 kafka_python 
 lxml 
 numpy 
 pandas 
 pika 
 Pillow 
 psycopg2 
 PyJWT 
 pymongo 
 python-dateutil 
 redis 
 requests 
 scikit-learn 
 scipy 
 scrapy 
 simplejson 
 tornado 
 twisted 
 virtualenv 
 ibm-watson 



For more information about Python 3.11 packages, see [(Details on GitHub)](https://github.com/ibm-functions/runtime-python/blob/master/python3.11/requirements.txt).

For more information about Python 3.9 packages, see [(Details on GitHub)](https://github.com/ibm-functions/runtime-python/blob/master/python3.9/requirements.txt).

For more information about Python 3.7 packages, see [(Details on GitHub)](https://github.com/ibm-functions/runtime-python/blob/master/python3.7/requirements.txt).
For more information, see [IBM.com - IBM Security - SAP Security and GRC Strategy Services](https://www.ibm.com/security/services/security-governance/sap-grc-strategy)



 Procedure to request IBM Security Services for SAP 

To begin with IBM Security Services for SAP, use either:



* Live Chat with IBM Security Sales, by using [IBM.com - IBM Security](https://www.ibm.com/security/services/security-governance/sap-grc-strategy) and click Let's talk in the botttom-left
* [Email with IBM Security Sales](https://www.ibm.com/account/reg/us-en/signup?formid=MAIL-security)





 Procedure to request IBM Security Services for SAP, directly from IBM Cloud for VMware Solutions 

Because of the close collaboration between IBM Cloud for VMware with SAP and IBM Security Services for SAP, the quickest way to use IBM Security Services in combination with SAP workloads on VMware is to:



1. Open the IBM Cloud for VMware Solutions console. Scroll down to the Services section and on the Featured Workload Solutions card click IBM Security Services for SAP.
2. On the IBM Security Services for SAP page, in the Engage IBM Security Services box, provide the requested details, and click Request a consultation.

An IBM Cloud for VMware Solutions representative will contact you by using your IBM Cloud contact information to help you with the solution that you need.
* Verify that Bad actors behavior detection and Request signature detection are selected





1. Set the following under Mitigation Mode:





* Mitigation Mode: Standard





1. Click Save and Next.



8. Under Virtual Server Properties



1. Check Assign Policy to Virtual Server(s).
2. Under Virtual Server select Use Existing.
3. Under Assign Virtual Servers, move the virtual server that you created previously over from Available to Selected.
4. Click Save and Next.



9. Click Deploy.
10. Verify that the configuration is under *Deployed status.
start_timestamp String The time when the call started, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 stop_timestamp String The time when the call ended, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 milliseconds_elapsed Number The duration of the call, in milliseconds. 
 end_reason string The reason the call ended. The possible reasons are as follows:<br><br><br><br> * assistant_transfer<br> * assistant_hangup<br> * caller_hangup<br> * failed<br><br><br> 
 security.media_encrypted Boolean Whether the media was encrypted. 
 security.signaling_encrypted Boolean Whether the SIP signaling was encrypted. 
 security.sip_authenticated Boolean Whether SIP authentication was used to authenticate the caller. 







 session_initiation_protocol 

The session_initiation_protocol object contains the following properties:



Properties of the session_initiation_protocol object

 Property Type Description 

 invite_arrival_timestamp String The time when the INVITE request arrived, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 setup_milliseconds Number The time it took to set up the call, in milliseconds. This is the time between when the initial SIP INVITE request was received and when the final SIP ACK request was received. 
 headers.call_id String The SIP Call-ID header field pulled from the SIP INVITE related to the call. 
 headers.from_uri String The SIP URI from the initial SIP INVITE From header. 
 headers.to_uri String The SIP URI from the initial SIP INVITE To header. 







 assistant_interaction_summaries 

The assistant_interaction_summaries object contains the following properties:



Properties of the assistant_interaction_summaries object

 Property Type Description 

 assistant_id String The unique identifier of the assistant. 
 session_id String The unique identifier of the session.
Key Type Description 

 start_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the call started. 
 stop_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the call ended. 
 milliseconds_elapsed number Length of the call in milliseconds. 
 end_reason string Call end reason: <br>assistant_transfer <br>assistant_hangup <br>caller_hangup <br>failed 
 security.media_encrypted Boolean Indicates whether the media was encrypted. 
 security.signaling_encrypted Boolean Indicates whether the SIP signaling was encrypted. 
 security.sip_authenticated Boolean Indicates whether SIP authentication was used to challenge the authentication of the caller. 



The session_initiation_protocol object contains the following keys:



Keys for the session_initiation_protocol object

 Key Type Description 

 invite_arrival_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the INVITE request arrived. 
 setup_milliseconds number Time it took to set up the call in milliseconds. Specifically, the field shows the time between when the initial SIP INVITE request was received and when the final SIP ACK request was received. 
 headers.call_id string The SIP Call-ID header field pulled from the SIP INVITE related to the call. 
 headers.from_uri string SIP URI from the initial SIP INVITE From field 
 headers.to_uri string SIP URI from the initial SIP INVITE To field 



The assistant_interaction_summaries object contains the following keys:



Keys for the assistant_interaction_summaries object

 Key Type Description 

 assistant_id string The unique identifier of the assistant. 
 session_id string The unique identifier of the session. 
 turns JSON array An array of the Watson Assistant transactions that took place during the conversation. 



The turn object contains the following keys:



Keys for the turn object

 Key Type Description
$ curl -X PUT "https://us-south.kms.cloud.ibm.com/api/v2/instance/policies?policy=dualAuthDelete" -H "authorization: Bearer $ACCESS_TOKEN" -H "bluemix-instance: $KP_INSTANCE_ID" -H "content-type: application/vnd.ibm.kms.policy+json" -d '{
"metadata": {
"collectionType": "application/vnd.ibm.kms.policy+json",
"collectionTotal": 1
},
"resources": [
{
"policy_type": "badName",
"policy_data": {
"enabled": false
}
}
]
}'
Show more



 JSON response 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Bad Request: Instance policy could not be created. Please see reasons for more details.",
"reasons":
{
"code": "BODY_QUERY_PARAM_MISMATCH_ERR",
"message": "Data in body does not match data required by query parameter",
"status": 400,
"moreInfo": "https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}









 3 - Extracting the subject from the bearer... 



 Message 

Extracting the subject from the bearer token failed: Make sure the bearer token passed is the correct one (and correct format) and is allowed to perform requested actions

Reason code: BEARER_SUB_EXTRACTION_ERR





 HTTP status code 

400 - Bad Request
"address": "module.instance_config.ibm_cos_bucket.bad_resource_cos_bucket_missing_all_configuration0]",
"module_address": "module.instance_config",
"mode": "managed",
"type": "ibm_cos_bucket",
"name": "bad_resource_cos_bucket_missing_all_configuration",
"index": 0,
"provider_name": "registry.terraform.io/ibm-cloud/ibm",
"change": {
"actions":
"create"
],
"before": null,
"after": {
"activity_tracking": ],
"allowed_ip": null,
"archive_rule": ],
"cross_region_location": null,
"endpoint_type": "public",
"expire_rule": ],
"force_delete": true,
"key_protect": null,
"metrics_monitoring": ],
"region_location": "us-south",
"retention_rule": ],
"single_site_location": null,
"storage_class": "standard",
"timeouts": null
},
"after_unknown": {
"activity_tracking": ],
"archive_rule": ],
"bucket_name": true,
"crn": true,
"expire_rule": ],
"id": true,
"metrics_monitoring": ],
"resource_instance_id": true,
"retention_rule": ],
"s3_endpoint_private": true,
"s3_endpoint_public": true
},
"before_sensitive": false,
"after_sensitive": {
"activity_tracking": ],
"archive_rule": ],
As each piece of evidence is related to one or more assets, the evidence summarization algorithms discover the relevant evidence based on assets (as opposed to pipelines run IDs in v1).

Evidence is summarized in the CD pipeline, based on the provenance field of each inventory item. For more information, see [Inventory](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-inventory).

The v2 evidence summary is calculated, unless you explicitly opt out by setting skip-v2-summary to 1.

The change management system uses the v1 evidence summary as the basis for the change request, unless you explicitly opt in by setting use-v2-summary to 1.







 v1 evidence collection 

Evidence is organized in the locker on a per-pipeline-run basis, that is, every piece of evidence that was collected in a pipeline run is stored next to each other. This organization makes evidence collection easy when you have a pipeline run ID. However, it's difficult to tell which piece of evidence is relevant for an asset, such as evidence that is related to a docker image. This difficulty is because evidence can span across multiple pipeline runs, such as a CI pipeline, a staging CD pipeline, or a production CD pipeline. For more information, see [v1 evidence format](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-evidencedevsecops-v1-evidence-format).

Because of these difficulties, v1 evidence is superseded by v2.

The v1 evidence collection is the legacy evidence collection. To opt out of v1 evidence collection, see [Turning off legacy v1 evidence collection](https://cloud.ibm.com/docs/devsecops?topic=devsecops-turn-off-v1-evidence).
Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that need to be run to create the Log Analysis instance, the resource Key, and IAM access policy in your account.

./terraform plan
3. Create the resources.

./terraform apply

If the creation fails, check the Event Streams brokers are reachable and the authentication credentials are valid.



Next, you can:



* [Monitor streaming with Activity Tracker](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-streamingstreaming-4).
* [Monitoring streaming by using IBM Cloud Monitoring](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-streaming-monitor).







 Removing the streaming configuration 

Complete the following steps from the directory where you have the terraform script that you use to configure streaming:



1. Initialize the Terraform CLI.

./terraform init
2. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that need to be run to create the Log Analysis instance, the resource Key, and IAM access policy in your account.

./terraform plan
3. Delete the configuration.

./terraform destroy
The Terraform execution plan summarizes all the actions that need to be run to create the Log Analysis instance, the resource Key, and IAM access policy in your account.

./terraform plan
3. Create the resources.

./terraform apply



Next, you can:



* [Monitor archiving with Activity Tracker](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-archiving-la-monitor).
* [Monitoring archiving by using IBM Cloud Monitoring](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-archiving-monitor).







 Removing the archiving configuration 

To remove the archiving configuratoon, complete the following steps from the directory where you have the terraform script that you use to configure archiving:



1. Initialize the Terraform CLI.

./terraform init
2. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that need to be run to create the Log Analysis instance, the resource Key, and IAM access policy in your account.

./terraform plan
3. Delete the configuration.

./terraform destroy
If the LPAR is not authenticated to access the internet, the command returns an error message. For information on troubleshooting SUMA error messages, see [Troubleshooting SUMA error messages](https://www.ibm.com/support/knowledgecenter/ssw_aix_72/install/serv_update_mgt.htmlserv_update_mgt__section_troubleshoot_suma).

0500-013 Failed to retrieve list from fix server.

Complete the following steps to configure SUMA to use the proxy settings:



1. Ensure that the bos.ecc_client.rte file set is installed on the AIX LPAR by running the following command, lslpp -h bos.ecc_client.rte.
2. Determine if the config_conn_path command is available in the bos.ecc_client.rte file set by running the following command, lslpp -w /usr/ecc/bin/config_conn_path.
3. Configure your proxy settings by completing the following steps:



1. Run the smit srv_conn command.
2. Select Create/Change Service Configuration and press Enter.
3. Select Create/Change Primary Service Configuration and press Enter.
4. Set the following fields in the SMIT interface:



Configuring proxy settings:

Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
Connection type [HTTP_Proxy]
Test service configuration [Yes]

If type is DIRECT_INTERNET, no entry required.

If type is HTTP_PROXY,
IP address [xx.xx.xx.xx]
Port number [5026]
Authentication user ID []
Authentication password requested interactively.

Where, xx.xx.xx.xx is the IP address of the proxy and 5026 is the port number that is used to connect to the proxy settings. When you press Enter, a test connection determines whether the AIX LPAR is authenticated to access the internet by using the proxy settings.
"moreInfo": "https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}









 3 - Extracting the subject from the bearer... 



 Message 

Extracting the subject from the bearer token failed: Make sure the bearer token passed is the correct one (and correct format) and is allowed to perform requested actions

Reason code: BEARER_SUB_EXTRACTION_ERR





 HTTP status code 

400 - Bad Request

The HTTP 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

The client should not repeat this request without modification.





 Context 

The identify and access management (IAM) access token, or format, was invalid. If this is a curl request then the authorization header needs to be set using this format:

-H "authorization: Bearer $ACCESS_TOKEN"

Depending on which platform (Linux, Mac, Windows) or shell (bash, sh, zsh) you are using, you need to be aware of using single versus double quotes. Some systems will not interpret variables inside single quotes. For example, ('Bearer $ACCESS_TOKEN') may not replace $ACCESS_TOKEN with the value.

Make sure you specify a valid IAM token. You may need to login (again) if your token has expired. Here are a few lines of command line interface (CLI) code to login and set the access token.

 login with single sign on (sso)
$ ibmcloud login --sso

 set the region (-r) and resource group (-g)
$ ibmcloud target -r us-south -g Default

 set the ACCESS_TOKEN environment variable (with Bearer)
$ export ACCESS_TOKEN=ibmcloud iam oauth-tokens | grep IAM | cut -d : -f 2 | sed 's/^ //'

 show the access token
$ echo $ACCESS_TOKEN