vania-janet/multiturn-rag-retrieval-data huggingface dataset:
1. Add an image such as a brand logo by clicking Select and browsing your local system for an image to upload.
2. Choose a color scheme by either selecting one of the color options or specifying in a hex value.
3. Change between web and mobile to see how the color scheme looks on each type of device.
4. When you're happy with your choices, click Save Changes.



7. In a browser, refresh your login page. The changes that you made in the previous step are already visible.







 Support for Cloud Foundry service broker 

The IBM Cloud Foundry service broker is unsupported. All services that use the Cloud Foundry service broker will stop working on 1 June 2023, when Cloud Foundry enters the [End-of-Support stage](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).

Not sure if your App ID instance is using the Cloud Foundry service broker? In the [Cloud Foundry services](https://cloud.ibm.com/cloudfoundry/public) section, check whether your App ID instance is listed as an alias. If your instance is already an alias, as shown in the following screen capture, you do not need to take any action.

Zoom

![Screenshot showing how to identify instances with aliases.](https://cloud.ibm.com/docs-content/v1/content/27ecaa7a29890634603881a8e64789974a29916b/appid/images/cf-alias-screenshot.svg)

Figure 1. Identifying instances with aliases.

If your instance is not an alias and you want to keep it, please contact [IBM Cloud support](https://cloud.ibm.com/unifiedsupport/supportcenter) to discuss next steps.





 Next steps 

Ready to jump in and get started with your own apps?
For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://developer.hashicorp.com/terraform/language).





1. Create a Code Engine project by using the code_engine_project resource argument in your main.tf file.

data "ibm_resource_group" "resource_group" {
name = "<your_resource_group_name>"
}

resource "ibm_code_engine_project" "code_engine_project_instance" {
name = "<your_project_name>"
resource_group_id = data.ibm_resource_group.resource_group.id
}
2. After you finish building your configuration file, initialize the Terraform CLI. For more information, see [Initializing Working Directories](https://developer.hashicorp.com/terraform/cli/init).

terraform init
3. Provision the project from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://developer.hashicorp.com/terraform/cli/run).



1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan

data.ibm_resource_group.resource_group: Reading...
data.ibm_resource_group.resource_group: Read complete after 1s [id=<your_resource_group_id>]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:
For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).







 Creating a resource group by using Terraform 

Use the following steps to create a resource group by using Terraform:



1. Create an argument in your main.tf file. The following example creates a resource group by using the ibm_resource_group resource, where name is a unique name to identify the resource group.

resource "ibm_resource_group" "resourceGroup" {
name = "prod"
}

You can specify tags associated with the resource group instance. For more information, see the argument reference details on the [Terraform Resource Management](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_group) page.
2. After you finish building your configuration file, initialize the Terraform CLI. For more information, see [Initializing Working Directories](https://www.terraform.io/cli/init).

terraform init
3. Provision the resources from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://www.terraform.io/cli/run).



1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan
2. Run terraform apply to create the resources that are defined in the plan.

terraform apply









 Renaming a resource group 

Your first resource group is created and named Default for you.
See the following example that uses the command line to test the standard analyzer:

curl "https://$ACCOUNT.cloudant.com/_search_analyze" -H "Content-Type: application/json"
-d '{"analyzer":"standard", "text":"ablanks@renovations.com"}'

See the following result of testing the standard analyzer:

{
"tokens": [
"ablanks",
"renovations.com"
]
}







 Queries 

After you create a search index, you can query it.



* Run a partition query by using the following request:

GET /$DATABASE/_partition/$PARTITION_KEY/_design/$DDOC/_search/$INDEX_NAME
* Run a global query by using the following request:

GET /$DATABASE/_design/$DDOC/_search/$INDEX_NAME



Specify your search by using the query parameter.

See the following example that uses HTTP to query a partitioned index:

GET /$DATABASE/_partition/$PARTITION_KEY/_design/$DDOC/_search/$INDEX_NAME?include_docs=true&query=":"&limit=1 HTTP/1.1
Content-Type: application/json
Host: $ACCOUNT.cloudant.com

See the following example that uses the command line to query a partitioned index:



* Curl
* Java
* Node
* Python
* Go



curl "https://$ACCOUNT.cloudant.com/$DATABASE/_partition/$PARTITION_KEY/_design/$DDOC/_search/$INDEX_NAME?include_docs=true&query=":"&limit=1"

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.PostPartitionSearchOptions;
import com.ibm.cloud.cloudant.v1.model.SearchResult;

Cloudant service = Cloudant.newInstance();

PostPartitionSearchOptions searchOptions =
Site map 



 Getting started with IBM Cloud Satellite 

[Getting started with IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-startedgetting-started)



* [What are Satellite locations, hosts, and so on?](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-startedsat-key-terms)
* [Choose your infrastructure for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-startedgs-start-here)



* [Minimum requirements for hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-startedgs-min-reqs)



* [I created a Satellite location, what comes next?](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-startedwhats-next)







 Understanding Satellite use cases 

[Satellite use cases](https://cloud.ibm.com/docs/satellite?topic=satellite-use-caseuse-case)



* [Benefits of using Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-use-casebenefits)
* [Common use cases for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-use-caseuse-case-common)



* [Deploying Red Hat OpenShift environment as a managed service wherever it is needed](https://cloud.ibm.com/docs/satellite?topic=satellite-use-caseuse-case-common1)



* [Finance use cases for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-use-caseuse-case-finance)



* [Leveraging mainframe data for customers restricted from moving data to cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-use-caseuse-case-finance1)
To get started, you need the IBM Cloud CLI so that you can interact with services that you provision on IBM Cloud. You also need the openssl and jq packages installed locally on your workstation.



1. Create an [IBM Cloud account](https://cloud.ibm.com).
2. Download and install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) for your operating system.
3. Download and install the [IBM Key Protect CLI plug-in](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-up-cli) v0.6.3 or later, and [configure it to use in Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-cli). Make sure to update the KP_PRIVATE_ADDR variable to the current instance key management endpoint URL.

To check your IBM Key Protect CLI plug-in version:

ibmcloud plugin show key-protect

To update your IBM Key Protect CLI plug-in to the latest version:

ibmcloud plugin update key-protect -r 'IBM Cloud'
4. Download and install the [OpenSSL cryptography library](https://www.openssl.org/source/).

You can use openssl commands to create encryption keys on your local workstation if you're trying out Hyper Protect Crypto Services for the first time. This tutorial requires OpenSSL version 1.0.2r or above.

If you're using a Mac, you can quickly get up and running with OpenSSL by using [Homebrew](https://brew.sh/). Run brew install openssl if you're installing the package for the first time, or run brew upgrade openssl to upgrade your existing package to the latest version.
5. Download and install [jq](https://stedolan.github.io/jq/).
For more information about IBM Cloud accounts, see [Setting up your IBM Cloud account](https://cloud.ibm.com/docs/account?topic=account-account-getting-started) and [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
* A Satellite cluster or an Red Hat® OpenShift® cluster on IBM Cloud that is registered with your Satellite location.



If you don't have a Satellite cluster, you can [register a Red Hat OpenShift cluster with Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-register-openshift-clusters).



* A [Satellite cluster group](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig) that contains the cluster that is required by the toolchain. The toolchain in this tutorial supports a Satellite cluster group that contains only Red Hat OpenShift clusters.
* Image Pull Secrets. Make sure that you configure the image pull secrets that are required to deploy application images in your cluster namespace. For more information, see [understanding how to authorize your cluster to pull images from a private registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycluster_registry_auth).
* A Satellite location for deploying the resources.
* An instance of the [Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started) service.







 Step 1: Getting started 

Start to create a toolchain in IBM Cloud.



1. Log in to [IBM Cloud Toolchains](https://cloud.ibm.com/devops/toolchains) with your IBM Cloud credentials.
2. Select the Resource Group and Location for your toolchain.
3. Click Create toolchain.
4. On the Create a Toolchain page, select Satellite under Filters to display templates that are applicable for Satellite.
5.
[Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > Get started.
2. Enter the name of your company as you want it to be displayed in the catalog, and click Save. For the purpose of this tutorial, enter Example Corp as the company name.







 Step 2: Create your test environment 

You, or a member of your team, uses the test environment to onboard the template and validate that it can be deployed to your VPC. Your test environment includes a private catalog in which you import the template from an external repository.



1. Click Create in the Create your test environment section.
2. Enter Example Corp Catalog as the name of the private catalog, and click Create.







 Step 3: Set up access for your team 

You can enlist team members to help with the onboarding process by assigning them specific levels of IBM Cloud Identity and Access Management (IAM) access. To streamline the process of assigning access, complete the following steps to create your access group:



1. Click Assign in the Assign access section.
2. Enter Example Corp Terraform Template as the name of the access group, and click Assign. The following roles are assigned to the access group by default:



* Administrator on the Catalog Management service
* Editor on the Partner Center - Sell service
* Editor on the User Management service
* Editor on the IAM Access Groups service
* Viewer on all account management services



For more information about the actions associated with each role, see [Actions and roles for account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles).







 Step 4: Invite team members to your account 

After you create the Example Corp Terraform Template access group, you're ready to invite team members to your account and add them to your access group. Team members are granted the following editor permissions by default:
Terraform on IBM Cloud docs 

Explore the capabilities of the IBM Cloud Provider plug-in for Terraform. You can get started by installing the Terraform CLI and configure the IBM Cloud Provider plug-in. Then, you can try out a tutorial to create an IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud cluster by using Terraform. You can also choose one of the IBM-provided Terraform templates to get started with the provisioning of other IBM Cloud services with Terraform, such as IBM Cloud Object Storage or IBM Key Protect.

 Developer tools 

[CLI reference](https://www.terraform.io/docs/cli/index.html)[Terraform reference](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs)

 Recommended content 

[Set up the Terraform CLI and IBM Cloud Provider plug-in Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform so that you can start working with services in IBM Cloud.](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started)[Find supported Terraform resources and data sources Explore the Terraform resources and data sources that you can use to provision, update, and delete IBM Cloud services with Terraform. ](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-resources-datasource-list)[Browse Terraform templates Explore the sample Terraform templates, onboard them to your private catalogs, and try them using Schematics.](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatesample-templates)[Create Kubernetes and OpenShift clusters Learn how to create single and multizone IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud clusters with Terraform.]
To avoid the installation of these tools you can use the [Cloud Shell](https://cloud.ibm.com/shell) from the IBM Cloud console.





 Step 1: Target a resource group 



1. [Login](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) with IBM Cloud CLI with username and password, or use the API key.
2. Specify the target resource group for your resources. You can list the available resource groups with the following command.

ibmcloud resource groups
Retrieving all resource groups under account 1b0834ebce7f4b94983d856f532ebfe2 as xxx@yyy.com...
OK
Name ID Default Group State
default 28b0e7d18da9417ea85b2ba308088657 true ACTIVE
3. If you want to use the default resource group, you can set your target resource group with the following command:

VMWARE_RG=$(ibmcloud resource groups --output json | jq -r '.[] | select(.name == "default")'.id)

If you want to create a new resource group for your VMware assets e.g. with a name VMware, you can use the following commands:

VMWARE_RG_NAME="VMware"

VMWARE_RG=$(ibmcloud resource group-create $VMWARE_RG_NAME --output json | jq -r .id)
4. Then set your target to the wanted resource group.

ibmcloud target -g $VMWARE_RG







 Next steps 

The next step in the tutorial series is:



* [Provision a IBM Cloud VPC for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vpcvpc-bm-vmware-vpc)
Try out IBM Cloud, for free 

Looking to try out IBM Cloud®? Create an account and start building proof of concepts (POCs) with the many components available in IBM Cloud. You can try Lite and Free service plans to explore IBM Cloud at no cost while learning how to work in the cloud, use Watson, and more. This quick start guide is intended to help you get up and running on IBM Cloud without having to think about costs until you're ready.



 Before you begin 

Go to the [IBM Cloud console](https://cloud.ibm.com) and create an account. You're asked to enter your credit card information to secure your account and verify your identity. There are no costs that are associated with signing up, and you can try out IBM Cloud for free. You pay only for billable services that you choose to use, with no long-term contracts or commitments.

You're set up with a [Pay-As-You-Go account](https://cloud.ibm.com/docs/account?topic=account-accountspaygo), and you can access the full IBM Cloud catalog, including all Lite and Free plans. You receive a $200 credit to help get you started. You can use the $200 credit on IBM Cloud products that are used in the first 30 days.





 Step 1: Explore the catalog 

Explore the catalog for services that are free to use by filtering for Lite and Free pricing plans. You can work on your projects worry free, without the risk of generating a bill.



1. Go to the [catalog](https://cloud.ibm.com/catalog).
2. Select the Lite and Free pricing plan options.







 Step 2: Create an instance 

Create an instance of product that includes a free Lite plan or a Free tier pricing plan.



1. Select the tile from the catalog after reviewing the filtered list of products.
2. Enter any required information to create the instance.
3. Click Create.







 Step 3: Check out the tutorials
The following example creates an application called myfruitcounter that uses the docker strategy and provides the location for the source code in the current directory (.). You must also set the environment variables to connect to Cloudant.

ibmcloud ce app create --name myfruitcounter --build-source . --strategy dockerfile --env CLOUDANT_URL=<your_url> --env CLOUDANT_APIKEY=<your_key> --env DBNAME=fruitcounter

Example output

Creating application 'myfruitcounter'...
Packaging files to upload from source path '.'...
Submitting build run 'myfruitcounter-run-220727-142949868'...
Creating image 'private.us.icr.io/ce--6ef04-n2lgvg2l59v/app-myfruitcounter:220727-1929-y8ej0'...
Waiting for build run to complete...
Build run status: 'Running'
Build run completed successfully.
Run 'ibmcloud ce buildrun get -n myfruitcounter-run-220727-142949868' to check the build run status.
Waiting for application 'myfruitcounter' to become ready.
Configuration 'myfruitcounter' is waiting for a Revision to become ready.
Ingress has not yet been reconciled.
Waiting for load balancer to be ready.
Run 'ibmcloud ce application get -n myfruitcounter' to check the application status.
OK

https://myfruitcounter.n2lfrg2876v.us-south.codeengine.appdomain.cloud
2. Test the app by opening the provided URL for the fruit picker app. Pick your favorite fruit and submit. The running total of fruit choices is displayed. You can refresh the application and choose another fruit. The addition is displayed in the running total.
Step 1: Clone the sample app 

First, clone the repo and change the directory to where the sample app is located.

git clone https://github.com/IBM-Cloud/get-started-ruby

cd get-started-ruby





 Step 2: Run the app locally (optional) 



1. Run the app locally by running the following commands.

rbenv install 2.3.0

rbenv local 2.3.0

gem install bundler

bundle install

rails server
2. View your app at the following URL: http://localhost:3000







 Step 3: Prepare the app for deployment 

To deploy to IBM Cloud, it can be helpful to set up a manifest.yml file. The manifest.yml file includes basic information about your app, such as the name, how much memory to allocate for each instance and the route. We've provided a sample manifest.yml file in the get-started-ruby directory.

Open the manifest.yml file, and change the name from GetStartedRuby to your app name, app_name.

apps:
- name: GetStartedRuby
random-route: true
memory: 128M

In this manifest.yml file, random-route: true generates a random route for your app to prevent your route from colliding with others. If you choose to, you can replace random-route: true with host: myChosenHostName, supplying a host name of your choice.





 Step 4: Deploy the app 

You can use the IBM Cloud® CLI to deploy apps.



1. Log in to your IBM Cloud® account, and select an API endpoint.

ibmcloud login

If you have a federated user ID, instead use the following command to log in with your single sign-on ID. See [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id) to learn more.

ibmcloud login --sso
2. Target a Cloud Foundry org and space:
Getting Started 

This tutorial uses a [sample app](https://github.com/IBM-Cloud/clouddatabases-helloworld-cloudfoundry-examples/tree/node/rabbitmq) to demonstrate how to connect a Cloud Foundry application in IBM Cloud to an IBM Cloud® Messages for RabbitMQ service. The application creates, reads from, and writes to a database that uses data that is supplied through the app's web interface.

If you have already created your deployment and want to connect to your RabbitMQ, you can skip to [getting your connection strings](https://cloud.ibm.com/docs/messages-for-rabbitmq/howto-getting-connection-strings.html) and [connecting with the RabbitMQ Management plug-in](https://cloud.ibm.com/docs/messages-for-rabbitmq/connecting-cli-client.html).



 Before you begin 



* You need an [IBM Cloud account](https://cloud.ibm.com/registration).
* Install [Node.js](https://nodejs.org/) and [Git](https://git-scm.com/downloads).
* See [Getting to production](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-best-practices) for guidance on setting up a basic IBM Cloud® Messages for RabbitMQ deployment.







 Step 1: Create a Messages for RabbitMQ service instance 

Create a Messages for RabbitMQ service from the [Messages for RabbitMQ page](https://cloud.ibm.com/catalog/messages-for-rabbitmq/) in the IBM Cloud catalog.

Choose a service name, region, organization and space to provision the service in, and for the Select a database version field, choose Latest Preferred Version. In this example, the service name is "example-rabbitmq".

Click Create to provision your service. Provisioning can take a while to complete. You are taken back to your IBM Cloud Dashboard while the service is provisioning.

You cannot connect an application to the service until provisioning is complete.