vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Added the --inventory-connection-type, --bastion-credential-json and --credential-json option value to the create, and config updates. Updated non-english translations for the command-line. Fixed duplication display of command-object argument in ibmcloud schematics jobs run interactive mode. 
 1.6.0 29 September 2021 Support for linux-ppc64le, and linux-s390x binaries. Lists Terraform v1.0 in the details panel. Display Terraform v0.11 depreciation message in Schematics Workspaces page. Fixed the resource query list command returns values as empty string. 
 1.5.12 02 September 2021 Suppress status message for --output json flag. 
 1.5.11 27 August 2021 Added a flag --pull-latest to existing workspace update command. Fixed BNPP issue. Fixed the locale translations. 
 1.5.10 11 August 2021 Supports Terraform v0.15. Fixed locale translations. 
 1.5.9 13 July 2021 Fixed locale translations. 
 1.5.8 08 July 2021 Fixed shared data sets API path. Disabled shared data sets commands. 
 1.5.7 04 June 2021 Enhanced ibmcloud schematics state list command to display as tabular data with a new column taint status. Fixed ibmcloud schematics job run command with --input flag description. Fixed ibmcloud schematics job run command with --output json flag description. Fixed ibmcloud schematics action update command with --credentials flag and the locale translations. 
 1.5.6 03 June 2021 Updated ibmcloud schematics workspace new command to support Terraform v0.14 and the locale translations.
1.12.8 22 Mar 2023 [Schematics agent beta-1](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-reference&interface=cliagents-cmd) and [policy](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-reference&interface=clipolicy-cmd) CLI commands are available in us-south, us-east, eu-de, eu-gb region. 
 1.12.7 07 Feb 2023 Bug fix to disable API_AGENT_ATTACHMENT in us-south, us-east, eu-de, eu-gb region. 
 1.12.6 30 Jan 2023 Enhanced complex input support through blueprint yaml file. Fixes related to blueprint status output in the blueprint list table, index out of range for workspace action output, refresh token issue for long running blueprint jobs, and spinner panic fixes in get blueprint. 
 1.12.5 18 Dec 2022 Blueprint subcommand usage, revert to original usage of blueprint create, blueprint apply and so on. Support for specifying complex inputs via a local YAML file using -input-file option. 
 1.12.3 18 Nov 2022 Fixed blueprint subcommand usage, support source type in the blueprint list table. 
 1.12.3 3 Nov 2022 Enhanced blueprint commands, CLI with the latest SDK update, and the workspace action command update. 
 1.12.2 11 Aug 2022 Included --output flag and bug fixes for all blueprint commands in and released Schematics v1.12.2 plug-in. 
 1.12.1 26 July 2022 Incorporated the bugs and fixes related to blueprint commands in Schematics and released v1.12.1 plug-in. 
 1.12.0 11 July 2022 Support for Agents commands in Schematics from command-line. 
 1.11.1 8 July 2022 Support for blueprint commands, and fix the translation issue in Schematics from command-line.
You can also upload your own TLS certificates for custom Ingress domains to this Certificate Manager instance and use the new [ibmcloud ks ingress secret commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_secret_create) to create secrets for these certificates in your cluster. To ensure that a Certificate Manager instance is automatically created for your new or existing cluster, verify that the API key for the region and resource group that the cluster is created in has the correct Certificate Manager permissions.





 18 August 2020 

Versions
: Master fix pack update change log documentation is available.
: Kubernetes version [1.18.8_1525](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1188_1525_master), [1.17.11_1537](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11711_1537_master), [1.16.14_1544](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11614_1544_master), and [1.15.12_1550](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1550_master).





 17 August 2020 

Locations
: You can create [clusters on VPC infrastructure](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc) in the Tokyo multizone region.

Versions
: Worker node fix pack update change log documentation is available.
capability-show 

This command discovers if a capability is supported for a particular database type.

Short version - cs

ibmcloud cdb capability-show CAPABILITY_ID TYPE VERSION PLATFORM LOCATION TARGET_PLATFORM TARGET_LOCATION [--json] [--api-version]



 Command options 



* --json or -j Display results as JSON.
* --api-version or -v
API Version used for request.







 Capability ID options 



* autoscaling
* encryption
* endpoints
* groups
* locations
* point_in_time_recovery
* remotes
* restores
* versions







 Examples 

ibmcloud cdb capability-show 5f2d37a0-40a5-4a39-bf6a-0dbb1249ac5e database 3.2.1 IBMCloud us-south







 backup-capability-show 

This command discovers if a database type can be restored from a particular instance.

Short version - bcs

ibmcloud cdb discover-capability-information-from-backup (BACKUP_ID) (CAPABILITY_ID) (TARGET_PLATFORM) (TARGET_LOCATION) [--json] [--api-version] [--nowait]



 Command options 



* --json or -j Display results as JSON.
* --api-version or -v
API Version used for request.







 Capability ID options 



* restores







 Examples 

ibmcloud cdb discover-capability-information-from-backup f7d318b6-6d4e-4d2a-9be4-7c1efbc94a52 5f2d37a0-40a5-4a39-bf6a-0dbb1249ac5e IBMCloud us-south --json --api-version 2021-09-30 --nowait







 deployment-capability-show 

This command discovers if a particular deployment or formation supports a particular capability.

Short version - dcs
Terraform v1.1 Sept 2022 September 2023 September 2024 
 Terraform v1.2 March 2023 March 2024 March 2025 
 Terraform v1.3 Expected July 2023 Earliest July 2024 Earliest July 2025 
 Terraform v1.4 Expected September 2023 Earliest September 2024 Earliest September 2025 







 User actions 

Follow these steps to upgrade to continue working with the latest versions of Terraform in IBM Cloud Schematics.



1. Identification: Identify the version of Terraform in your IBM Cloud Schematics Workspaces. The Schematics Workspaces list indicates the version Terraform in use. Also, individual Schematics workspace [settings pages](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-version) in the console indicate the use of Terraform version. If you are using the command-line run [ibmcloud schematics workspace list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-list) command to list the Terraform version.
2. Migration: Migrate older Terraform versions to the current supported version. For more information about migrating Terraform version, see [Upgrading the Terraform workspace version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionmigrate-steps12).
3. Verification: You can verify that the workspaces are properly migrated by accessing the list of Terraform version that the target version you want to access in Schematics Workspace. Then, run the [ibmcloud schematics refresh](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-refresh) and [ibmcloud schematics plan](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-plan) commands to verify the migrated Terraform version works properly.
* Removes the kube-audit log source option from ibmcloud oc logging config commands.
* Adds a column to the output of ibmcloud oc addon-versions for the minimum required Red Hat OpenShift version.
* Adds a check to verify that you are logged in to the IBM Cloud CLI before a command request is issued.
* Updates the help text in various languages.







 Version 0.4.51 

Version 0.4.51 of the CLI was released on 7 November 2019.



* Adds the [ibmcloud oc kms crk ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliks_kms_crk_ls), [ibmcloud oc kms enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliks_kms_enable), and [ibmcloud oc kms instance ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliks_kms_instance_ls) commands to create and manage key management service (KMS) providers in a cluster.
* Adds the optional --skip-advance-permissions-check option to ibmcloud oc cluster create and ibmcloud oc cluster rm.
* Changes the --vpc-id option to be optional for ibmcloud oc worker-pool create vpc-classic.
* Fixes the error message for when no cluster name or ID is specified for ibmcloud oc worker get or ibmcloud oc worker-pool get.
* Adds public and private as supported values for the --hardware option of ibmcloud oc worker-pool create classic.
* When the --admin option is included in ibmcloud oc cluster config, removes -admin from the cluster name in the KUBECONFIG file path.
* Updates all command help to use the new space-separated syntax.







 Version 0.4.42
If you use [IBM Cloud IAM service access roles](https://cloud.ibm.com/docs/openshift?topic=openshift-iam-service-access-roles) to manage all your RBAC users, don't include this option. - Updates the Go version to 1.11.5.







 Version 0.2.40 

Version 0.2.40 of the CLI was released on 6 February 2019.



* Adds the [ibmcloud oc cluster addon ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addons), [ibmcloud oc cluster addon enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_enable), and [ibmcloud oc cluster addon disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_disable) commands for working with managed cluster add-ons such as the [Istio](https://cloud.ibm.com/docs/containers?topic=containers-istio) managed add-on for IBM Cloud Kubernetes Service.
* Improves help text for IBM Cloud Dedicated users of the ibmcloud oc vlan ls command.







 Version 0.2.30 

Version 0.2.30 of the CLI was released on 31 January 2019.



* Increases the default timeout value for ibmcloud oc cluster config to 500s.







 Version 0.2.19 

Version 0.2.19 of the CLI was released on 16 January 2019.



* Adds the IKS_BETA_VERSION environment variable to enable the redesigned beta version of the Red Hat OpenShift on IBM Cloud plug-in CLI. To try out the redesigned version, see [Using the beta command structure](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelogchangelog_beta).
* Removed security group network interface commands security-group-network-interface, security-group-network-interface-add, security-group-network-interface-remove and security-group-network-interfaces.







 Note 



* Support for primary_ipv4_address property in primary-network-interface and network-interface options for the instance-create, instance-create-from-template, instance-template-create and instance-template-create-override-source-template commands were removed. Use primary_ip property to create the resource with wanted IP address.
* Support for IPV4 option for the instance-create, instance-network-interface-create, instance-create-from-template, instance-template-create and instance-template-create-override-source-template commands were removed. Use the address option to create the resource with wanted IP address.
* Support for PNIC-IP option and primary_ipv4_address property in network-interface option for the bare-metal-server-create command was removed. Use primary_ip property in network-interface option and pnic-rip-address option to create the bare metal server with wanted IP address.
* Support for IP option for the bare-metal-server-network-interface-create command was removed. Use address option to create the bare-metal-server-network-interface with wanted IP address.









 v3.5.0 

Version 3.5.0 was released on 2022-03-25.



 New commands 



* N/A







 Updated commands 



* Update load-balancer-listener-create,load-balancer-listener-update, load-balancer-pool-create and load-balancer-pool-update commands to support UDP protocol.







 Removed commands 



* N/A









 v3.4.0 

Version 3.4.0 was released on 2022-02-24.



 New commands 



* N/A







 Updated commands 



* Update instance-create, instance-update, instance-template-create, instance-template-create-override-source-template and instance-create-from-template commands to support metadata service.
* Update instance-create and instance-create-from-template commands to support trusted profile.







 Removed commands
Run the following command to store the version date in a variable so that it can be reused in your session. For more information about setting the version parameter, see Versioning in the [Transit Gateway API](https://cloud.ibm.com/apidocs/transit-gatewayversioning)

api_version="2020-03-31"

To verify that this variable was saved, run echo $api_version and make sure that the response is not empty.





 Step 5: Verify that you have API access 

If you run into unexpected results, add the --verbose (debug) flag after the curl command to obtain detailed logging information.



* Call the [List Available Locations API](https://cloud.ibm.com/apidocs/transit-gatewaylist-offering-type-locations) to see the locations available for your transit gateway, in JSON format. At least one object should return.

curl -X GET "$transit_api_endpoint/v1/offering_types/dedicated/locations?version=$api_version" -H "Authorization: $IAM_TOKEN"
* Call the [List gateways](https://cloud.ibm.com/apidocs/transit-gatewaylist-gateways) API to see any gateways that you already created under your account, in JSON format.

curl -X GET "$transit_api_endpoint/v1/transit_gateways?version=$api_version" -H "Authorization: $IAM_TOKEN"
* Shifts all existing ibmcloud oc cluster feature commands into the [ibmcloud oc cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-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 oc 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.



* Adds the [ibmcloud oc cluster ca create](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_ca_create), [ibmcloud oc cluster ca rotate](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_ca_rotate), and [ibmcloud oc cluster ca status](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_ca_status) commands to manage the rotation of certificate authority (CA) certificates for your cluster components.
* Adds the [ibmcloud oc ingress secret](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_ingress_secret_create) set of beta commands to manage Ingress secrets in your cluster, such as creating secrets for TLS certificates that are stored in IBM Cloud Certificate Manager.
* Adds the ibmcloud oc ingress alb migrate set of beta commands to migrate resources that are formatted for ALBs that run the Red Hat OpenShift on IBM Cloud Ingress image to resources that are formatted for ALBs that run the Kubernetes Ingress image.
Installing the stand-alone IBM Cloud CLI 

The IBM Cloud® Command Line Interface provides commands for managing resources in IBM Cloud. When you install the standalone IBM Cloud CLI, you get only the CLI itself without any recommended plug-ins or tools.

If you want to install both the latest IBM Cloud CLI and other recommended plug-ins and tools for developing applications for IBM Cloud, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) and [Extending IBM Cloud CLI with plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins).



 Before you begin 

If you need to use a 32-bit version, or a previous version other than the latest for IBM Cloud Dedicated environments, see [IBM Cloud CLI releases](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/).





 Installing with an installer 

Use the following steps to install the latest stand-alone IBM Cloud CLI:



1. Use a browser to access the official [ibm-cloud-cli-releases](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/) GitHub repository, and select the installer of your OS to begin the download. The following operating systems are supported: macOS X 64-bit, Windows™ 64-bit, Linux™ x86 64-bit, and Linux™ LE 64-bit (ppc64le).
2. Run the installer:



* For Mac and Windows™, run the installer.
* For Linux™, extract the package and run the install script.



3. Log in to IBM Cloud:

ibmcloud login

Now, you're ready to manage IBM Cloud resources. Enter ibmcloud help to view the command descriptions.

If you're using a federated ID, [log in with a one-time passcode or an API key](https://cloud.ibm.com/docs/account?topic=account-federated_id).
/dev/hd2 2.16 0.26 89% 36565 37% /usr
/dev/hd9var 0.19 0.16 17% 953 3% /var
/dev/hd3 0.22 0.22 1% 33 1% /tmp
/dev/hd1 0.03 0.03 2% 7 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.44 0.05 90% 11651 49% /opt
/dev/||vedump 0.25 0.25 1% 4 1% /var/admin/ras/||vedump






 Attaching a new (disk) volume 

If your disk is not at the correct size, complete the following steps:

You must also complete these steps if you want to store the mksysb image in a data disk for shared access or long-term storage.



1. Create a file system to hold the mksysb archive.
2. Click Add new under Attached volumes.
3. Give your data volume a Name. Select the Type, Size, and make it Shareable. In the following example, mksysbfs is the volume name and it has 20 GB of space for multiple mksysb archive files:
4. After successfully attaching the mksysbfs volume to the helper VM, log in to the VM. The volume appears as a new hdisk. Run the lspv and cfgmgr commands on the helper VM to configure and show the new disk. The new disk is labeled as hdisk1. Using the lspv command:

 lspv
hdisk0 00f6db0acc7aece5 rootvg active

Using the cfgmr command:

 cfgmr
lspv
hdisk0 00f6db0acc7aece5 rootvg active
hdisk1 none none

5. Create an AIX Volume Group by running the mkvg command.
ibmcloud version 2.16.0+492aff3-2023-04-06T16:13:44+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.66 false
cloud-internet-services[cis] 1.14.11 true
code-engine[ce] 1.43.3 true
container-registry[cr] 1.0.8 true
container-service[kubernetes-service/ks] 1.0.506 false
cra 1.3.0 false
doi 0.4.2 false
schematics[sch] 1.12.9 true
secrets-manager[sm] 2.0.0 true

 ibmcloud dev --version
Incorrect Usage. flag provided but not defined: -version

NAME:
ibmcloud dev - Create, develop, deploy, and monitor applications

USAGE:
ibmcloud dev command [arguments...] [command options]

COMMANDS:
help Show help
pipeline-get [Beta] Get details for a pipeline
pipeline-log [Beta] Get logs for a pipeline, stage, job, or job execution
pipeline-open [Beta] View a pipeline in the browser
pipeline-run [Beta] Run a pipeline
tekton-info [Beta] Get details for a tekton pipeline
tekton-logs [Beta] Get logs for a tekton pipelinerun
tekton-pipeline-cancel [Beta] Cancel an ongoing pipeline
tekton-pipelinerun [Beta] Get details for a tekton pipelinerun
tekton-pipelineruns [Beta] List the pipelineruns for a tekton pipeline
tekton-trigger [Beta] Trigger a tekton pipeline
toolchain-delete [Beta] Delete a toolchain
toolchain-get [Beta] Get details for a toolchain in a resource group
toolchain-open [Beta] View a toolchain in the browser
Before you can add new service bindings to an app or job that has service bindings that use the previous implementation, you must unbind all these service bindings. You can then re-create them with the improved implementation and add new service bindings.
* You cannot individually unbind these service bindings. You must remove them all by using the app unbind --all or job unbind --all command.
* If you are working with Function workloads, your function automatically uses the latest implementation of service bindings.



To take advantage of the latest enhancements and continue to manage service bindings for your apps and jobs easily, update to the [latest IBM Cloud Code Engine CLI version](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions) and [replace service bindings that use the previous implementation](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-bindingreplaceprevimpl-binding).



 How can I replace a service binding that uses the previous implementation? 

If your app or job has service bindings that use the previous implementation, and you want to add new service bindings to your app or job, you must first remove the bindings that use the previous implementation before new bindings are created. You can re-create those existing service bindings if needed.

Your application might not be fully functional during the process of unbinding and rebinding.



1. To discover if your app or job uses the previous implementation of service bindings, run the app get or job get command. If the previous service binding implementation is used, the output of this command provides the information, and the commands that you must use to bind another service to the application or job. For example,

ibmcloud ce app get --name myapp

Example output

Run 'ibmcloud ce application events -n myapp' to get the system events of the application instances.
Run 'ibmcloud ce application logs -f -n myapp' to follow the logs of the application instances.
OK

This application uses a previous service binding implementation.
Your application will continue to function normally.
Beta[Storage commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_storage) View and modify storage resources. 







 cluster commands 

Create, view, and modify clusters and cluster settings, such as add-on, subnet, and master settings.



 ibmcloud oc cluster addon disable 

Disable a managed add-on in an existing cluster. This command must be combined with one of the following subcommands for the managed add-on that you want to disable.



 ibmcloud oc cluster addon disable debug-tool 

Virtual Private Cloud

Classic infrastructure

Disable the add-on for the IBM Cloud Kubernetes Service Diagnostics and Debug Tool.

ibmcloud oc cluster addon disable debug-tool --cluster CLUSTER [-f]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-f
: Optional: Force the command to run with no user prompts.





 ibmcloud oc cluster addon disable image-key-synchronizer 

Virtual Private Cloud

Classic infrastructure

Disable the add-on for the [Image Key synchronizer](https://cloud.ibm.com/docs/openshift?topic=openshift-imagesencrypted-images).

ibmcloud oc cluster addon Disable image-key-synchronizer --cluster CLUSTER [--version VERSION]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--version VERSION
: Optional: Specify the version of the add-on to install. If no version is specified, the default version is installed.



 Example addon disable image-key-synchronizer command