vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For example, you can enable the NGINX PROXY protocol so that client connection information is passed in request headers to ALBs.
* Adds the optional --endpoint option to the ibmcloud ks cluster config command to specify a type of endpoint for the cluster context, such as the cluster's private cloud service endpoint.
* Updates the help text in various languages.
* Updates the Go version to 1.15.6.







 Version 1.0.197 

Version 1.0.197 of the CLI was released on 18 November 2020.



* Adds a warning message to the ibmcloud ks cluster config command about temporary kubectl command failures due to RBAC synchronization.
* Ensures that incident IDs are returned with 500-level messages.
* In ibmcloud ks cluster storage commands, the cluster name is now accepted in the --cluster option in addition to the cluster ID.
* Updates the output of the ibmcloud ks ingress alb migrate command to be more readable.
* Updates the help text in various languages.







 Version 1.0.178 

Version 1.0.178 of the CLI was released on 6 October 2020.



* Updates the Go version to 1.15.2.
* Updates the help text in various languages.







 Version 1.0.171 

Version 1.0.171 of the CLI was released on 24 September 2020.



* Shifts all existing ibmcloud ks cluster feature commands into the [ibmcloud ks cluster master](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_master_pse_enable) subcategory.
* Adds the cluster Status, the Pod Subnet, and the Service Subnet fields to the output of the ibmcloud ks cluster get command.
* Updates the help text in various languages.







 Version 1.0.157 

Version 1.0.157 of the CLI was released on 24 August 2020.

Added commands: The following commands are added.
* CONFIG_FILE with the path of the configuration file.



Using this tool, you can also display details like the current positions of the consumers, their lag, and client-id for each partition for a group. For example:

kafka-consumer-groups.sh --bootstrap-server BOOTSTRAP_ENDPOINTS --command-config CONFIG_FILE --describe --group GROUP --timeout 60000

Replace GROUP in the example with the group name that you want to retrieve details for.

See the following sample output from running the kafka-consumer-groups tool:

GROUP           TOPIC   PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG   CONSUMER-ID    HOST          CLIENT-ID
consumer-group-1 foo        0          264           267         3       client-1-abc example.com client-1
consumer-group-1 foo        1          124           124         0       client-1-abc example.com    client-1
consumer-group-1 foo        2          212           212         0       client-2-def example.com    client-2

From the example, you can see consumer group consumer-group-1 has two consumer members that consume messages from topic foo with three partitions. It also shows that the consumer client-1-abc that is consuming from partition 0 is three messages behind because the current offset of the consumer is 264 but the offset of the last message on partition 0 is 267.





 Topics 

You can use the kafka-topics tool with Event Streams. Ensure that you use V2.8 of the tool, because it does not require Zookeeper access.

A scenario where you might want to use kafka-topics is to find out information about your topics and their configuration in an existing cluster so that you can re-create them in a new cluster. You can use the information that is output from kafka-topics to create the same named topics in the new cluster.
Configuring Vyatta 5400 

You can configure your Vyatta 5400 using the procedure here.

You must configure the public virtual LAN (VLAN) 1224, which is now associated and routed, before it can pass traffic. Two pieces of information are needed to complete the configuration:



* The public-side bond of the Brocade 5400 vRouter appliance
* The default gateway of 1224



It is the public-side VLAN where the compute option is located, not the Brocade 5400 vRouter appliance's public VLAN.



 In the SoftLayer portal 

Follow these steps:



1. Within the SoftLayer web portal, in Devices, locate the bond on the Configuration tab for the Brocade 5400 vRouter device. Assume that eth1=bond1 on your device.
2. Select Network > IP Management > VLANs from the web portal to find the default gateway for VLAN 1224.
3. Click your VLAN in the list, then click the Subnet where you see your gateway. Make a note of the mask Classless Inter-Domain Routing (CIDR) details located after the slash.







 Configuring the private VLAN using the CLI 

There are two command modes in the command-line interface (CLI): operational and configuration.

Operational mode provides access to operational commands for:



* Displaying and clearing information
* Enabling and disabling debugging
* Configuring terminal settings
* Loading and saving configuration
* Restarting the system



Configuration provides access to commands for:



* Creating
* Modifying
* Deleting
* Committing
* Showing configuration information
* Navigating through the configuration hierarchy



When you log on to the system, the system is in operational mode. You must switch to configuration mode for the commands.

You can tell which mode that you are in based on the prompt. You are in operational mode if the prompt is #, and configuration mode if the prompt is $.

Follow these steps to configure the private VLAN by using the CLI.
: Autolearning is now generally available for all languages and enabled by default in all new assistants. Your assistant can learn from interactions with your customers and improve responses. For more information, see [Using autolearning to improve assistant responses](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-autolearn).

See which actions use a specific variable
: The Variables page now includes a new Actions count column. You can click on the number in the column to see which actions use a variable. For more information, see [Creating a session variable](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-manage-infocreate-session-variable).

Expression editor character limit increased
: The character limit in the expression editor has increased from 1,024 to 4,000. For more information, see [Writing expressions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-expressions).





 15 June 2023 

New API version
: The current API version is now 2023-06-15. This version introduces the following changes:



* Invalid expressions in callouts to client actions are now replaced with empty strings
* The default value of async_callout changes from true to false



Custom extensions now support OAuth 2.0 authentication
: You can now use OAuth 2.0 authentication when you build and add custom extensions. For more information, see [Building a custom extension](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-build-custom-extension) and [Adding an extension to your assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-add-custom-extension).





 8 June 2023 

Edit step titles
: You can now add and edit titles for each step, which can help you more easily identify what a step does in an action.
This pause might be to allow time for a request to complete, or simply to mimic the appearance of a live agent who might pause between responses. The pause can be of any duration from 1 to 10 seconds. For more information, see [Pause response](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-respondrespond-pause-response).





 17 November 2022 

Use unrecognized requests to get action recommendations
: In Analyze, the new Recognition page lets you view groups of similar unrecognized requests. You can use the requests as example phrases in new or existing actions to address questions and issues that aren't being answered by your assistant. For more information, see [Use unrecognized requests to get action recommendations](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-analytics-recognition).





 15 November 2022 

Journeys
: Beginning with web chat version 6.9.0, you can now create journeys to guide your customers through tasks they can already complete on your website. A journey is an interactive, multipart response that can combine text, video, and images, presented in sequence in a small window superimposed over your website.

Journeys are available as a beta feature. For more information, see [Guiding customers with journeys](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-journeys).





 10 November 2022 

Dynamic options
: Within the options customer response, you can use the dynamic setting to generate the list when you need to ask questions that are potentially different each time and for each customer. You need to set up a list variable as the source of the options. For more information, see [Dynamic options](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-dynamic-options).

Extension inspector
: You can use the new extension inspector in the action editor Preview pane to debug problems with custom extensions. The extension inspector shows detailed information about what data is being sent to and returned from an external API.
Terraform v0.14 introduced new sensitive attribute in the variable metadata configuration. Schematics do not detect this sensitive attribute. Users should continue to use the sensitive checkbox in the IBM Cloud Schematics console, and use secure flag in the API payload. Schematics already supports masking the sensitive updated values. Terraform v0.14 introduced a lock file for versions with the name .terraform.lock.hcl. This file is created during terraform init. If you use .terraform.lock.hcl file in the Terraform commands, the versions stored in .terraform.lock.hcl file are used. Schematics doesn't support this feature. Schematics will not store this file for subsequent actions.







 February 2021 

Review the release notes for February 2021.



 25 February 2021 

Schematics supports the ability to store the user-defined file
: IBM Cloud Schematics supports the ability to store the user-defined file for running the subsequent Terraform commands. For more information, see [store user-defined files in Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-general-faqpersist-file).

Allowed file extensions in Schematics
: Allowed and blocked file extensions support during cloning. For more information, see [allowed and blocked file extensions](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqclone-file-extension).

Schematics CLI plug-in and commands support in CLI documentation
: IBM Cloud Schematics [command-line plug-in to install](https://cloud.ibm.com/docs/cli?topic=schematics-cli-plugin-schematics-cli-reference), and [view command-line commands](https://cloud.ibm.com/docs/cli?topic=schematics-cli-plugin-schematics-cli-reference) in the CLI documentation.





 12 February 2021 

Ansible open beta release
: Updated the CLI plug-in change log page for the [release of version 1.0.454](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).







 September 2022 



 23 September 2022 

Added support for remote workers
: You can now assign workload hosts to a location from a single provider or from multiple providers. See [Setting up a Satellite location with remote workers](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-multi-infra).





 21 September 2022 

CLI change log
: Updated the CLI plug-in change log page for the [release of version 1.0.452](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).





 12 September 2022 

CLI change log
: Updated the CLI plug-in change log page for the [release of version 1.0.446](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).





 6 September 2022 

New! Location overview information.
: Learn more about planning and creating a location with the new location overview information. See [Understanding Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-location-host).







 August 2022 



 31 August 2022 

New! You can now create Red Hat CoreOS enabled Satellite locations in the Sao Paulo (sao, br-sao) region.
: To create a Red Hat CoreOS enabled location in the Sao Paulo region, see [Understanding Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).





 23 August 2022 

New! You can now create Red Hat CoreOS enabled Satellite locations in the Osaka (osa, jp-osa) region.
: Updated the CLI plug-in change log page for the [release of version 1.0.433](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).





 3 August 2022 

RHEL 8 is now supported.
: You can now select RHEL8 as your operating system. For more information, see [Planning your operating system](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).

New! Check out the Satellite Config tutorial.
: Learn about how to integrate Satellite Config with a Continuous Delivery toolchain to deploy your apps. For more information, see [Deploying Kubernetes resources to clusters with Continuous Delivery and Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-sat_toolchain_tutorial).





 2 August 2022 

New! You can now create Red Hat CoreOS enabled Satellite locations in the Toronto (tor, ca-tor) region.
: To create a Red Hat CoreOS enabled location in the Toronto region, see [Understanding Satellite locations](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os).







 July 2022 



 22 July 2022 

New! Beta support for the VMware CSI driver template
: You can use the VMware CSI driver template to create persistent storage for stateful apps that run in Satellite clusters. For more information, see the [VMware CSI driver template documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driver).





 15 July 2022 

New information about using a custom Network Time Protocol (NTP) server
: You can now define a custom NTP server for your RHCOS hosts. For more information, see the [Specifying a custom Network Time Protocol (NTP) server](https://cloud.ibm.com/docs/satellite?topic=satellite-config-custom-ntp).
To find out more about your key rotation options in Key Protect, check out [Comparing your key rotation options](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-rotationcompare-key-rotation-options).





 20 March 2019 

Announcing secure import of encryption keys
: Enable the secure import of encryption keys to the cloud by creating transport encryption keys for your Key Protect service. For more information, see [Bringing your encryption keys to the cloud](https://cloud.ibm.com/docs/key-protect?topic=key-protect-importing-keys).







 February 2019 



 13 February 2019 

Key Protect deprecates Cloud Foundry instances:
: Key Protect instances that were provisioned before 15 December 2017 are running on a legacy infrastructure that is based on Cloud Foundry. This legacy Key Protect service will be decommissioned on 15 May 2019. If you have active production keys in an older Key Protect instance, ensure that you migrate the keys to a new instance by 15 May 2019 to avoid losing access to your encrypted data. You can check to see whether you're using a legacy instance by navigating to your resource list from the [IBM Cloud console](https://cloud.ibm.com/login/). If your Key Protect instance is listed in the Cloud Foundry Services section of the IBM Cloud resource list, or if you're using a bluemix.net API endpoint to target operations for the service, you're using a legacy instance of the Key Protect. After 15 May 2019, the legacy endpoint will no longer be accessible, and you won't be able to target the service for operations.

Need help with migrating your encryption keys into a new Key Protect instance? For detailed steps, check out the [migration client in GitHub](https://github.com/IBM-Cloud/kms-migration-client).







 December 2018 



 19 December 2018 

Key Protect has updated endpoints:
: To align with IBM Cloud's new unified experience, Key Protect has updated the base URLs for its service APIs. You can now update your applications to reference the new cloud.ibm.com endpoints.
You can use the kafka-topics tool with Event Streams. Ensure that you use V2.8 of the tool, because it does not require Zookeeper access.

A scenario where you might want to use kafka-topics is to find out information about your topics and their configuration in an existing cluster so that you can re-create them in a new cluster. You can use the information that is output from kafka-topics to create the same named topics in the new cluster. For more information about how to create topics, see [Using the administration Kafka Java client API](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-kafka_java_api) or the [ibmcloud es topic-create command](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-cli_referenceibmcloud_es). Alternatively, you can also use the IBM Event Streams console.

See the following sample output from running the kafka-topics tool:

bin/kafka-topics.sh --bootstrap-server kafka03-prod01.messagehub.services.us-south.bluemix.net:9093 --command-config vcurr_dal06.properties --describe

Topic:sample-topic	PartitionCount:3	ReplicationFactor:3	 Configs:min.insync.replicas=2,unclean.leader.election.enable=true,retention.bytes=1073741824,segment.bytes=536870912,retention.ms=86400000
Topic: sample-topic    Partition: 0    Leader: 0    Replicas: 0,2,1 Isr: 0,2,1
Topic: sample-topic    Partition: 1    Leader: 1    Replicas: 1,2,0	 Isr: 0,2,1
Topic: sample-topic    Partition: 2    Leader: 2    Replicas: 2,1,0	 Isr: 0,2,1
Topic:testtopic	 PartitionCount:1	 ReplicationFactor:3
expires: Tue, 15 Sep 2020 07:54:31 GMT
date: Tue, 15 Sep 2020 07:54:31 GMT

<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>

You do not have permission to access "http://xxxx;" on this server.<P>
Reference 18.9df02817.1600156471.bf3f7f1
</BODY>
</HTML>
Show more





 Where I can find the Akamai CNAME? 

You can find the Akamai CNAME in the following ways:



* From the console, you can click into the CDN domain, and view the Akamai CNAME in Overview > Details.
* From the API, use the [list domain mapping by uniqueid](https://cloud.ibm.com/docs/CDN?topic=CDN-cdn-api-referencelistdomainmappingbyuniqueid) or the [list all domain mapping](https://cloud.ibm.com/docs/CDN?topic=CDN-cdn-api-referencelistdomainmappings) commands to get the Akamai CNAME.







 Why is the Akamai CNAME empty or shown as -? 

If you are using wildcard CDN mapping, there's no Akamai CNAME associated. If you just created the SAN HTTPS mapping, the Akamai CNAME can only be generated when the mapping is in the Domain validation required status. That's because Akamai can only generate the Akamai CNAME when the certificate is selected. Before the Domain validation required status is active, the - character is shown as the Akamai CNAME value.
IBM Cloud Schematics CLI 

Run these commands when you want to automate your IBM Cloud Schematics Workspaces, Actions, Jobs, resources.



 Prerequisites 



* Set up your [CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cli).
* Install [Schematics plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin).



Be sure to keep your CLI up-to-date so that you can use the current released commands and their options. For more information about the current command-line version releases, see [Command-line version history](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases).





 Actions commands 

Review the commands that you want to create, update, list, delete, and work with your Schematics Actions.



 Inventory host groups 

IBM Cloud Schematics supports inventory host groups to group the applications hostname such as web server, database server, Operating System, region, or network.

A host group is a collection of hosts that you can run your Ansible playbook against. A condition defines either a workspace or a query within a workspace. For instance, you can run your inventory against all the hosts in your development workspace, or against all hosts with a webserver tag in your development workspace. The host groups can be defined by using Static inventory or Dynamic inventory method.

Static inventory allows to create the collection of hosts that you can run your Ansible playbook against. A condition defines either a workspace or a query within a workspace. For instance, you can run your inventory against all the hosts in your dev workspace, or against all hosts with a webserver tag in your dev workspace. You can also add multiple conditional target resources for your workspaces to run.

Dynamic inventory allows to create the collection of hosts in a inventory file that defines the hosts and group of hosts upon which your playbook operates.
This feature is now generally available. See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log17-august-2021).







 6 April 2021 



 For all version dates 

File storage for VPC. Accounts that have been granted special approval to preview this feature can now create NFS-based file shares in a zone in your region. Share file storage over multiple virtual service instances within the same zone across multiple VPCs. Learn about [creating file shares and mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about), and explore the new [API methods](https://cloud.ibm.com/apidocs/vpc-betalist-share-profiles).







 19 March 2021 



 For all version dates 

Instance resize. You can now resize an instance by providing the profile property in the API method PATCH /instances/{id} ([Update an instance](https://cloud.ibm.com/apidocs/vpc-betaupdate-instance)). For more information, see [Resizing a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance&interface=api).

This feature is now generally available. See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log30-march-2021).







 9 March 2021 



 For all version dates 

Bring your own license. You can now [bring your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about) (BYOL) for custom images that you create and import to IBM Cloud VPC. When you import a custom image, you can choose from new byol Red Hat Enterprise Linux (RHEL) and Windows operating systems.

A new dedicated_host_only property has been added to operating system resources.