vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [ibmcloud catalog offering version cra](https://cloud.ibm.com/docs/account?topic=account-manage-catalogs-pluginversion-cra) and [ibmcloud catalog offering version scc](https://cloud.ibm.com/docs/account?topic=account-manage-catalogs-pluginversion-scc).

ibmcloud catalog offering get-scan-results [--version-locator LOCATOR]



 Command options 

--version-locator LOCATOR
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.







 ibmcloud catalog offering version create-draft 

Run the following command to create a draft of an existing version. This command is useful for changing an existing version that you want to publish without introducing a new version. Some changes, like changing the source file, require you to revalidate the product.

ibmcloud catalog offering version create-draft --version-locator VERSION_NUMBER [--output FORMAT]



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.

--output FORMAT (optional)
: Specifies output format. The default is terminal compatible and the only supported alternative is JSON, for example, --output json.







 ibmcloud catalog offering version delete-version 

Run the following command to delete a version of a product.

ibmcloud catalog offering version delete-version --version-locator VERSION_NUMBER [--output FORMAT]



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.

--output FORMAT (optional)
: Specifies output format. The default is terminal compatible and the only supported alternative is JSON, for example, --output json.
Smart contract versioning example

 Organization Action Smart contract definition version Smart contract package version 

 Org1 Propose definition to channel v1.0.0 smartcontract_1.0.0 
 Org2 Approve definition and install smart contract package v1.0.0 smartcontract_1.0.0 
 Org3 Approve definition and install own smart contract package version with additional logging for example v1.0.0 smartcontract_1.0.1 
 Org3 Commit definition to channel v1.0.0 Org1: smartcontract_1.0.0 <br> <br>Org2: smartcontract_1.0.0 <br> <br>Org3: smartcontract_1.0.1 
 Org2 Propose update to smart contract definition with new package v1.1.0 smartcontract_1.1.0 
 Org1 Approve definition and install own smart contract package version with enhanced error checking for example v1.1.0 smartcontract_1.1.1 
 Org3 Abstains because he is on vacation 
 Org2 Commit definition to channel v1.1.0 Org1: smartcontract_1.1.1 <br> <br>Org2: smartcontract_1.1.0 <br> <br>Org3: none 
 Org3 Update package details and uses own version of smart contract package v1.1.0 smartcontract_1.1.1 



Whenever channel members agree to an update in the business logic, and channel members are running different custom versions of the smart contract, each member needs to implement the updated business logic in their own version of the smart contract and repackage it. Blindly installing a smart contract package from another organization risks overwriting any customizations that you might have added to your version of the smart contract.





 Important considerations when you update smart contracts 



1. What happens to my peers if I forget to upgrade them to the latest version before committing the smart contract definition on the channel?

After updating a smart contract definition to use a use smart contract package and committing it to the channel, if there are still peers on the channel running the previous version, those peers are no longer able to endorse transactions for the smart contract.
* [Updating your app to use project-only endpoints from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-console-projendpt)
* [Updating your app to use private endpoints from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-console-privateendpt)
* [Updating your app with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-cli)
* [Updating your app to use project-only endpoints with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-cli-projectonly)
* [Updating your app to use private endpoints with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-cli-privateendpt)
* [Updating an app to reference a different image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-diff-image)



* [Updating an app to reference a different image in Container Registry from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-crimage-console)
* [Updating an app to reference a different image in Container Registry with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-crimage-cli)
* [Updating an app to reference an image that is built from source code from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-source-console)
You can adjust them if necessary. For more information, see:



* [SAP Note 2382421 - Optimizing the Network Configuration on HANA- and OS-Level](https://launchpad.support.sap.com//notes/2382421)
* [SAP Note 2477204 - FAQ: SAP HANA Services and Ports](https://launchpad.support.sap.com//notes/2477204)







 Is there information on the ports and services that are used by SAP? 

See [TCP/IP Ports of All SAP Products](https://help.sap.com/viewer/ports) for detailed explanations of SAP ports and services





 How can I optimize my SAP HANA performance? 

See [SAP Note 2000000 - FAQ: SAP HANA Performance Optimization](https://launchpad.support.sap.com//notes/2000000)





 How can I use SAP HANA Mini Checks to monitor and highlight potential issues with my HANA implementation? 

See [SAP Note 1999993 - How-To: Interpreting SAP HANA Mini Check Results](https://launchpad.support.sap.com//notes/1999993)





 I see that HANA is using large SWAP memory. What is going on? 

See [SAP Note 2779331 - HANA services use large SWAP memory](https://launchpad.support.sap.com//notes/2779331)







 SAP NetWeaver generic questions 



 Which versions of SAP NetWeaver are supported? 

Most versions of SAP NetWeaver Application Server (ABAP or JAVA) from 7.0 or higher are supported across the IBM Cloud® for SAP portfolio.

For a full updated list of SAP NetWeaver versions and SAP Kernel Patch Levels supported for the various IaaS options, see the following SAP Notes:



* [SAP Note 2414097 - SAP Applications on IBM Cloud Classic Infrastructure environment](https://launchpad.support.sap.com//notes/2414097)
* [SAP Note 2927211 - SAP Applications on IBM Cloud Virtual Private Cloud (VPC) Infrastructure environment](https://launchpad.support.sap.com//notes/2927211)
app: kube-audit-forwarder
strategy:
rollingUpdate:
maxUnavailable: 1
type: RollingUpdate
template:
metadata:
labels:
app: kube-audit-forwarder
spec:
containers:
- image: haproxytech/haproxy-alpine:2.6
imagePullPolicy: IfNotPresent
name: haproxy
volumeMounts:
- name: config-volume
mountPath: /usr/local/etc/haproxy/haproxy.cfg
subPath: haproxy.cfg
volumes:
- name: config-volume
configMap:
name: kube-audit-forwarder-cm
---
apiVersion: v1
kind: Service
metadata:
name: kube-audit-forwarder
namespace: ibm-kube-audit
spec:
selector:
app: kube-audit-forwarder
ports:
- protocol: TCP
port: 80
targetPort: 3000
---
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
name: kube-audit-forwarder
namespace: ibm-kube-audit
spec:
podSelector:
matchLabels:
app: kube-audit-forwarder
policyTypes:
- Ingress
ingress:
- ports:
- protocol: TCP
port: 3000
from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
k8s-app: konnectivity-agent
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
app: konnectivity-agent
* [Linux™ 64-bit ARM](https://ibm-cloud-cli.s3.private.us.cloud-object-storage.appdomain.cloud/2.16.0/binaries/IBM_Cloud_CLI_2.16.0_linux_arm64.tgz)
* [Linux™ 32-bit](https://ibm-cloud-cli.s3.private.us.cloud-object-storage.appdomain.cloud/2.16.0/binaries/IBM_Cloud_CLI_2.16.0_linux_386.tgz)
* [PowerLinux™ 64-bit](https://ibm-cloud-cli.s3.private.us.cloud-object-storage.appdomain.cloud/2.16.0/binaries/IBM_Cloud_CLI_2.16.0_linux_ppc64le.tgz)
* [System/390 Linux™ 64-bit](https://ibm-cloud-cli.s3.private.us.cloud-object-storage.appdomain.cloud/2.16.0/binaries/IBM_Cloud_CLI_2.16.0_linux_s390x.tgz)



If you want to install binaries from previous releases, follow this template to construct the private endpoint link of the binary that you want to download, replacing release_tag with the release version that you want to download.

To view previous releases, access the official [ibm-cloud-cli-releases](https://github.com/IBM-Cloud/ibm-cloud-cli-release/tags) Github repository.



 Mac OS X 64-bit 

https://ibm-cloud-cli.s3.private.us.cloud-object-storage.appdomain.cloud/<release_tag>/binaries/IBM_Cloud_CLI_<release_tag>_macos.tgz





 Windows 64-bit
For more information, see [ibmcloud catalog offering version cra](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-pluginversion-cra) and [ibmcloud catalog offering version scc](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-pluginversion-scc).

ibmcloud catalog offering get-scan-results [--version-locator LOCATOR]



 Command options 

--version-locator LOCATOR
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.







 ibmcloud catalog offering version create-draft 

Run the following command to create a draft of an existing version. This command is useful for changing an existing version that you want to publish without introducing a new version. Some changes, like changing the source file, require you to revalidate the product.

ibmcloud catalog offering version create-draft --version-locator VERSION_NUMBER [--output FORMAT]



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.

--output FORMAT (optional)
: Specifies output format. The default is terminal compatible and the only supported alternative is JSON, for example, --output json.







 ibmcloud catalog offering version delete-version 

Run the following command to delete a version of a product.

ibmcloud catalog offering version delete-version --version-locator VERSION_NUMBER [--output FORMAT]



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.

--output FORMAT (optional)
: Specifies output format. The default is terminal compatible and the only supported alternative is JSON, for example, --output json.
Viewing and changing vSRX licenses 

The vSRX has two available licenses:



*  Standard
*  Content Security Bundle (CSB)



For information on the features offered with these licenses, refer to [Choosing a vSRX License](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-startedchoosing-license).

To view your current license, perform the following procedure:



1.  From your browser, open [https://cloud.ibm.com](https://cloud.ibm.com) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the upper left, then click Classic Infrastructure.
3.  Choose Network > Gateway Appliances.
4.  Click the Gateway Appliance Name to access the Gateway Appliance Details page.



To change your current license, perform the steps above, then:



1.  Run a [Readiness check](https://cloud.ibm.com/docs/vsrx?topic=vsrx-vsrx-readiness) for “License upgrade” and address any errors that are found.
2.  Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/icons/edit-tagging.svg) next to your current license to edit it.
3.  Select your new license type, then click Save.
Static route add-on change log 

For deployment steps, see the [managed static route add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-static-routes) docs.

For steps on updating the static route add-on, see [Updating managed add-ons](https://cloud.ibm.com/docs/openshift?topic=openshift-managed-addonsupdating-managed-add-ons).

To view a list of add-ons and the supported cluster versions, run the following command or see the [Supported cluster add-ons table](https://cloud.ibm.com/docs/openshift?topic=openshift-supported-cluster-addon-versions).

ibmcloud oc cluster addon versions



  Version 1.0.0 



  Change log for 1.0.0_649, released 8 September 2021 



*  Uses apiextensions.k8s.io/v1 instead of apiextensions.k8s.io/v1beta1.
* [Update MSPs in consortium to add organization-level endorsement policy](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-update-consortium)
* [Create channel and join peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-before-peer)
* [Export and Import Membership Service Providers (MSPs)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-before-msps)
* [Peer admin identity](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-peer-admin)



* [Limitations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-limitations)



* [Can I continue to use the Fabric SDK to deploy my smart contracts?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-sdk)
* [What happens to my existing smart contracts?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-existing-sc)
<br><br> * [ibm_en_destination](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination)<br> * [ibm_en_destination_android](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_android)<br> * [ibm_en_destination_chrome](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_chrome)<br> * [ibm_en_destination_firefox](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_firefox)<br> * [ibm_en_destination_ios](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_ios)<br> * [ibm_en_destination_safari](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_safari)<br> * [ibm_en_destination_slack](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_slack)<br> * [ibm_en_destination_webhook](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_destination_webhook)<br> * [ibm_en_source](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_source)<br> * [ibm_en_subscription](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_subscription)<br> * [ibm_en_subscription_android](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/en_subscription_android)<
Use the offline mode for Liberty 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

When a Liberty app is pushed to IBM Cloud®, the Liberty buildpack can access sites external to IBM Cloud to acquire artifacts required by the app.



*  https://download.run.pivotal.io and https://java-buildpack.cloudfoundry.org are used to access components for:



*  [AppDynamics agent](https://www.appdynamics.com/)
*  [MariaDB JDBC driver](https://mariadb.com/)
*  [New Relic agent](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-new_relic)
*  [OpenJDK](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-customizing_jreopenjdk)
*  [PostgreSQL JDBC driver](https://www.postgresql.org)



*  https://dl.zeroturnaround.com/jrebel/ is used to access components for [JRebel](https://www.jrebel.com/products/jrebel).
*  https://files.dynatrace.com/downloads/appmon/cloudfoundry/buildpack/java/ is used to access the [Dynatrace agent](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_dynatrace).





  Working with a proxy 

In some environments a proxy might be required. See [Working with a proxy](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-working_with_proxy) for more details.
Upgrading to a new Major Version 

When a major version of a database is at its end of life (EOL), it is a good idea to upgrade to a current major version.

You can find the available versions of RabbitMQ on the [IBM Cloud® Messages for RabbitMQ the catalog](https://cloud.ibm.com/catalog/messages-for-rabbitmq) page, from the cloud databases cli plug-in command [ibmcloud cdb deployables-show](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show), or from the cloud databases API [/deployables](https://cloud.ibm.com/apidocs/cloud-databases-apiget-all-deployable-databases) endpoint.

Upgrading your new deployment by [restoring a backup](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=cloud-databases-dashboard-backupsrestoring-a-backup) of your data into the new version. Restoring from a backup has a number of advantages:



* The original deployment continues running and production work can be uninterrupted.
* You can test the new database out of production and act on any application incompatibilities.
* The entire process can be rerun at any point.
* A fresh restoration reduces the likelihood that unneeded artifacts of the older version are carried over to the new deployment.





 Upgrading in the UI 

You can upgrade to a new version when [restoring a backup](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=cloud-databases-dashboard-backupsrestoring-a-backup) from the Backups tab of your Deployment Overview. Clicking Restore on a backup brings up a dialog box where you can change some options for the new deployment. One of them is the database version, which is auto-populated with the versions available for you to upgrade to. Select a version and click Restore to start the provision and restore process.





 Upgrading through the CLI
* Add support for .NET ASP.NET Core 3.1.7
* Add support for .NET ASP.NET Core 2.1.22
* Add support for .NET Runtime 3.1.8
* Add support for .NET Runtime 2.1.22
* Add support for .NET SDK 3.1.402
* Add support for .NET SDK 2.1.810
* Remove support for .NET ASP.NET Core 3.1.4
* Remove support for .NET ASP.NET Core 2.1.18
* Remove support for .NET Runtime 3.1.4
* Remove support for .NET SDK 3.1.202
* Remove support for .NET SDK 2.1.806
* Update Node.js version to 10.22.1







 8 September 2020 

Updated Node.js buildpack v4.4-20200828-1028
: The SDK for Node.js buildpack v4.4 provides Node.js community runtime versions v10.21.0, v.10.22.0, v12.18.2, v12.18.3. The default is latest 10.x, so it is currently 10.21.0. This buildpack is based on the community node.js buildpack [v1.7.26](https://github.com/cloudfoundry/nodejs-buildpack/tree/v1.7.26).





 26 August 2020 

Updated Liberty buildpack v3.48-20200821-1648
: The default Liberty runtime GA version is the 20.0.0.9 release.



* The alternate Liberty runtime GA version is changed to the 20.0.0.9 release.
* The IBM JRE version is updated to 8 SR6 FP15.
* The IBM JRE 8 SR6 FP15 includes fixes for the following three PSIRTs:
2023-05-30 API migration (file shares) 

As described in the [Beta VPC API](https://cloud.ibm.com/apidocs/vpc-beta) reference [versioning](https://cloud.ibm.com/apidocs/vpc-betaapi-versioning-beta) policy, to more quickly respond to feedback as a feature progresses through its beta phase, support for older versions of the beta API is limited to 45 days. Therefore, beta API requests must specify a version query parameter date value within the last 45 days.

Before you adopt the beta release version 2023-05-30 or later, be aware of the following changes, which might require you to update your client:



* In the [Shares](https://cloud.ibm.com/apidocs/vpc-betalist-share-profiles) methods, the targets property was changed to mount_targets.
* In the [share mount targets](https://cloud.ibm.com/apidocs/vpc-betalist-share-mount-targets) methods, the resource_type property value was changed to share_mount_target.
* When [creating](https://cloud.ibm.com/apidocs/vpc-betacreate-share) a file share, you must specify the mount_targets property instead of the targets property
* When making [share mount targets](https://cloud.ibm.com/apidocs/vpc-betalist-share-mount-targets) method requests, you must use the method URL /shares/{id}/mount_targets instead of /shares/{id}/targets.



All requests that use the following methods enforce the existing requirement that you provide the [maturity=beta](https://cloud.ibm.com/apidocs/vpc-betamaturity-query-parameter) query parameter:



* [Create a file share](https://cloud.ibm.com/apidocs/vpc-betacreate-share)
* [Create a mount target for a file share](https://cloud.ibm.com/apidocs/vpc-betacreate-share-mount-target)
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 10 February 2022 

Review the release notes for 10 February 2022.

CLI version 1.25.4 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 03 February 2022 

Review the release notes for 03 February 2022.

CLI version 1.25.3 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).







 January 2022 

Review the release notes for January 2022.



 27 January 2022 

Review the release notes for 27 January 2022.

CLI version 1.25.2 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Added more information for troubleshooting jobs when job runs do not complete
: See [Why is my job not completing(/docs/codeengine?topic=codeengine-ts-jobrun-doesnotcomplete)?

Added information about considerations when you use SSH keys for accessing your source repository
: See [Choosing an SSH key for code repository](https://cloud.ibm.com/docs/codeengine?topic=codeengine-code-repositorieschoose-ssh-key).





 20 January 2022 

Review the release notes for 20 January 2022.

CLI version 1.25.0 released
: This CLI version adds support for creating a build that pulls source from a local directory. See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Added information about considerations for HTTP handling with Code Engine apps and jobs