vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Configuring the Cloud Functions CLI to use an HTTPS proxy 

The Cloud Functions CLI can be set up to use an HTTPS proxy. To set up an HTTPS proxy, an environment variable that is called HTTPS_PROXY must be created. The variable must be set to the address of the HTTPS proxy, and its port by using the following format: {PROXY IP}:{PROXY PORT}.

Changing the name of the org or space creates a new namespace based on the changed name. The entities in the old namespace are not visible in the new namespace and might be deleted.





 Migrating from OpenWhisk CLI to Cloud Functions CLI plug-in 

You can now use the Cloud Functions CLI plug-in to interact with Cloud Functions entities. Although you can continue to use the stand-alone OpenWhisk CLI, it does not have the latest features that are supported by Cloud Functions, such as IAM-based namespaces and service bind.



 Command syntax 

All the command options and arguments for commands in the Cloud Functions CLI plug-in are the same as the options for the [OpenWhisk stand-alone CLI](https://github.com/apache/openwhisk-cli) with the following differences.



* The IBM Cloud® Functions plug-in automatically utilizes your current login and target information.
* wsk commands are now run as ibmcloud fn.
* The wsk ibmcloud login command is no longer needed. You can sign in by using ibmcloud login command.
* You can manage your APIs by using the ibmcloud fn api commands.



For more information, see the [Cloud Functions CLI reference](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-cli).





 API Authentication and Host 

With the Cloud Functions CLI plug-in, you don't need to explicitly configure the API key and API host. Instead, you can log in with the ibmcloud login command.
2. Verify that the plug-in is installed.

ibmcloud plugin list

Example Output

Plugin Name Version
cloud-functions/wsk/functions/fn 1.0.32
3. All Cloud Functions commands begin with ibmcloud fn. To see everything that you can do with the Cloud Functions plug-in, run ibmcloud fn with no arguments.

ibmcloud fn



For more information about Cloud Functions commands, see the [Cloud Functions CLI reference](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-cli).





 Next steps for IBM Cloud® Functions CLI 

To work with Cloud Functions entities, you must first create or target a namespace. For more information, see [Managing namespaces](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces).





 Updating the Cloud Functions CLI plug-in 

You might want to update the CLI periodically to use new features.



1. View your current plug-in list by running ibmcloud plugin list command.

ibmcloud plugin list

Example Output

Plugin Name Version Status
cloud-functions/wsk/functions/fn 1.0.35 Update Available
cloud-object-storage 1.1.0
container-registry 0.1.437
container-service/kubernetes-service 0.4.51
2. If an update is available, run the ibmcloud plugin update command.

ibmcloud plugin update cloud-functions







 Configuring the Cloud Functions CLI to use an HTTPS proxy 

The Cloud Functions CLI can be set up to use an HTTPS proxy. To set up an HTTPS proxy, an environment variable that is called HTTPS_PROXY must be created. The variable must be set to the address of the HTTPS proxy, and its port by using the following format: {PROXY IP}:{PROXY PORT}.

Changing the name of the org or space creates a new namespace based on the changed name.
Configuring App Configuration 

[IBM Cloud® App Configuration](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-getting-started) is a centralized feature management and configuration service that provides a convenient, consistent, and secure approach to accessing, referencing, and reusing collections of feature flags and properties within toolchains.

You can configure an App Configuration instance by using the App Configuration service instance dashboard to add and manage specific environments and collections that contain sets of feature flags and properties. You can further refine the use of feature flags and properties by specifying target segments that evaluate based on user attributes and rules.

You can also add an App Configuration tool integration to a toolchain and apply specific feature flags or properties from the service instance to the environment or trigger properties of the associated pipeline. You can repeat this process across multiple toolchains by using App Configuration service instances, as required. For example, you can use a service instance to centrally store and manage all of the feature flags and properties that are required by toolchains across several environments.

When you apply feature flags or properties to a toolchain, special App Configuration feature flag and property references are saved within the toolchain instead of in the literal values. This feature supports centralized management of feature flags and properties directly from an App Configuration service instance. Feature flags and property values are then immediately available to toolchains that contain references to those feature flags and property values during subsequent pipeline runs.



 Creating an App Configuration integration 

Before you create an App Configuration tool integration in your toolchain, make sure that you provision an instance of the App Configuration service in a region and resource group that your toolchain can refer to.



1. If you are configuring this tool integration as you are creating the toolchain, and an App Configuration tool integration exists within the template that you are configuring, click the App Configuration tab. Alternatively, in the More tools section, click App Configuration.
2. If you have an existing toolchain and are adding this tool integration to it, from the IBM Cloud console, click the menu icon !
What is App Configuration? 

IBM Cloud 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 can also manage the properties for distributed applications centrally.



*  App Owners - Roll out features by segment and independent from code deployments.
*  Developers - Reduce source code branch complexity and troublesome merges by including untested or unfinished features behind a feature flag in your main branch.
*  Testers - Test new features in production and be assured of a smooth transition. Use flags to activate untested features only for testers and QA personnel until it's time to release.





  Features 

Key features of App Configuration:



*  Centralized configuration - Configure multiple, distributed resources from a central location. Use collections to organize your flags by app or resource.
*  Dark Launch - Includes features that are not ready for launch into your deployments, and activate them when they are ready.
*  Segmented Feature Rollout - Activate features for different segments at different times, or vary features by segment.
*  Feature Rollback - Instantly roll back problematic features by toggling feature flags in the App Configuration cloud dashboard.
*  Phased Rollout - Configure feature flag to be enabled for a subset of entities to implement progressive delivery of features.
You can also use a Cloud Foundry command-line interface, called cf, to deploy web apps.

Clients, which can be mobile apps, apps that run externally, apps that are built on IBM Cloud, or developers that are using browsers, interact with the IBM Cloud-hosted apps. Clients use REST or HTTP APIs to route requests through IBM Cloud to one of the app instances or the composite services.

The following figure shows the high-level Cloud Foundry architecture on IBM Cloud.

Zoom

![IBM Cloud architecture](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/cloud-foundry-public/images/arch.png)

Figure 4. Cloud Foundry architecture on IBM Cloud

You can deploy your apps to different IBM Cloud regions, for latency or security considerations. You can choose to deploy either to one region or across multiple regions.

Zoom

![Multi-region app development](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/cloud-foundry-public/images/multi-region.png)

Figure 5. Multi-region app deployment





 IBM Cloud infrastructure layers 

IBM Cloud abstracts and hides operating system and infrastructure layers so that you don't need to manage them. However, sometimes you might want to know more about the operating system and middleware for your app.



 Viewing IBM Cloud infrastructure layers 

You can run the ibmcloud cf stacks command to show the available stacks, or root file systems, that your apps are to be deployed to. You can also specify the stack when you use the ibmcloud cf push command with the -s option and the stack_name, where the stack_name is the root file system. IBM Cloud Foundry currently only supports cflinuxfs3.

ibmcloud cf push <APP_NAME> -s STACK
If you need more help, try [getting support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-get-support).





 Run your Function 

To get started, read [Working with Functions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-work) and [Function workloads](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cefunctions).

Functions can use a managed runtime or a custom runtime. Find out more at [Runtimes](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-runtime).

Want to customize your function?



* How much CPU and memory does your function need? See [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo).
* Want to define environment variables for your function? Find out how with [Working with environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvar).
* Does your function take advantage of configmaps or secrets? Take a look at [Working with secrets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secret) or [Working with configmaps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-configmap).



Ready to deploy?



* [Creating Function workloads with inline code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-inlinecode).
* [Creating Function workloads with repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-repo).
default a8a12accd63b437bbd6d58fb8b462ca7 true ACTIVE
test a8a12abbbd63b437cca6d58fb8b462ca7 false ACTIVE
6. Target a resource group by running the following command.

ibmcloud target -g <resource_group>

Example output

Targeted resource group default







 Setting up the Cloud Functions CLI plug-in 

To work with Cloud Functions, download and install the CLI plug-in.

You can use the Cloud Functions CLI plug-in to perform the following tasks.



* Run your code snippets, or actions, on Cloud Functions. See [Creating and invoking actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions).
* Create triggers and rules to enable your actions to respond to events. See [Creating triggers and rules](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-triggers).
* Bundle actions and configure external events sources. See [Create and use packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_ov).
* Explore the catalog of packages and enhance your applications with external services. See [Adding IBM Cloud](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-services).



Complete the following steps to install the Cloud Functions CLI plug-in



1. Install the Cloud Functions plug-in.

ibmcloud plugin install cloud-functions
2. Verify that the plug-in is installed.

ibmcloud plugin list

Example Output

Plugin Name Version
cloud-functions/wsk/functions/fn 1.0.32
3. All Cloud Functions commands begin with ibmcloud fn. To see everything that you can do with the Cloud Functions plug-in, run ibmcloud fn with no arguments.

ibmcloud fn
App Configuration CLI 

The IBM Cloud command-line interface (CLI) provides extra capabilities for service offerings. IBM Cloud CLI supports a plug-in framework to extend its capability. You can install the App Configuration CLI plug-in from the IBM Cloud plug-in repository. With the App Configuration service CLI plug-in, you can easily manage App Configuration service instances by using the CLI commands.

To run IBM Cloud App Configuration commands, use ibmcloud app-configuration or ibmcloud ac.



 Prerequisites 



* An IBM Cloud account. If you do not have an account, click [here](https://cloud.ibm.com/) to create one.
* An instance of [IBM Cloud App Configuration](https://cloud.ibm.com/catalog/services/app-configuration) service.
* [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
* Optionally, if you want to use private endpoint support that is provided by the IBM Cloud platform, make sure you [enable VRF and service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint&interface=ui).







 Installing App Configuration CLI plug-in 

Install the App Configuration CLI plug-in by running the following command from the IBM plug-in repo IBM Cloud:

ibmcloud plugin install app-configuration

You're notified on the command-line when updates to the IBM Cloud CLI and plug-ins are available. Be sure to keep your CLI up-to-date so that you can use the new commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.



 Output 

The command returns the following output:

Looking up 'app-configuration' from repository 'IBM Cloud'...
Plug-in 'app-configuration' found in repository 'IBM Cloud'
Attempting to download the binary file...
IBM Cloud HSM 6.0 and 7.0 are available in the [IBM Cloud catalog](https://cloud.ibm.com/catalog/infrastructure/hardware-security-module). Both versions are supported, however, these instructions focus on how to configure IBM Cloud HSM 6.0 to work with the IBM Blockchain Platform. If you are using 7.0, it is possible that some of the commands will differ slightly.





 Process overview 



* [Part One: Set up the HSM device and HSM client](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-hsm-gemaltoibp-hsm-gemalto-part-one)

This process involves deploying an HSM and configuring a partition as well as deploying an HSM client that you will use to configure the device. Throughout these instructions you will run some commands from the HSM server and others from the HSM client. For clarity, we prefix these steps with either ![HSM server](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/icon-hsm-2.png) or ![HSM client](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/icon-hsm-client.png).
* [Part Two: Configure communications between the HSM server and client](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-hsm-gemaltoibp-hsm-gemalto-part-two)

Communications between the HSM and client require a Network Trust Link (NTL) -- an encrypted, secure communications channel between the HSM and client.
Navigate to the IBM Log Analysis service and create an instance in the same region as your Cloud Functions namespace.
2. Configure the Log Analysis instance to receive platform service logs.



You can also launch logging from your Cloud Functions dashboard by selecting Launch Logging.



 Configure IBM Log Analysis 

To use the [IBM Log Analysis service](https://cloud.ibm.com/observe/logging) to view the logs of your Cloud Functions actions, you need to provision an instance first. For more information about additional options, see the [Getting started tutorial](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started).

To enable an instance that is receiving Cloud Functions action logs, you need to configure the [Platform Service Logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_svc_logs) in the logging service.

Cloud Functions sends the action logs to the Log Analysis service in the same region as the Cloud Functions namespace. Actions logs of a Cloud Functions namespace in us-south are sent to a logging instance in us-south.
1. In the Cloud Functions console, go to the [Create page](https://cloud.ibm.com/functions/create).
2. Select the namespace that you want to install the package into.
3. Click Install Packages.
4. Click the Watson package group.
5. Click the Discovery package.
6. Click Install.
7. After the package is installed, you are redirected to the Actions page and can search for your new package, which is named discovery-v1.
8. To use the actions in the discovery-v1 package, you must bind service credentials to the actions.



* To bind service credentials to all actions in the package, complete step 4 in the CLI instructions.
* To bind service credentials to individual actions, complete the following steps in the console.



You must complete the following steps for each action that you want to use.



1. Click on an action from the discovery-v1 package that you want to use. The details page for that action opens.
2. In the left navigation, click on the Parameters section.
3. Enter a new parameter. For the key, enter __bx_creds. For the value, paste in the service credentials JSON object from the service instance that you created earlier.











 Using the Discovery package 

To use the actions in this package, run commands in the following format:

ibmcloud fn action invoke discovery-v1/<action_name> -b -p <param name> <param>

All actions require a version parameter in the format YYYY-MM-DD. When the API is changed in a backwards-incompatible way, a new version date is released. See more details in the [API reference](https://cloud.ibm.com/apidocs/discoveryversioning).

This package's functions use the current version of Discovery, 2018-03-05. Try out the list-environments action.

ibmcloud fn action invoke discovery-v1/list-environments -b -p version 2018-03-05
Release notes for Cloud Functions 

Use the release notes to learn about the latest changes to IBM Cloud® Functions that are grouped by date.

For information about changes to the Cloud Functions CLI, see [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).



 June 2022 



 21 June 2022 

Additional support for the IBM Cloud Object Storage trigger.
: You can utilize the new Object Storage functionality for versioning and replication. See [Setting up the IBM Cloud Object Storage trigger](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_ev).





 9 June 2022 

Added information about packaging Java code.
: See [Packaging Java code by using the Java runtime with Docker](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_java_docker).







 April 2022 



 29 April 2022 

Node.js version 16 is now the default.
: See [JavaScript runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesopenwhisk_ref_javascript_environments).







 June 2021 



 21 June 2021 

Overview topic for troubleshooting
: See [Troubleshooting overview](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-troubleshooting).







 May 2021 



 7 May 2021 

Deprecated of packages and runtimes.
: See [runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimes).





 1 May 2021 

Added information about error handling.
: See [Error handing for Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-error-handing-functions).

Added information about getting support.
: See [runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimes).





 1 May 2021 

Added information about error handling.
: See [Error handing for Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-error-handing-functions).

Added information about getting support.
: See [Getting help and support](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-gettinghelp).







 April 2021 



 27 April 2021 

Added information about deprecating Watson services.
: See the individual packages.





 12 April 2021 

Updates to action information.
: Added and updated information for preparing your application code. See [Preparing apps for actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prep).

New Functions CLI version 1.0.54.
: See [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).







 March 2021 



 29 March 2021 

New Functions CLI version 1.0.53.
: See [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).





 25 March 2021 

Updated list of supported versions.
: See [Runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimes).

Updated the Composer topic.
: See [Composer](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composer).

Added information about adding an IBM Cloud Functions Channel to IBM Cloud Monitoring.
myfunction Ready https://myfun1.4svg40kna19.us-south.codeengine.appdomain.cloud 0.25 1G 8d
helloworld Ready https://myfunction1.4svg40kna19.us-south.codeengine.appdomain.cloud 0.25 1G 16d
myfunction1 Ready https://myfunction111.4svg40kna19.us-south.codeengine.appdomain.cloud 0.25 500M 25h
myfunction3 Ready https://myfunction41.4svg40kna19.us-south.codeengine.appdomain.cloud 0.25 500M 25h







 ibmcloud ce function runtimes 

List available function runtimes.

ibmcloud ce function runtimes [--all] [--output OUTPUT] [--quiet]



 Command Options 

--all, -A
: Display all runtimes, including deprecated runtimes. This value is optional. The default value is false.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce fn runtimes





 Example output 

Name ID Family Default Optimized
Node.js 18 nodejs-18 nodejs true true
Python 3.11 python-3.11 python true true







 ibmcloud ce function unbind 

Unbind IBM Cloud service instances from a function.

ibmcloud ce function unbind --name FUNCTION_NAME (--binding BINDING_NAME | --all) [--quiet]



 Command Options 

--name, -n