vania-janet/multiturn-rag-retrieval-data huggingface dataset:
However, to take advantage of new features, you must create an IAM-enabled namespace.





 How do I see a list of my Cloud Functions namespaces? 

You can see a list of your Cloud Functions namespaces by running the [namespace list](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_namespace_list) command. The command output includes all the namespaces in the currently selected region and also lists whether the namespace is a Cloud Foundry-based or an IAM-based namespace. Note that the namespace list command is scoped to the targeted region and resource group that you set. To view your current region and resource group, run ibmcloud target. To set your region and resource group to a different choice, run ibmcloud target -r REGION -g RESOURCE_GROUP, where REGION and RESOURCE_GROUP are the new targets.

ibmcloud fn namespace list

The following example shows sample output from the ibmcloud fn namespace list command.

name type id description
dev CF-based dev
cfsdocs_prod CF-based prod
playground IAM-based <id_string> IAM playground.

You can see a list of your IAM-based namespaces in the [IBM Cloud Console Resource list](https://cloud.ibm.com/resources) or by using the resource service-instances CLI command. This command lists Cloud Functions namespaces of all regions.

ibmcloud resource service-instances --service-name functions

The following example shows sample output from the ibmcloud resource service-instances --service-name functions command.

Name Location State Type
playground us-south active service_instance





 How do I see the Cloud Functions entities in my namespace? 

You can see a list of your Cloud Functions entities by running the [namespace get](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_namespace_get) command.
Creating Function workloads from local source code 

You can create your Code Engine function directly from source code on your local workstation with the IBM Cloud® Code Engine CLI. Use the fun create command to both build a code bundle from your local source, and deploy your function to reference this built code bundle.

When you submit a build that pulls code from a local directory, your source code is packed into an archive file. Code Engine automatically uploads the code bundle to an IBM Cloud® Container Registry namespace in your account, and then creates and deploys your function to reference this built code bundle. Note that you can only target IBM Cloud Container Registry for your local builds. For this scenario, you need to provide only a name for the function and the path to the local source. For a complete listing of options, see the [ibmcloud ce fun create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create) command.

For information about required permissions for accessing image registries, see [Setting up authorities for image registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registryauthorities-registry).

You can choose to ignore certain file patterns from within your source code by using the .ceignore file, which behaves similarly to a .gitignore file. For example, entries for a .ceignore file for a Node.js function might include node_modules and .npm. For more sample file patterns to ignore, see the [GitHub .gitignore repository](https://github.com/github/gitignore).

IBM Cloud® Container Registry is required for this scenario.

Before you begin



* Set up your [Code Engine CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli) environment.
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
IBM Cloud CLI for Eclipse IDE plug-in (preview) 

This preview release of IBM Cloud® CLI for Eclipse plug-in provides extensions for Eclipse integrated development environments (IDEs). This Eclipse IDE plug-in enables developers to manage their IBM Cloud account, resources, and applications within the Eclipse IDE.

This plug-in provides functions that are provided by the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli). The IBM Cloud CLI allows developers to work with IBM Cloud resources, apps, and containers.

Zoom

![IBM Cloud CLI Eclipse plug-in](https://cloud.ibm.com/docs-content/v1/content/c169dfbb5a2bb64d01f8c6ca8d8691910f0a702e/cli/images/eclipse.png)

Figure 1. IBM Cloud CLI Eclipse plug-in

This plug-in supports running ibmcloud CLI commands from within the Eclipse environment.

The IBM Cloud CLI Developer Tools eclipse-ibmcloud-cli plug-in for Eclipse is an open source project that is available on [GitHub](https://github.com/IBM-Cloud/eclipse-ibmcloud-cli).



 Before you begin 

To use the Eclipse plug-in, install the following software:



* [Eclipse](https://www.eclipse.org/downloads/)
* [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli)



If you install the IBM Cloud CLI in a custom directory, set the system property ibmcloud_eclipse_cli_path to the custom location of the IBM Cloud CLI installation. For example, -Dcom.ibmcloud.eclipse.cli.path=<path-to-ibmcloud-cli-installation>. Specify this location in the eclipse.ini file under vmargs.





 Installing the IBM Cloud CLI plug-in
Optional: You can view your Satellite configuration [in the console](https://cloud.ibm.com/satellite/configuration), or by running the ibmcloud sat config ls[command](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-config-configuration-ls).







 Step 10: Deploying a new version of your app from a different branch 

If you have multiple branches in your repository representing multiple versions of the app, you can deploy a different branch to see a new version of your app running. Follow these steps to modify the toolchain to deploy a different branch of your source repository.



1. On the Overview of your toolchain, select the delivery pipeline to modify.
2. Click Triggers.
3. Click the action menu for the commit-push trigger.
4. Select Edit.
5. In the Branch field, select the branch you want to deploy. For example, v2.
6. In the deployment-branch line under Properties, click the Edit icon.
7. Modify the value of this property to the branch name you want to deploy. For example, v2.
8. Save the changes.
9. Check your app to see if it is running the new version by visiting the app URL with your browser.
10. Optional: View the new version of your configuration in the Satellite configurations [console](https://cloud.ibm.com/satellite/configuration) or by running running the ibmcloud sat config get --config CONFIG[command](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-config-configuration-get).



Now you can deploy Kubernetes resources to multiple clusters with a single toolchain.
* [Resolution for build source not specified correctly](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-bldpush-stepfailts-buildsource-notcorrect)
* [Resolution for a problem due to Docker Hub rate limits](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-bldpush-stepfailts-build-dockerbuild-ratelimits)
* [Resolution for build source not supported by buildpacks](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-bldpush-stepfailts-buildpack-notsupported)
* [Resolution for a problem with the Docker build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-bldpush-stepfailts-build-dockerbuild)



[Why does my Python app fail to deploy?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-build-pythonts-build-python)





 Troubleshooting Functions 

[Debugging functions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-functiontroubleshoot-function)



* [Function limits to consider](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-functionts-function-limits)
* [Getting logs for my function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-functionts-funcrtion-gettinglogs)
* [Keep your runtime and CLI versions up to date](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-functionts-function-uptodate)
* [Deploying a new version of your app from a different branch](https://cloud.ibm.com/docs/satellite?topic=satellite-sat_toolchain_tutorialmodify_trigger)







 Deploying apps to clusters with Satellite Config 

[Deploying apps to clusters with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorialbegin-sat-config-tutorial)



* [Objectives](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorialbegin-sat-config-tutorial-objectives)
* [Audience](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorialbegin-sat-config-tutorial-audience)
* [Prerequisites](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorialbegin-sat-config-tutorial-prereq)
* [Beginner tutorial: Deploying a hello world app](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorialbegin-sat-config-tutorial-deploy-app-ui)
* [Advanced tutorial: Deploying an app and updating it with new versions](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorialbegin-sat-config-tutorial-advanced-helloworld-ui)







 Connecting Locations with IBM Cloud using Direct Link 

[Connecting Locations with IBM Cloud using Direct Link](https://cloud.ibm.com/docs/satellite?topic=satellite-direct-link-tutorialdirect-link-tutorial)



* [FAQ](https://cloud.ibm.com/docs/satellite?topic=satellite-direct-link-tutorialfaq-direct-link)
The IBM Cloud API key is essential to authenticate with the IBM Cloud platform. Also the IAM token and IAM refresh token that Schematics requires to work with the resource's API, and to determine the permissions that you were granted. When you use native Terraform, always you must provide the IBM Cloud API key. In Schematics, the IAM token is retrieved for all IAM-enabled resources, including IBM Cloud Kubernetes Service clusters, and VPC infrastructure resources. However, the IAM token is not retrieved for IBM Cloud Foundry and classic infrastructure resources and the API key must be provided in the provider block.

Can I specify a different IBM Cloud API key in the provider block?

If you want to use a different API key than the one that is associated with your IBM Cloud account, you can provide this API key in the provider block. If an API key is configured in the provider block, this key takes precedence over the API key that is stored in IBM Cloud.

Can I provide an API key for a service ID?

You can provide an API key for a service ID for all IAM-enabled services, including VPC infrastructure resources. You cannot use a service ID for classic infrastructure or IBM Cloud Foundry resources.

Follow the instructions to configure the provider block.



1. Choose how you want to configure the provider block.



* Option 1 Create a separate provider.tf file. The information in this file is loaded by Terraform and IBM Cloud Schematics, and applied to all Terraform configuration files that exist in the same GitHub directory or tape archive file .tar. This approach is useful if you split out your infrastructure code across multiple files.
* Option 2 Add a provider block to your Terraform configuration file. You might choose this option if you prefer to, specify the provider alongside with your variables and resources in one Terraform configuration file.



2. Review what [credentials and information that you must provide in the provider block to work with your resources](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referencerequired-parameters).
Setting up the IBM Cloud Schematics CLI 

Before you begin using the IBM Cloud® Schematics CLI to deploy IBM Spectrum Symphony, review and complete the following prerequisites:



1. Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2. Log in to the IBM Cloud CLI with your IBMid. If you have multiple accounts, you are prompted to select which account to use. If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login

If your credentials are rejected, you might be using a federated ID. To log in with a federated ID, use the --sso flag. For more information, see [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id).
3. Install and set up the [IBM Cloud Schematics CLI plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin).
4. Make sure to generate your IBM Cloud API key. For more information, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey).
5. Create the config.json file that represents the configuration parameters that you would like to use to build the IBM Spectrum Symphony cluster. To learn more about all the properties, see [Deployment values](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-deployment-values). You can view a sample configuration file [here](https://github.com/IBM-Cloud/hpc-cluster-symphony/blob/master/sample/configs/hpc_workspace_config.json).
For details, see [Reaching enterprise backend with IBM Cloud Secure Gateway via console](https://www.ibm.com/blogs/cloud-archive/2015/04/reaching-enterprise-backend-bluemix-secure-gateway/).

To deploy your app to IBM Cloud as a Cloud Foundry app, select a runtime from the IBM Cloud catalog. The runtime contains a starter Hello World app that you can replace with your own app. If you cannot find a starter that provides the runtime you want, you can bring a custom, Cloud Foundry-compatible buildpack to IBM Cloud by using the –b option with the ibmcloud cf push command. For details, see [Using community buildpacks](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_buildpacks).

You can use the following tools and services that IBM Cloud provides:



Table 1. IBM Cloud tools

 Tool Method 

 Cloud Foundry CLI Manage your code on local client and use the CLI to push your app to IBM Cloud manually. For more information, see the [ibmcloud cf push command](https://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.html). 
 Eclipse Manage your code in Eclipse and use the IBM® Eclipse tools for IBM Cloud to push your app. 
 Git integration Manage your code on GitHub and integrate Git into IBM Cloud. You can collaborate with other developers. Your app is deployed to IBM Cloud automatically when you commit changes in the code. You do not need to push the app manually. 
 IBM Cloud DevOps Delivery Pipeline Manage your code on DevOps GitHub repository and deploy your app to IBM Cloud by using the DevOps Delivery Pipeline. 



If the Cloud Foundry platform does not support your app requirements, you can use a container or VM where the runtime is set up, configured, and maintained with more customized options.





 Developing and deploying your apps using toolchains in Continuous Delivery
: For more information about the go runtimes, see [(Details on GitHub)](https://github.com/apache/openwhisk-runtime-go/blob/master/README.md).
: For more information about writing go actions, see [Preparing Go apps](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_go).

Java
: By default, all Java actions are executed in a version 8 environment.
: For more information about the java:8 runtime, see [(Details on GitHub)](https://github.com/apache/openwhisk-runtime-java/blob/master/core/java8/CHANGELOG.md).

.NET Core (deprecated)
: The .NET core runtime is deprecated. There is no relacement. Instead, you must migrate to a different runtime.





 Available images and runtimes per region 

To view the available runtimes for IBM Cloud Functions in each region. The following links return a JSON response. The runtimes section of the response contains the set of available runtimes. The image section contains the name of the runtime image on [Docker Hub](https://hub.docker.com/) and the tag that is used.



* [us-south](https://us-south.functions.cloud.ibm.com/)
* [us-east](https://us-east.functions.cloud.ibm.com/)
* [eu-gb](https://eu-gb.functions.cloud.ibm.com/)
* [eu-de](https://eu-de.functions.cloud.ibm.com/)
* [jp-tok](https://jp-tok.functions.cloud.ibm.com/)
* [au-syd](https://au-syd.functions.cloud.ibm.com)
* [Cloud Foundry application bindings](https://docs.cloudfoundry.org/devguide/services/application-binding.html)





 Commands 

The following command list the IBM Cloud services you have mapped to be used in your IBM® Cloud Foundry applications.

ibmcloud cf services

The following command lists any "customer user provided services" you might have set up.

ibmcloud cf cups





 Output 

These are provided in VCAP_APPLICATION and VCAP_SERVICES variable groups in Cloud Foundry, but different services do these different ways.





 Migration steps 

In the IBM Cloud, you can use the same services with your new compute service as you have been with Cloud Foundry, there should be no need to move or migrate data. Your application can continue accessing those services once the basic connections have been made.

In the new IBM Cloud compute service, bind the compute service to the other IBM Cloud services you are using, and allow the necessary applications to access those services.







 Network policies 

Determine the container-2-container communication for your application and any other network policies you have set up.

References:



* [IBM Cloud Foundry container-to-comtainer networking](https://www.ibm.com/cloud/blog/cloud-foundry-container-to-container-networking)
* [Cloud Foundry networking](https://docs.cloudfoundry.org/devguide/deploy-apps/cf-networking.html)
* [Cloud Foundry understanding networking](https://docs.cloudfoundry.org/concepts/understand-cf-networking.html)





 Commands 

The following command lists all the current network policies you have in place in your IBM® Cloud Foundry org and space.

ibmcloud cf network-policies





 Output 

Record the interconnections between your IBM® Cloud Foundry applications, making note of what applications needs to talk to other applications.





 Migration steps 

Communicating directly between running containers or micro-services can be important for operational load, speed, and security. Be sure to understand the needs for the compute type you are moving to to ensure smooth ongoing operations.







 User responsibilities 

What are the responsibilities for users for ongoing IBM® Cloud Foundry applications?
ibmcloud version 2.16.0+492aff3-2023-04-06T16:13:44+00:00

 ibmcloud plugins
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.67 false
cloud-internet-services[cis] 1.14.11 true
code-engine[ce] 1.43.5 true
container-registry[cr] 1.0.8 true
container-service[kubernetes-service/ks] 1.0.523 false
cra 1.3.5 Update Available false
doi 0.4.2 false
schematics[sch] 1.12.10 true
secrets-manager[sm] 2.0.1 true

 ibmcloud dev
3.0.0

 java
openjdk version "11.0.19" 2023-04-18
OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu120.04.1)
OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu120.04.1, mixed mode, sharing)

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

 mvn
Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
Maven home: /opt/IBM/maven
Java version: 11.0.19, vendor: IBM Corporation, runtime: /usr/local/jdk11
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.2.15-300.fc38.x86_64", arch: "amd64", family: "unix"

 gradle

Welcome to Gradle 8.1.1!
Regions and endpoints 

Review region and connectivity options for interacting with IBM Cloud IBM Cloud App Configuration.



 Available regions 

IBM Cloud App Configuration is available in the following regions:



* Dallas
* Washington DC
* London
* Sydney



You can create IBM Cloud App Configuration resources in one of the supported IBM Cloud regions.





 Service endpoints 

IBM Cloud App Configuration offers two connectivity options for interacting with its service APIs.

Public endpoints
: By default, you can connect to resources in your account over the IBM Cloud public network. Your data is encrypted in transit by using the Transport Security Layer (TLS) 1.2 protocol.

Private endpoints
: To further secure your connection, you can also enable [virtual routing and forwarding (VRF) and service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint) for your infrastructure account. When you enable VRF for your account, you can connect to IBM Cloud App Configuration by using a private IP that is accessible only through the IBM Cloud private network.



 Public endpoints 

The following table contains the base URLs for the IBM Cloud App Configuration API endpoints. When you call the API, use the URL that corresponds to the region where your service instance is deployed. Add the path for each method to form the complete API endpoint for your requests.



Table 1. Public endpoints

 Location Endpoint URL 

 Dallas https://us-south.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 Washington DC https://us-east.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 London https://eu-gb.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 
 Sydney https://au-syd.apprapp.cloud.ibm.com/apprapp/feature/v1/instances/{guid} 







 Private endpoints
Troubleshooting for Cloud Foundry 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).

General problems with creating Cloud Foundry apps might include apps that can't be updated, or double-byte characters that aren't displayed. In many cases, you can recover from these problems by following a few easy steps.



 Cloud Foundry API endpoints 

While the legacy api..bluemix.net Cloud Foundry API endpoints are still available, you can update scripts and infrastructure automation to use the following updated Cloud Foundry API endpoints for your region:



* api.us-south.cf.cloud.ibm.com (previously api.ng.bluemix.net)
* api.eu-gb.cf.cloud.ibm.com (previously api.eu-gb.bluemix.net)
* api.us-east.cf.cloud.ibm.com (previously api.us-east.bluemix.net)
* api.eu-de.cf.cloud.ibm.com (previously api.eu-de.bluemix.net)
* api.au-syd.cf.cloud.ibm.com (previously api.au-syd.bluemix.net)







 Automatic failover between IBM Cloud regions isn't available 

You can't use automatic failover between IBM Cloud® regions. However, you can use a DNS provider that supports failover among many IP addresses as a workaround.

 What’s happening 

When an IBM Cloud region becomes unavailable, the apps that are running in that region are also unavailable, even if the same apps are running in another IBM Cloud region.

 Why it’s happening 

IBM Cloud doesn't yet provide automatic failover from one region to another.

 How to fix it 

You can use a DNS provider that supports intelligent failover among many ID addresses, and manually configure your DNS settings to enable the automatic failover between IBM Cloud regions.