vania-janet/multiturn-rag-retrieval-data huggingface dataset:
CLI version history 

Find a summary of changes for each version of App Configuration plug-in. Keep your CLI up to date so that you can use all of the available commands and their options.



Table 1. Changes in the IBM Cloud App Configuration CLI

 Version       Release date       Changes                                                                 

 0.0.1 BETA    11 February 2021   Initial release.                                                        
 0.0.2 BETA    2 March 2021       Config support.                                                         
 0.0.3 BETA    9 April 2021       Properties support.                                                     
 1.0.0 BETA    21 May 2021        Environment support.                                                    
 1.0.1         4 June 2021        Import or export configuration support.                                 
 1.0.2         16 June 2021       Initializing using Instance GUID.                                       
 1.0.3         7 October 2021     Support for JSON and YAML data types for feature flags and properties.  
 1.0.4         12 November 2021   Update dependencies.                                                    
 1.0.5         4 January 2022     Update dependencies.                                                    
 1.0.6         22 February 2022   Added custom header to all outgoing API requests.                       
 1.0.7         29 April 2022      Added phased rollout support.                                           
 1.0.8         3 June 2022        Update dependencies.                                                    
 1.0.9         9 June 2022        Support for snapshot APIs.                                              
 1.0.10        26 August 2022     Support for Secret reference in Property type.                          
 1.0.11        16 September 2022  Support for private endpoints.
ID Name Status
0076-2249dabc-8c71-4a54-bxy7-953701ca3999 subnet1 available
0767-173bn4aa-060b-47e7-am45-b3395a593897 subnet2 available

For the best performance of an auto scale instance group, ensure that you use a subnet size of 32 or greater.

If you don't have one available, you can create a subnet by using the ibmcloud is subnet-create command. For more information about creating a subnet, see [IBM Cloud VPC CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencesubnets).
6. List the available images for creating your instance template. You can create an instance by using a stock image, a custom image from your account, or an image that was shared with your account from a private catalog. Run one of the following commands based on the image that you plan to use.



* Select a stock image or image from your account for your instance.



To list all available images, run the following command:

ibmcloud is images

Deprecated images do not include the most current support.

Now select image ibm-debian-11-3-minimal-amd64-1. To get the image ID, run the following command:

image=$(ibmcloud is images | grep -i "debian.available.amd64.public" | cut -d" " -f1)

Save the image ID as a variable, which is used later to provision an instance.



* Select an image shared from a private catalog for the instance



To list all available images, run the following command.

ibmcloud is catalog-image-offerings

This command returns both the offering_crn and the offering_version_crn for the available images.
: A new region in Sao Paulo, Brazil is available. The new region is br-sao and the domain name is br.icr.io. For more information, see [Local regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local).





 19 August 2021 

Using registry tokens is discontinued
: From 19 August 2021, registry tokens are no longer accepted for authentication. For more information, see [IBM Cloud Container Registry Deprecates Registry Tokens for Authentication](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-container-registry-deprecates-registry-tokens-for-authentication).





 9 August 2021 

The ibmcloud cr login command logs you into the <region>.icr.io registry domain only
: From version 0.1.541 of the Container Registry CLI, the ibmcloud cr login command logs you in to the <region>.icr.io registry domain only, where <region> is your [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions). If you want to log in to the deprecated domain, registry.<region>.bluemix.net, use docker login, see [Authentication](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_apikey_auth).





 8 July 2021 

Using Notary v1 for signing images is deprecated
: The Notary v1 service for signing images is deprecated. It is being removed from Container Registry on 31 August 2021.

As an alternative approach, Container Registry supports the [Red Hat Signing](https://www.redhat.com/en/blog/container-image-signing) model. For more information, see [Signing images for trusted content by using Red Hat signatures](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontentregistry_trustedcontent_red_hat_sig).





 21 June 2021
* Adds the [ibmcloud ks ingress secret](https://cloud.ibm.com/docs/containers?topic=containers-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 ks ingress alb migrate set of beta commands to migrate resources that are formatted for ALBs that run the IBM Cloud Kubernetes Service Ingress image to resources that are formatted for ALBs that run the Kubernetes Ingress image.
* Adds the [ibmcloud ks ingress alb enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_configure) and [ibmcloud ks ingress alb disable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_disable) commands.
* Adds the optional --version option to the ibmcloud ks ingress alb create command to specify the IBM Cloud Kubernetes Service Ingress image version or Kubernetes Ingress image version for the ALB.



Renamed commands: The following commands are shifted to new naming categories.



* Shifts all existing ibmcloud ks alb commands into the [ibmcloud ks ingress alb](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clialb-commands) subcategory.
* Changes the names of the following options in the relevant ibmcloud ks ingress alb commands: --alb-id to --alb, --secret-name to --name, and --user-ip to --ip.



Deprecated commands: The following commands are deprecated in favor of the new commands.



* Deprecates the ibmcloud ks alb cert set of commands.
* Deprecates the ibmcloud ks alb configure command.
* Removes the deprecated ibmcloud ks alb rollback command,
* 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.
* Adds the [ibmcloud oc ingress alb enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_alb_configure) and [ibmcloud oc ingress alb disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_alb_disable) commands.
* Adds the optional --version option to the ibmcloud oc ingress alb create command to specify the Red Hat OpenShift on IBM Cloud Ingress image version or Kubernetes Ingress image version for the ALB.



Renamed commands: The following commands are shifted to new naming categories.



* Shifts all existing ibmcloud oc alb commands into the [ibmcloud oc ingress alb](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clialb-commands) subcategory.
* Changes the names of the following options in the relevant ibmcloud oc ingress alb commands: --alb-id to --alb, --secret-name to --name, and --user-ip to --ip.



Deprecated commands: The following commands are deprecated in favor of the new commands.



* Deprecates the ibmcloud oc alb cert set of commands.
For example, use [ibmcloud schematics state list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencestate-list) command to list the resources provisioned in your workspace.

Deprecate and warning message when using ibmcloud terraform command.
: The Schematics ibmcloud terraform command usage displays warning and deprecation message as Alias 'terraform' will be deprecated. Use schematics or sch in your commands.

Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.8.0](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released on 9 April 2022.







 March 2022 

Review the release notes for March 2022.



 31 March 2022 

Support deleting Schematics data objects
: The Schematics supports [deleting Schematics data from UI, CLI, and API](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-intro) for workspace, action, and inventories objects.

Fixes related to Schematics Actions and workspace
: 

* Now you can create actions with an [empty resource group](https://cloud.ibm.com/apidocs/schematics/schematicscreate-action). The empty resource group automatically points to the Default resource group.



: 

* [List workspace API](https://cloud.ibm.com/apidocs/schematics/schematicslist-workspaces) supports summary profile type.



: 

* [Get inventory definition](https://cloud.ibm.com/apidocs/schematics/schematicsget-inventory) supports detailed profile type.



Get job files API supports plan_json file type
Schematics deprecates Python v3.6 and upgrades the Schematics Job image to use Python v3.8 by mid of September 2022. For more information, see [Schematics announcement](https://cloud.ibm.com/status/announcement?component=schematics) tools.

Review the release notes for September 2022.



 21 September 2022 

The Schematics Job image supports Python v3.8
: The Schematics Job image supports Python v3.8 from 21 September 2022. For more information, see [Schematics announcement](https://cloud.ibm.com/status/announcement?component=schematics) tools.







 August 2022 

Review the release notes for August 2022.



 16 August 2022 

Schematics runtime now supports Ansible v2.9.27
: [Schematics runtime](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-utilities) supports Ansible v2.9.27 to run your Ansible automation.





 11 August 2022 

Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.12.2](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.





 04 August 2022 

Schematics allowed IP address for US, EU Central, and UK South region are updated
: Schematics lists the [US, EU Central, and UK South region](https://cloud.ibm.com/docs/schematics?topic=schematics-allowed-ipaddresses) allowed IP addresses to support US, EU Central, and UK South region endpoints.







 July 2022 

Review the release notes for July 2022.



 26 July 2022 

Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.12.1](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.
To deprecate a published product from the IBM Cloud catalog, see [ibmcloud catalog offering deprecate-offering](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-pluginpublish-offering-deprecate).

ibmcloud catalog offering delete --catalog CATALOG --offering OFFERING



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering publish account 

Run the following command to publish a product from your private catalog to an account. After the product is published, users in the account that have access to the private catalog and its containing resource group can create an instance and start using it.

ibmcloud catalog offering publish account [--catalog CATALOG]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering publish allowlist 

Run the following command to publish a product from your private catalog to a set of allowlisted accounts. After the product is published, users in the allowlisted accounts can create an instance and start using it.

ibmcloud catalog offering publish allowlist [--catalog CATALOG][--account-ids ACCOUNT-IDS]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.

--account-ids ACCOUNT-IDS
: The account IDs.







 ibmcloud catalog offering publish enterprise 

Run the following command to publish a product to an enterprise. After the product is published, users within the enterprise can create an instance of the product.

ibmcloud catalog offering publish enterprise [--catalog CATALOG]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering suspend-offering 

Run the following command to suspend a product from the catalog. You can suspend it for a short time without permanently deleting or deprecating it.
\n While other PHP modules might be part of the runtime, they are included only as indirect dependencies of the other listed modules. These unlisted modules are candidates to be removed as soon as they are not required by the referring modules.





 Ruby runtime (deprecated) 

The Ruby runtime is deprecated. There is no relacement. Instead, you must migrate to a different runtime.

By default, all Ruby actions are executed in a version 2.6 environment.

For more information about the Ruby 2.6 runtime, see [(Details on GitHub)](https://github.com/apache/openwhisk-runtime-ruby/blob/master/core/ruby2.6ActionLoop/CHANGELOG.txt).





 Docker runtime 

Docker actions run a user-supplied executable in a Docker container. You can include any compilation steps or dependencies by modifying your Dockerfile. You can specify a Docker image to use with your action code by specifying the --docker flag when you run the [action create](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_action_create) command. When you create an action that uses a Docker image, your app runs in the public Docker image that you specify during action creation.

Cloud Functions provides base images on Docker hub. You can use these images as-is when you create actions, or you can use them as a base image when you write your Dockerfile. You can see a list of the available runtimes images in the [Available images and runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesruntimes_available) section.

Cloud Functions actions can be created by using public images on from Docker Hub.



 Docker skeleton 

You can use the openwhisk/dockerskeleton image to deploy your action.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is operating-system 

View details of an operating system.

ibmcloud is operating-system OPERATING_SYSTEM_NAME [--output JSON] [-q, --quiet]



 Command options 



* OPERATING_SYSTEM_NAME: Name of the operating system.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is image 

View details of an image.

ibmcloud is image IMAGE [--output JSON] [-q, --quiet]



 Command options 



* IMAGE: ID or name of the image.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is images 

List all images in the region.

ibmcloud is images [--visibility all | public | private] [--owner-type all | provider | user] [--status STATUS] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]



 Command example 



* ibmcloud is images --status deprecated,obsolete







 Command options 



* --visibility: List images with given visibility. Valid visibility is: public or private.
* --owner-type: Filters images with given owner type. Default is all. One of: all, provider, user.
* --status: Filters the collection to images with the comma-separated list of status values. Available values: available, deleting, deprecated, failed, obsolete, pending, unusable.
Unsupported:kubectl apply --server-dry-run removed The deprecated --server-dry-run option is removed from the kubectl apply command. If your scripts rely on this option, update them to use the --dry-run=server option instead. 
 Unsupported:kubectl get --export removed The deprecated --export option is removed from the kubectl get command. If your scripts rely on this option, refer to the [Deprecate --export option from get command pull request](https://github.com/kubernetes/kubernetes/pull/73787) issue for discussion and references to scripts that handle various use cases. 
 kubectl --output jsonpath format changes The kubectl get--o jsonpath (or -o jsonpath) option now returns a JSON object for complex types such as structs, arrays, and slices. Previously, the option returned output in go format. If you use kubectl get to retrieve such fields using --output jsonpath, update your scripts to handle JSON objects. You might try using the -o go-template option to maintain compatibility with the previous behavior. 
 Temporary kubectl latency RBAC operations are now performed asynchronously. After you run ibmcloud ks cluster config for the first time after the update, kubectl commands might fail for a few seconds while RBAC synchronizes for the first time. Afterward, kubectl commands perform as expected. If you use automation to access the cluster with kubectl commands, add retry logic for kubectl commands after a kubeconfig file is successfully retrieved. 
 Unsupported: Select kubelet metrics The following kubelet metrics that were available via the /metrics and /metrics/resource endpoints are unsupported and removed.
This change applies when [creating](https://cloud.ibm.com/apidocs/vpc-betacreate-share-mount-target), [updating](https://cloud.ibm.com/apidocs/vpc-betaupdate-share-mount-target), [listing](https://cloud.ibm.com/apidocs/vpc-betalist-share-mount-targets), [retrieving](https://cloud.ibm.com/apidocs/vpc-betaget-share-mount-target), and [deleting](https://cloud.ibm.com/apidocs/vpc-betadelete-share-mount-target) share mount targets.

See [2023-05-30 API migration (file shares)](https://cloud.ibm.com/docs/vpc?topic=vpc-2023-05-30-migration-file-shares) for guidance on migrating from targets to mount_targets.





 For all version dates 

Enforcement of file shares beta API requests. Starting with API version 2023-05-30, all requests made for [shares methods](https://cloud.ibm.com/apidocs/vpc-betalist-shares) must include the [maturity=beta](https://cloud.ibm.com/apidocs/vpc-betamaturity-query-parameter) query parameter. Requests that omit the maturity=beta query parameter will be regarded as requests against the [VPC GA API](https://cloud.ibm.com/apidocs/vpc), which does not yet support shares. As a result, those requests will fail.







 11 April 2023 



 For all version dates 

Image lifecycle management. Accounts that have been granted special approval to preview this feature can now [deprecate](https://cloud.ibm.com/apidocs/vpc-betadeprecate-image) or [obsolete](https://cloud.ibm.com/apidocs/vpc-betaobsolete-image) custom images directly.
Virtual Private Cloud

Classic infrastructure

Disable an ALB in your cluster. The ALB and its pods still exist, but stop routing traffic to your apps.

The previous alias for this command, ibmcloud oc ingress alb configure, is deprecated.

ibmcloud oc ingress alb disable --alb ALB_ID --cluster CLUSTER [-q]

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

Command options:

--alb ALB_ID
: Required: The ID for an ALB. To view the IDs for the ALBs in a cluster, run ibmcloud oc ingress alb ls --cluster CLUSTER.

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

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress alb disable command 

ibmcloud oc ingress alb disable --alb public-cr18a61a63a6a94b658596aa93a087aaa9-alb1 --cluster mycluster







 ibmcloud oc ingress alb enable classic 

Classic infrastructure

Enable an ALB in your classic cluster.

The previous alias for this command, ibmcloud oc ingress alb configure classic, is deprecated.

You can use this command to:



* Enable a default private ALB. When you create a cluster, a default private ALB is created for you in each zone where you have workers and an available private subnet, but the default private ALBs are not enabled. However, all default public ALBs are automatically enabled, and any public or private ALBs that you create with the ibmcloud oc ingress alb create classic command are enabled by default too.
* Enable an ALB that you previously disabled.



ibmcloud oc ingress alb enable classic --alb ALB_ID --cluster CLUSTER [--ip IP_ADDRESS] [--version IMAGE_VERSION] [-q]

Minimum required permissions
Make sure that you are authenticated with the registry where the base image resides by using the ibmcloud cr login command or the docker login command.





 How can I debug a BOM command that is failing to analyze a Dockerfile? 



* Verify that the Dockerfile does not have any issues by running the docker build command and making sure that it passes.
* If your Dockerfile requires ARG to be passed, make sure that the ARG is set as an environment variable. You can also use the DOCKERBUILDFLAG environment variable.
* Authenticate with the registry that contains the base images.
* [icr-execute-in-dind-cluster](https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/README.mdicr-execute-in-dind-cluster): Runs Docker commands such as build and inspect, against a Docker engine that is running in a Kubernetes cluster. If a Docker DinD isn't available on the build cluster, a new one is deployed. Then, it pushes the resulting image to the IBM Cloud® Container Registry.



The [cr build](https://cloud.ibm.com/docs/container-registry-cli-plugin?topic=container-registry-cli-plugin-containerregclibx_cr_build) command is deprecated. If you use this command, or reference it from the [icr-cr-build](https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/README.mdicr-cr-build) task, you can migrate to the [icr-containerize](https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/README.mdicr-containerize), [icr-execute-in-dind](https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/README.mdicr-execute-in-dind), or [icr-execute-in-dind-cluster](https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/README.mdicr-execute-in-dind-cluster) Tekton tasks to build container images. For more information about this replacement, see the [IBM Cloud® Container Registry is Deprecating Container Builds](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-container-registry-deprecating-container-builds) blog post.