vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Regions 

IBM Cloud® Functions is available in the US South, US East, Germany, United Kingdom, Tokyo, and Sydney IBM Cloud regions. You can target a specific region whenever you log in to the IBM Cloud CLI or change your current region by using the -r flag.

ibmcloud target -r <region>

For example, to target the EU Central region:

ibmcloud target -r eu-de



  Cloud Functions endpoints 

The following endpoints are available for Cloud Functions and can be used with [Cloud Functions APIs](https://cloud.ibm.com/apidocs/functions).



Cloud Functions endpoints

 Region      Endpoint                                   

 US South    https://us-south.functions.cloud.ibm.com   
 US East     https://us-east.functions.cloud.ibm.com    
 UK South    https://eu-gb.functions.cloud.ibm.com      
 EU Central  https://eu-de.functions.cloud.ibm.com      
 Tokyo       https://jp-tok.functions.cloud.ibm.com     
 Sydney      https://au-syd.functions.cloud.ibm.com     







  Cloud Functions web action endpoints 

The following endpoints are available for Cloud Functions and can be used with [Cloud Functions web actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions_web).



Cloud Functions endpoints

 Region      Endpoint                                     

 US South    https://us-south.functions.appdomain.cloud   
 US East     https://us-east.functions.appdomain.cloud    
 UK South    https://eu-gb.functions.appdomain.cloud      
 EU Central  https://eu-de.functions.appdomain.cloud      
 Tokyo       https://jp-tok.functions.appdomain.cloud     
 Sydney      https://au-syd.functions.appdomain.cloud
Working with Functions 

A Function is a stateless code snippet that performs tasks in response to an HTTP request. With IBM Code Engine Functions, you can run your business logic in a scalable and serverless way. IBM Code Engine Functions provide an optimized runtime environment to support low latency and rapid scale-out scenarios. Your Function code can be written in in Node.js or Python, which are optimized to run in IBM Code Engine Functions. In addition, your Function code can be written for any OpenWhisk compatible runtime environment or a custom runtime image.

Before you begin



* If you want to use the Code Engine console, go to [Code Engine overview](https://cloud.ibm.com/codeengine/overview).
* If you want to use the CLI, [set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* Plan and choose your approach for making your code run as a Code Engine Function component.





 Function limitations 



* Supported in Washington, D.C. (us-east), Frankfurt (eu-de), and Sydney (au-syd) regions only.
* No support for subscribing to event producers.
* No support for custom domains.
* No support for limiting the visibility of your function.
* No support for Terraform.







 How do I make my code run as a Code Engine Function component? 

Whether your code exists as source in a local file or in a Git repository, or your code is a container image that exists in a public or private registry, Code Engine provides a streamlined way for you to run your code as a Function.



* If you are starting with source code that is located in a Git repository, you can choose to point to the location of your source, and Code Engine takes care of building the code bundle from your source and creating the Function with a single operation. In this scenario, Code Engine uploads your code to IBM Cloud® Container Registry.
1.0.29 06 February 2019 Added commands deploy and undeploy to deploy or undeploy a collection of Functions entities via a manifest file. For more information, see the [Deployment](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-deploydeploy) documentation. 
 1.0.28 21 January 2019 Added an error message when update, delete, get namespace name exists multiple times. 
 1.0.27 11 December 2018 <br><br> * Added namespace get fixes.<br> * Added a fix for --save-as when an action is a black box action.<br><br><br> 
 1.0.26 30 November 2018 Enabled ibmcloud fn property get --auth to correctly return the auth key in a new environment. 
 1.0.25 23 November 2018 <br><br> * Improved error message result display.<br> * Added a fn namespace get fix to correctly display namespace properties.<br><br><br> 
 1.0.23 15 October 2018 Added support for ruby (.rb) action code recognition. 
 1.0.22 20 August 2018 Added us-east region support. 
 1.0.21 01 August 2018 Aliases fn and functions can now be used for Cloud Functions commands: ibmcloud fn <command> and ibmcloud fn <command>. You can also still use ibmcloud wsk <command>. 
 1.0.19 02 July 2018 Minor bug fixes and improvements. 
 1.0.18 20 June 2018 <br><br> * Added a fix for unbinding user-provided service instances.<br> * Performance improvements.<br><br><br> 
 1.0.17 12 June 2018 Added support for binding (ibmcloud wsk service bind) and unbinding (ibmcloud wsk service unbind) user-provided service instances that are created by using the ibmcloud cf create-user-provided-service command. 
 1.0.16 24 May 2018 Minor bug fixes and improvements. 
 1.0.15 21 May 2018 Minor bug fixes and improvements.
* [Including modules for a Python Function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-localfunction-python-dep-local)



* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-localnextsteps-funruncr)



[Runtimes](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-runtimefun-runtime)



* [Supported managed runtimes for Functions on Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-runtimefun-supported-managed)
* [CPU and memory combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-runtimefun-cpu-mem)



[Migrating IBM Cloud Functions to Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate)



* [Comparing Code Engine to Cloud Functions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-compare)
* [Key capabilities](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-key)
* [How Functions compare to apps and jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-compare-app-job)
* [Migrating IBM Cloud Functions Actions to Code Engine Functions FAQ](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faqs)



* [How can I process a bulk-load of computations?]
* [How Functions compare to apps and jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-compare-app-job)
* [Migrating IBM Cloud Functions Actions to Code Engine Functions FAQ](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faqs)



* [How can I process a bulk-load of computations?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq1)
* [I used Cloud Function to include dynamic elements for my web application. Can I move to Code Engine Functions?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq2)
* [Can I trigger my function code?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq3)
* [Can my function be accessed through a public URL?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq4)
* [How can I secure my functions?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq5)
* [Can I include dynamic elements?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq6)
* [Can I use sequences to chain my functions together?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-migratefun-migrate-faq7)
* [Can I use whisk.system actions?]
* The [auto-configuration](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-auto_config) support was also extended to work with the [Compose for MongoDB service](https://cloud.ibm.com/docs/ComposeForMongoDB?topic=ComposeForMongoDB-about) (Currently only available with the monthly Liberty runtime).







 20 January 2017 

Updated Node.js buildpack v3.10
: This release of the buildpack supports IBM SDK for Node.js runtime versions: 0.10.47, 0.10.48, 0.12.17, 0.12.18, 4.7.0, 4.7.2, 6.9.2, and 6.9.4. The default is now 4.7.2. It is also synchronized with the [Cloud Foundry Node.js buildpack v1.5.24](https://github.com/cloudfoundry/nodejs-buildpack/tree/v1.5.24). It contains a fix for a bug where npm start was not always called to start apps.





 13 December 2016 

Updated Liberty buildpack v3.6-20161209-1351
: The default Liberty runtime version was updated to the [16.0.0.4](https://www.ibm.com/support/pages/node/715555) release.



* The IBM JRE version 8 was updated to SR3 FP21 version.
* The [auto-configuration](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-auto_config) support was also extended to work with the [Compose for PostgreSQL service](https://cloud.ibm.com/docs/ComposeForPostgreSQL?topic=ComposeForPostgreSQL-about).
* The buildpack also provides an updated version of the agent for the Auto-Scaling service.
* The buildpack was updated to support environment variables as part of the include locations in the server.xml file.
cloud-functions[wsk/functions/fn] 1.0.64 false
cloud-internet-services[cis] 1.14.9 true
code-engine[ce] 1.41.3 true
container-registry[cr] 1.0.6 true
container-service[kubernetes-service/ks] 1.0.498 false
cra 1.1.5 false
doi 0.4.1 false
schematics[sch] 1.12.7 true
secrets-manager 0.1.25 true

 ibmcloud dev --version
ibmcloud dev version 2.17.1

 java -version
openjdk version "11.0.17" 2022-10-18
IBM Semeru Runtime Open Edition 11.0.17.0 (build 11.0.17+8)
Eclipse OpenJ9 VM 11.0.17.0 (build openj9-0.35.0, JRE 11 Linux amd64-64-Bit Compressed References 20221031_559 (JIT enabled, AOT enabled)
OpenJ9 - e04a7f6c1
OMR - 85a21674f
JCL - a94c231303 based on jdk-11.0.17+8)

 ant -version
Apache Ant(TM) version 1.10.13 compiled on January 4 2023

 mvn -version
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: /opt/IBM/maven
Java version: 11.0.17, vendor: IBM Corporation, runtime: /usr/local/jdk11
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.49-linuxkit", arch: "amd64", family: "unix"

 gradle -version

Welcome to Gradle 8.0.2!

Here are the highlights of this release:
Autoscaling 

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).

IBM Cloud® has built-in autoscaling support for IBM® Cloud Foundry apps that adjust app instance numbers automatically by:



* Dynamic scaling instances based on app performance metrics.
* Scheduled scaling of instances based on date and time.



This capability is based on the [App AutoScaler](https://github.com/cloudfoundry/app-autoscaler) Cloud Foundry open source project. See the [App AutoScaler User Guide](https://github.com/cloudfoundry/app-autoscaler/blob/master/docs/Readme.md) to get started.



 Managing autoscaling from the console 

Autoscaling can be defined for apps that are deployed on IBM Cloud Foundry. If you don't have an IBM Cloud Foundry app running on IBM Cloud®, [deploy a Cloud Foundry app](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deployingapps) to IBM Cloud® before you configure autoscaling.



1. From the [IBM Cloud console](https://cloud.ibm.com), click the menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/icons/icon_hamburger.svg), and select Resource List.
2. On the Resource List page, click Cloud Foundry apps.
3. Click the app to view its Overview page.
4. Click Autoscaling.
5. In the Policy tab, configure your scaling policy for the app.





 Creating autoscaling policies
* [proxy](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementproxy)
* [noproxy](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementnoproxy)
* [hc](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementhc)
* [jmx](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementjmx)
* [localjmx](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_managementlocaljmx)









 How to configure App Management 

To enable App Management utilities, set the value of the BLUEMIX_APP_MGMT_ENABLE environment variable to the utility or list of utilities you want to enable, then restage your app. You can enable multiple utilities by separating them with a +.

For example, to enable hc, debug and trace utilities, run the following command:

ibmcloud cf set-env <myApp> BLUEMIX_APP_MGMT_ENABLE hc+debug+trace

Restage your app after you set the environment variable:

ibmcloud cf restage <myApp>

If you do not want the App Management utilities to be installed with your app, set the BLUEMIX_APP_MGMT_INSTALL environment variable to false and restage your app.

For example, run the following commands to stage your app without App Management utilities:

ibmcloud cf set-env <myApp> BLUEMIX_APP_MGMT_INSTALL false
ibmcloud cf restage <myApp>





 Restrictions 

Changes that you make to your app by using App Management are transient and are lost after you exit this mode. This mode is only for temporary development use and is not intended to be used as a production environment due to performance.



 Liberty utilities 



 jmx
Deploying apps 

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).

You can deploy apps to IBM Cloud® with the command line interface or the integrated development environments (IDEs). You can also use app manifests to deploy apps. When you use an app manifest, you reduce the number of deployment details that you must specify every time that you deploy an app to IBM Cloud.



 App deployment 

Deploying an app to IBM Cloud includes two phases, staging the app and starting the app.



 Staging an app 

During the staging phase, IBM Cloud takes care of the app container orchestration. When you push an app, the Cloud Controller sends a staging request to IBM Cloud, which takes over the task of allocating the app instances. The IBM Cloud backend orchestrates app containers to ensure fault-tolerance and long-term consistency.

All apps are deployed to the Diego architecture. To stage an app, deploy the app with the ibmcloud app push command:

ibmcloud app push <appname>

For more details, see [ibmcloud push](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_appsibmcloud_app_push).





 Starting an app 

When an app is started, the instance or instances of the app container are created. You can use the ibmcloud cf ssh or ibmcloud cf scp command to access the app container file system which includes the logs. The ibmcloud cf files command does not work for apps running on the Diego architecture.

If the app fails to start, the app is stopped, the contents of your app container are removed, and the log files are not available.

If you can't access the logs for the app by using the ibmcloud cf ssh or ibmcloud cf scp command, you can use the ibmcloud cf logs command to see the cause of the staging errors in the app container.
: Added support for configuring project-wide settings for service binding operations and access to IBM Cloud Container Registry in the console. See [Configuring project-wide settings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrations).

Updated support for TLS secrets
: Updated support for creating TLS secrets in the console to also permit the upload of a certificate chain and its private key from a file. See [Creating a TLS secret from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretsecret-create-ui-tls).

Added troubleshooting information for creating an allowlist for Code Engine apps and jobs
: 

* See [How can I add my Code Engine app to an allowlist](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-allowlist-app)?



: 

* See [How can I add my Code Engine job to an allowlist](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-allowlist-job)?



Added troubleshooting information for deploying a Python app
: See [Why does my Python app fail to deploy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-python)?





 19 April 2023 

New! Configuring a highly available application tutorial
: See [Configuring a highly available application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-multiple-regions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 14 April 2023 

CLI version 1.43.3 released
The API endpoint functions.cloud.ibm.com is still active, but now returns response data as content type text/plain instead of text/html. Other content types are not changing. Migrate your web actions to use the new API endpoint. The previous endpoints are deprecated and will be deactivated at some point.





 Migrating deployment scripts 

If you have scripts that use the OpenWhisk CLI with the wsk commands, all commands work the same way by using the command ibmcloud fn. You can modify your scripts to use the IBM Cloud CLI plug-in, or create an alias or wrapper so that current commands that use wsk are translated to ibmcloud fn. The ibmcloud login and ibmcloud target commands in the IBM Cloud CLI work in unattended mode. With unattended mode, you can configure your environment before you run ibmcloud fn commands to deploy and manage your Cloud Functions entities.
Create an App Configuration service instance 

App Configuration provides capabilities to deliver an agile development methodology by separating feature rollouts from regular release cycles. App Configuration is a centralized feature management and configuration service for use with web and mobile applications, microservices, and distributed environments.

Instrument your applications with App Configuration SDKs, and use the App Configuration dashboard or App Configuration administrator API to define features flags, which are organized into collections and targeted to segments. Change feature flag states in the cloud to activate or deactivate features in your application or environment, often without restarting.

You need an IBM Cloud® account to create an instance of the App Configuration service.

To create an App Configuration service instance, follow these steps.



1. Log in to your IBM Cloud account.
2. In the [IBM Cloud catalog](https://cloud.ibm.com/catalogservices), search App Configuration and select [App Configuration](https://cloud.ibm.com/catalog/services/apprapp). The service configuration screen opens.

Zoom

![Create an App Configuration service instance](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-create-instance.png)

Figure 1. App Configuration service instance
3. In the Create tab, select the location that represents the geographic area (Region) where you want to provision your instance. Currently, Dallas (us-south), Washington DC (us-east), London (eu-gb), and Sydney (au-syd) regions are supported.
4. Select a pricing plan - Based on your business requirements, select a pricing plan: Lite, Standard, and Enterprise.



* Lite - Includes all App Configuration capabilities for evaluation only. Not to be used for production. Lite plan services are deleted after 30 days of inactivity.
* Standard - The standard plan includes feature flags and property management capabilities.
ID: crn:v1:bluemix:public:cloudantnosqldb:eu-de:a/123456789012345678901234567890ab:f6f38f72-95af-4699-842c-4cac2a1ea19e:resource-key:5dab35d4-fe20-433e-9cb9-7ae4d93887d5
Created At: Wed Nov 28 16:30:08 UTC 2018
State: active
Credentials:
apikey: ABC123ABC123abc123abc123ABC123ABC123abc123
...
3. Bind the service to an action or package. The [ibmcloud fn service bind](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_service_bind) command makes your IBM Cloud service credentials available to your Cloud Functions code at run time.



Table 1. Parameters for the bind command

 Parameter Description 

 SERVICE The service name that you're binding. 
 ACTION_NAME The name of the action or package that you want to bind the service to. 
 --instance INSTANCE_NAME (Optional) Specify a service instance name. If you don't specify a service instance name, the first instance for the service is selected. 
 --keyname CREDENTIALS_NAME (Optional) Specify the credentials name. If you don't specify the credentials name, the first credentials for the service instance are selected. 



Example syntax

ibmcloud fn service bind SERVICE ACTION_NAME [--instance INSTANCE_NAME] [--keyname CREDENTIALS_NAME]

For example, to bind an IBM Cloudant service instance to an action called hello, run the following command.

ibmcloud fn service bind cloudantnosqldb hello --instance My-Cloudant --keyname cloudant-my1-creds

If your action is not found, try adding the package name to the command: demohello.
Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.59 false
cloud-internet-services[cis] 1.14.4 true
code-engine[ce] 1.35.0 true
container-registry 0.1.571 true
container-service[kubernetes-service/ks] 1.0.420 false
cra 0.1.20 false
doi 0.3.8 false
schematics 1.10.0 true

 ibmcloud dev --version
ibmcloud dev version 2.12.0

 java -version
openjdk version "11.0.11" 2021-04-20
OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
Eclipse OpenJ9 VM AdoptOpenJDK-11.0.11+9 (build openj9-0.26.0, JRE 11 Linux amd64-64-Bit Compressed References 20210421_975 (JIT enabled, AOT enabled)
OpenJ9 - b4cc246d9
OMR - 162e6f729
JCL - 7796c80419 based on jdk-11.0.11+9)

 ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021

 mvn -version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /opt/IBM/maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: /usr/local/openjdk-11
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.10.104-linuxkit", arch: "amd64", family: "unix"

 gradle -version

Welcome to Gradle 7.4.2!

Here are the highlights of this release: