vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI
* CLI
* API







 Listing and getting details of permitted networks 

List all permitted networks and get the details of a permitted network in your linked zone by using the UI, CLI, or API.



 Getting the details of a permitted network using the UI 

To get the details of a permitted network using the UI, take the following steps:



1. Navigate to the Zones section of your DNS Services instance, then select the Linked zones tab.
2. Click the link in the Zone name column of the linked zone you want to view.



In the Linked zone details page, the Permitted networks tab lists the details of the permitted network.





 Listing all permitted networks using the CLI 

To list a permitted network using the CLI, run the following command:

ibmcloud dns cross-account linked-zones [-i, --instance INSTANCE] [--output FORMAT]

Where:



* -i, --instance value is the instance name or ID. If not set, the context instance specified by ibmcloud dns instance-target INSTANCE is used.
* --output value specifies the output format. Currently, json is the only supported format.







 Getting the details of a permitted network using the CLI 

To get the details of a permitted network using the API, run the following command:

ibmcloud dns cross-account linked-zone LINKED_ZONE_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:



* LINKED_ZONE_ID is the ID of permitted network.
* -i, --instance value is the instance name or ID. If not set, the context instance specified by ibmcloud dns instance-target INSTANCE is used.
* --output value specifies the output format. Currently, json is the only supported format.







 Listing a permitted network using the API 

To list all linked zones using the API, follow these steps:



1. Set up your API environment with the correct variables.
2. Store the following values in variables to be used in the API command:



* INSTANCE_ID, which is the unique identifier of a service instance.
IDS_URL The URL for the current pipeline. 
 IDS_VERSION The number for the build that is being deployed or the SCM identifier. This property is available only in deploy jobs. 
 JOB_NAME The unique job ID in the context of the current pipeline. 
 PIPELINE_ARTIFACT_URL The URL that you can use to download the artifacts of the current Build job after the job completes. You must use a valid Bearer token to access the artifacts. 
 PIPELINE_INITIAL_STAGE_EXECUTION_ID The unique ID for the run of the pipeline. 
 PIPELINE_IMAGE_URL The URL of the container image that is built by a Container Registry build job. This property is present only in a job whose stage input is a Container Registry build job. This input Container Registry build job must explicitly export PIPELINE_IMAGE_URL, for example: export PIPELINE_IMAGE_URL=$REGISTRY_URL/$REGISTRY_NAMESPACE/$IMAGE_NAME:$BUILD_NUMBER. 
 PIPELINE_KUBERNETES_CLUSTER_NAME The name of the Kubernetes cluster that is selected in the current job. 
 PIPELINE_LOG_URL The URL that you can use to download the log file of the current job after the job completes. You must use a valid Bearer token to access the log files. 
 PIPELINE_STAGE_INPUT_JOB_ID The ID of the job that is input for the current stage. 
 PIPELINE_STAGE_INPUT_REV The revision of the input for the current stage. 
 PIPELINE_TRIGGERING_USER The current user for the pipeline job 
 TASK_ID The unique ID of the job's current run. 
 TMPDIR A directory location where temporary files are stored. 
 WORKSPACE The path for the current working directory. 







 Runtime and tool properties 

The following table lists and describes each of the runtime and tool environment properties that are available by default in pipeline environments.



Table 2. Runtime and tool environment properties

 Environment Property Description 

 ANT_HOME The path to Apache Ant 1.9.2. 
 ANT_JAVA8_HOME The path to a 1.10+ version of Apache Ant that requires Java 8. 
 GRADLE_HOME The path to Gradle 1.11.
You can also use the full names that are prefixed with the Kubernetes Config Context, which can be determined with the project current command. This value is optional.

--user, -u
: The user ID (UID) that is used to run the application. This value overrides any user ID that is set in the application Dockerfile. The ID must conform to the operating system requirements of the container. This value is optional. The default value is 0.

--visibility, -v
: The visibility for the application. Valid values are public, private and project. Setting a visibility of public means that your app can receive requests from the public internet or from components within the Code Engine project. Setting a visibility of private means that your app is not accessible from the public internet and network access is only possible from other IBM Cloud using Virtual Private Endpoints (VPE) or Code Engine components that are running in the same project. Visibility can only be private if the project supports application private visibility. Setting a visibility of project means that your app is not accessible from the public internet and network access is only possible from other Code Engine components that are running in the same project. This value is optional.

--wait, -w
: Create the application and wait for the application to be ready. If you specify the --wait option, the application create waits for a maximum time in seconds, as set by the --wait-timeout option, for the application to become ready. If the application is not ready within the specified wait-timeout period, the application create fails. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the application to be ready. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

ibmcloud ce application create --name myapp --image icr.io/codeengine/hello





 Example output 

Creating application 'myapp'...
[...]
Follow Steps 2 - 6 in [Connecting to a VNC console by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-connect-to-ESXi-bare-metal-serversconnect-to-vnc-console-cli) to connect to the VNC console.









 Logging in to ESXi DCUI 



1. Open the ESXi DCUI in a VNC console.
2. Press F2 from the DCUI main page to access the System Customization menu.
3. In the open window, enter the account name and password, then press Enter.



You can reset the password in the Configure Password section.





 Enabling SSH for the bare metal server (optional) 

By default, you don't have SSH access to the ESXi bare metal server. You can enable SSH access in DCUI by using one the following options.



 Enabling SSH from the DCUI 



1. Press F2 from the DCUI main page to access the System Customization menu. You are prompted to enter your account name and password.
2. From the System Customization menu, select Troubleshooting Options.
3. Under the Troubleshooting Mode Options menu, select Enable SSH and toggle it on.
4. SSH is enabled. You can now access DCUI by using SSH protocol.







 Enabling SSH by using a script 

You can also enable SSH when you provision a bare metal server by passing in the following script content as user data:

vim-cmd hostsvc/enable_ssh
vim-cmd hostsvc/start_ssh







 Connecting to a serial console 

You can optionally use a serial console to access ESXi DCUI. You must first manually switch to the serial console mode by using the following steps:



1. Reboot the bare metal server.
: The length of time in seconds to wait for the project to be restored. This value is required if the --wait option is specified. This value is ignored if the --no-wait option is specified. The default value is 600.





 Example 

This example restores the myproject project that is in soft deleted status to an active state. Use the project list command to display a list of all projects with their status.

ibmcloud ce project restore --name myproject





 Example output 

Restoring project 'myproject'...
OK







 ibmcloud ce project select 

Select a project as the current context. The project must be in active status before it can be selected.

ibmcloud ce project select (--name PROJECT_NAME | --id PROJECT_ID) [--endpoint ENDPOINT] [--kubecfg] [--quiet]



 Command Options 

--endpoint, -e
: The endpoint for the project. Valid values are public and private. If the --endpoint option is not explicitly specified, the behavior is determined by the system. If the IBM Cloud CLI is connected to private.cloud.ibm.com, the Code Engine project behaves as if --endpoint is private. If the IBM Cloud CLI is connected to cloud.ibm.com, the Code Engine project behaves as if --endpoint is public. This value is optional.

--id, --guid
: The ID of the project. This value is required if --name is not specified.

--kubecfg, -k
: Append the project to the Kubernetes configuration file. You can override the default Kubernetes configuration file by setting the KUBECONFIG environment variable. This value is optional. The default value is false.

--name, -n
: The name of the project. This value is required if --id is not specified.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example
If the user specifies Hello now as the input, then the @sys-date and @sys-time entities are triggered by the now reference. The entities object is an array, but because the expression is included in text, the entities are returned in String format, like this:

The entities are 2018-02-02, 14:34:56.

If you do not include text in the response, then an array is returned instead. For example, if the response is specified as an expression only, not surrounded by text.

<? entities ?>

The entity information is returned in its native data type, as an array.

[
{
"entity":"sys-date","location":6,9],"value":"2018-02-02","confidence":1,"metadata":{"calendar_type":"GREGORIAN","timezone":"America/New_York"}
},
{
"entity":"sys-time","location":6,9],"value":"14:33:22","confidence":1,"metadata":{"calendar_type":"GREGORIAN","timezone":"America/New_York"}
}
]

As another example, the following $array context variable is an array, but the $string_array context variable is a string.

{
"context": {
"array": [
"one",
"two"
],
"array_in_string": "this is my array: $array"
}
}

If you check the values of these context variables in the Try it out pane, you will see their values specified as follows:

$array : ["one","two"]

$array_in_string : "this is my array: ["one","two"]"

You can subsequently perform array methods on the $array variable, such as <? $array.removeValue('two') ?>,but not the $array_in_string variable.
This value is optional. The default value is false.

--registry-secret, --rs
: The name of the registry secret. The registry secret is used to authenticate with a private registry when you download the container image. This value is optional.

--registry-secret-clear, --rsc
: Clear the registry secret. This value is optional. The default value is false.

--request-timeout, --rt, --timeout, -t
: The amount of time in seconds that can pass before requests made to the application must succeed or fail. This value is optional. The default value is 0.

--rn, --revision-name
: The name of the revision. Use a name that is unique within the application.



* The name can contain lowercase letters, numbers, and hyphens (-).
* The name must end with a lowercase alphanumeric character.
* The fully qualified revision name must be in the format, Name_of_application-Name of revision.
* The fully qualified revision name must be 63 characters or fewer.



This value is optional.

--service-account, --sa
: The name of the service account. A service account provides an identity for processes that run in an instance. For built-in service accounts, you can use the shortened names manager, none, reader, and writer. You can also use the full names that are prefixed with the Kubernetes Config Context, which can be determined with the project current command. This value is optional.

--service-account-clear, --sac
: Clear the service account. This value is optional. The default value is false.

--user, -u
: The user ID (UID) that is used to run the application. This value overrides any user ID that is set in the application Dockerfile. The ID must conform to the operating system requirements of the container. This value is optional. The default value is 0.

--visibility, -v
: The visibility for the application.
The registry secret is used to authenticate with a private registry when you download the container image. This value is optional.

--request-timeout, --rt, --timeout, -t
: The amount of time in seconds that can pass before requests made to the application must succeed or fail. This value is optional. The default value is 300.

--rn, --revision-name
: The name of the revision. Use a name that is unique within the application.



* The name can contain lowercase letters, numbers, and hyphens (-).
* The name must end with a lowercase alphanumeric character.
* The fully qualified revision name must be in the format, Name_of_application-Name of revision.
* The fully qualified revision name must be 63 characters or fewer.



This value is optional.

--scale-down-delay, --sdd
: The amount of time in seconds that must pass at reduced concurrency before the application is scaled down. An increase of the number of concurrent requests causes an application to scale up. If the number of requests drops (reduced concurrency), the specified amount of time for this option determines how long the reduced concurrency needs to persist, before the application is scaled down. By default, the application will be scaled down immediately, if reduced concurrency is detected. This value is optional. The default value is 0.

--service-account, --sa
: The name of the service account. A service account provides an identity for processes that run in an instance. For built-in service accounts, you can use the shortened names manager, none, reader, and writer. You can also use the full names that are prefixed with the Kubernetes Config Context, which can be determined with the project current command. This value is optional.

--user, -u
: The user ID (UID) that is used to run the application. This value overrides any user ID that is set in the application Dockerfile. The ID must conform to the operating system requirements of the container. This value is optional. The default value is 0.
--service-account, --sa
: The name of the service account. A service account provides an identity for processes that run in an instance. For built-in service accounts, you can use the shortened names manager, none, reader, and writer. You can also use the full names that are prefixed with the Kubernetes Config Context, which can be determined with the project current command. This value is optional.

--service-account-clear, --sac
: Clear the service account. This value is optional. The default value is false.

--user, -u
: The user ID (UID) that is used to run the application. This value overrides any user ID that is set in the application Dockerfile. The ID must conform to the operating system requirements of the container. This value is optional. The default value is 0.

--visibility, -v
: The visibility for the application. Valid values are public, private and project. Setting a visibility of public means that your app can receive requests from the public internet or from components within the Code Engine project. Setting a visibility of private means that your app is not accessible from the public internet and network access is only possible from other IBM Cloud using Virtual Private Endpoints (VPE) or Code Engine components that are running in the same project. Visibility can only be private if the project supports application private visibility. Setting a visibility of project means that your app is not accessible from the public internet and network access is only possible from other Code Engine components that are running in the same project. This value is optional.

--wait, -w
: Update the application and wait for the application to be ready. If you specify the --wait option, the application update waits for a maximum time in seconds, as set by the --wait-timeout option, for the application to become ready. If the application is not ready within the specified --wait-timeout period, the application create fails. This value is optional. The default value is true.

--wait-timeout, --wto
: The length of time in seconds to wait for the application to be updated.
This prepends "EXTRA_LD_LIBRARY_PATH" to "LD_LIBRARY_PATH", ensuring that this is the first path to the .so file that is searched.

If your custom library is a JAR file and you need it to be accessible on the Spark classpath, you must specify the JAR file in the extra classpath for driver/executor depending on where you require the JAR file. For example, to add it in front of the driver classpath, add the following property, where the library set name is java_library:

"spark.driver.extraClassPath":"/home/spark/shared/user-libs/java_library/custom/"

If your custom library is a certificate file, for example a self signed ICD Postgres certificate, you can specify it in the connection URL in the following way:

sslrootcert=/home/spark/shared/user-libs/customize_integration_custom_lib/custom/postgres.cert

For details, see [Using IBM Cloud Databases for PostgreSQL as external metastore](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-postgresql-external-metastore).

If your custom library is a configuration file, it is made available to the Spark drivers and executors automatically.





 Example of customization script with a multi file download 

The parameters, and the script mentioned in the previous section are just a sample. You can implement additional logic if you need, like for downloading a directory or multiple files or downloading from different source, and so on.

For example, to download multiple files from a directory on Cloud Object Storage, see [Sample script](https://github.com/IBM-Cloud/IBM-Analytics-Engine/tree/master/ae-serverless/customization/multi-file-libraryset-example).
Schematics Policy list flags

 Flag Required / Optional Description 

 --profile or -r Optional Geographic region supported by Schematics service such as, us-south, us-east, eu-de, eu-gb. 
 --limit or -l Optional Maximum number of policies to list. Ignored if a negative number is set. The number must be a positive integer between 1 and 200. The default value is -1. 
 --offsetor -m Optional Offset in list. Ignored if a negative number is set. The default value is -1. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 



Example

ibmcloud schematics policy list





 ibmcloud schematics policy update 

Update the information of an existing policy by using policy ID. Changes are applied to the description by running the ibmcloud schematics policy update command.

Syntax

ibmcloud schematics policy update --id POLICY_ID [--kind POLICY_KIND] [--description DESCRIPTION] [--resource-group RESOURCE_GROUP] [--tags TAGS] [--file FILE] [--output OUTPUT]



Schematics policy update flags

 Flag Required / Optional Description 

 --id or -i Required ID of the policy. 
 --kind or -k Optional Policy kind for managing and deriving policy decision. Supported is agent_assignment_policy. 
 --description or -d Optional The description of Schematics customization policy. 
 --resource-group or -r Optional Resource group name or ID for the policy. 
 --tags or -t Optional Policy tags. This flag can be used multiple times to search for and locate agent policies faster. 
 --file or -f Optional Path to the JSON file containing the definition of the policy. 
 --output or -o Optional Specify output format, only JSON is supported. 



Example

ibmcloud schematics policy update --id policy-msk.soP.5c65 --description PolicyDescriptionUpdated
POLICY DETAILS
Name ID Description Kind Resource Group CRN Target Tags
* For more information about these methods, see [Listing information about models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-list).
* For more information about support for acoustic model customization, see [Language support for customization](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-support).







 22 October 2021 

Defect fix: Address asynchronous HTTP failures
: Defect fix: The asynchronous HTTP interface failed to transcribe some audio. In addition, the callback for the request returned status recognitions.completed_with_results instead of recognitions.failed. This error has been resolved.





 6 October 2021 

Updates to Czech and Dutch next-generation models
: The following next-generation language models have changed as indicated:



* The Czech telephony model, cs-CZ_Telephony, is now generally available (GA). The model continues to support low latency.
* The Belgian Dutch telephony model, nl-BE_Telephony, has been updated for improved speech recognition. The model continues to support low latency.
* The Netherlands Dutch telephony model, nl-NL_Telephony, is now GA. In addition, the model now supports low latency.



For more information about all available next-generation language models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

New US HIPAA support for Premium plans in Dallas location
: US Health Insurance Portability and Accountability Act (HIPAA) support is now available for Premium plans that are hosted in the Dallas (us-south) location. For more information, see [Health Insurance Portability and Accountability Act (HIPAA)](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-information-securityhipaa).





 16 September 2021 

New beta Czech and Netherlands Dutch next-generation models
}

This expression first gets the current date in milliseconds (since January 1, 1970, 00:00:00 GMT). It also calculates the number of milliseconds in 7 days. (The (2460601000L) represents one day in milliseconds.) It then adds 7 days to the current date. The result is the full date of the day that falls a week from today. For example, Fri Jan 26 16:30:37 UTC 2018. Note that the time is in the UTC time zone. You can always change the 7 to a variable ($number_of_days, for example) that you can pass in. Just be sure that its value gets set before this expression is evaluated.

If you want to be able to subsequently compare the date with another date that is generated by the service, then you must reformat the date. System entities (@sys-date) and other built-in methods (now()) convert dates to the yyyy-MM-dd format.

{
"context": {
"week_from_today": "<? new Date(new Date().getTime() +
(7 * (2460601000L))).format('yyyy-MM-dd') ?>"
}
}

After reformatting the date, the result is 2018-01-26. Now, you can use an expression like @sys-date.after($week_from_today) in a response condition to compare a date specified in user input to the date saved in the context variable.

The following expression calculates the time 3 hours from now.

{
"context": {
"future_time": "<? new Date(new Date().getTime() + (3 * (60601000L)) -
(5 * (60601000L))).format('h:mm a') ?>"
}
}

The (60601000L) value represents an hour in milliseconds. This expression adds 3 hours to the current time.