vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Download, modify, and redeploy your Cloud Foundry app with the command-line interface 

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

Use the IBM® Cloud Foundry command-line interface (CLI) to download, modify, and redeploy your Cloud Foundry apps and service instances.

Before you begin, [download and install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).

Then install the IBM Cloud Foundry CLI by running the following command:

ibmcloud cf install

After you install the CLI, you can get started:



1. Change to the directory where your code is located.

cd <your_new_directory>
2. Make changes to your app code as you see fit. For example, if you are using an IBM Cloud sample app and your app contains the src/main/webapp/index.html file, you can modify it and edit "Thanks for creating ..." to say something new. Ensure the app runs locally before you deploy it back to IBM Cloud.

When deploying your app back to IBM Cloud, the manifest.yml is used to determine your app’s URL, memory allocation, number of instances, and other crucial options . You can [read more about the manifest file](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html) in the Cloud Foundry documentation.

Also pay attention to the README.md file, which contains details such as any applicable build instructions.

If your app is a Liberty app, you must build it before redeploying.
3. Log in to IBM Cloud with your IBMid. If you have multiple accounts, you will be prompted to select the account to use. If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login
* [Get the Code ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://github.com/IBM/powerai-notebook?cm_sp=IBMCode-_-accelerate-training-of-machine-learning-algorithms-_-Get-the-Code)
* [View the Demo ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.youtube.com/watch?v=1nnWj6W7QJI&cm_sp=IBMCode-_-accelerate-training-of-machine-learning-algorithms-_-View-the-Demo)







 Build a cognitive recommendation app with Swift 

Build a Swift-based mobile chatbot to provide recommendations, reservations, and event planning.



* [Learn more ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/patterns/build-a-cognitive-recommendation-app-with-swift/)
* [Get the Code ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://github.com/IBM/CognitiveConcierge?cm_sp=IBMCode-_-build-a-cognitive-recommendation-app-with-swift-_-Get-the-Code)
* [View the Demo !
Install Liberty features 

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

The Liberty for Java runtime includes [a subset of features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-liberty_featuresliberty_features) that are available in Liberty. You can install features that are not included in the runtime by running the Liberty installUtility command as a Cloud Foundry pre-runtime hook when the app is pushed to IBM Cloud.

For a full list of available features, see [Liberty features](https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/rwlp_feat.html).

For information on using pre-runtime hooks, see [Configure Pre-Runtime Hooks](https://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.htmlprofile) in the Cloud Foundry documentation.



1. In the root directory of the app that you want to push to IBM Cloud, create a .profile.d directory.
2. In the .profile.d directory, create a script file that runs the installUtility command as shown in the following example.

This example installs the audit-1.0 feature.

!/bin/sh
echo "Installing audit-1.0"
export PATH=$PATH:$HOME/app/.java/jre/bin

$HOME/app/.liberty/bin/installUtility install audit-1.0 --acceptLicense

You can install multiple features by specifying additional features names separated by spaces.
3. Push your app to IBM Cloud, using the -p option to specify the app's root directory.

For example, run the following command to push your app:
* [Generate a workspace plan using the UI](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksplan-wks-ui)



* [Verifying workspace plan](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksverify-wks-plan-ui)



* [Generate a workspace plan using the CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksplan-wks-cli)



* [Verifying workspace plan execution](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksverify-wks-plan-cli)



* [Generate a workspace plan using the API](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksplan-wks-api)



* [Verifying workspace plan execution](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksverify-wks-plan-api)



* [Generating a workspace plan using Terraform](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wksplan-wks-terraform)
* [Next steps](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wkssch-plan-wks-nextsteps)



[Running a workspace apply](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wkssch-deploy-wks)



* [Before you begin](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksdisplay-prerequisites)
New! Deploying apps and running jobs with Code Engine is even easier!
: With Code Engine, you can now go from source code to a running app or a configured job with a single command. The app create command automatically runs the container build and deploys your app in a single step. You don't even need to know about building container images or working with registries. Just let Code Engine handle all these processes for you.



* If you are familiar with "push source code" platforms, such as Cloud Foundry, start by exploring the tutorial [Deploying Cloud Foundry applications in Code Engine: Getting started](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-tutorial).
* If you are familiar with Code Engine, see [Deploying your app from repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-source-code), [Deploying your app from local source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-local-source-code), [Creating a job from repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-code), and [Creating your job from local source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-local-source-code).



CLI version 1.30.0 released
: This version of the CLI supports deploying apps and configuring jobs from local or repository source code with a single command. See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 21 April 2022 

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

Updated versions for buildpacks
This SAP Note (and others) is found at [https://support.sap.com/en/index.html](https://support.sap.com/en/index.html)





 Before you begin 

Before you use the scripts in the Bastion cli or Schematics:



* Set up your account to access the VPC. Make sure that your account is [upgraded to a paid account](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct).
* If you have not already, create a bastion server to store the SAP kits. For more information, see [Automate SAP bastion server - SAP media storage repository](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server). You need the floating IP from your bastion server for deployment.
* Download the SAP kits from the SAP Portal to your Deployment Server. Make note of the download locations. Ansible decompresses the files. For more information, see the readme file, in the respective GitHub repository for Schematics and Terraform and on the About page for the Catalog Tile.
* [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
* [Create or retrieve your SSH key ID](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorial). You need the 40-digit UUID for the SSH key, not the SSH key name.
* Terraform should be already installed on the bastion server that you deployed. For more information, see [Bastion server for SAP deployment](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server).
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).



Before you work with local source, make sure that your source is in an accessible location on your local workstation.



 Creating a function from local source code with the CLI 

This example uses the following Node.js code, saved as a main.js file. You can substitute your own code.

async function main(params) {
console.log(process.env);
console.log(params.__ce_headers);
console.log("params: "+params);
return {
statusCode: 200,
headers: { 'Content-Type': 'application/json' },
body: params };
}

module.exports.main = main;



1. Change to the directory that contains the main.js file or record the path to it.
2. Create a function called myfun-local that uses a the main.js file as source. This command automatically builds and pushes the code bundle to a Container Registry namespace in your account. If you do not have an existing Container Registry namespace, Code Engine automatically creates one for you.

ibmcloud ce fn create --name myfun-local --runtime nodejs-18 --build-source main.js

Example output

Preparing function 'myfun-local' for build push...
Creating function 'myfun-local'...
Packaging files to upload from source path 'main.js'...
Submitting build run 'myfun-local-run-230123-111011111'...
To use the API and CLI interfaces, the Terraform-based automation code is available in this [public GitHub repository](https://github.com/IBM/ibm-spectrum-scale-ibm-cloud-schematics).

The offering enables the initial Spectrum Scale-based HPC cluster creation. Any updates that are needed post-deployment regarding Spectrum Scale configuration or setup should be performed by using Spectrum Scale tools and commands. If you use the Schematics interface to make changes to configuration properties and reapply those changes, you can cause disruptions to the running Spectrum Scale cluster. Restoring it back to a working state might not be easy.



 Architecture diagrams 

Zoom

![Architecture diagram](https://cloud.ibm.com/docs-content/v1/content/8249e0dc29214a2ec0dab6b6ab2240d81b1b89ba/hpc-spectrum-scale/images/hpccluster_scale_scratch_architecture.svg)

Figure 1. Architecture diagram of a IBM Spectrum Scale cluster on IBM Cloud

Zoom

![Architecture diagram peristent](https://cloud.ibm.com/docs-content/v1/content/8249e0dc29214a2ec0dab6b6ab2240d81b1b89ba/hpc-spectrum-scale/images/hpccluster_scale_persistent_architecture_05_26_22.svg)

Figure 2. Architecture diagram of a IBM Spectrum Scale cluster using persistent storage on IBM Cloud
This view handles all the deployment steps (install, approve, commit) which are required by the smart contract lifecycle on channels that are enabled with application capability v2.0 or higher.

Follow these steps if you have your channel is configured with application capability V2 or higher and a .tar.gz smart contract package.

To launch the deploy view:



1. Check that you are connected to the network in the Fabric Environments pane.
2. Expand the channel that you want to deploy your smart contract to.
3. Click + Deploy smart contract.



There are three steps to deploying a smart contract by using the deploy view.



 Step 1: Choose a smart contract to deploy 



1. Use the dropdown to select the smart contract package that you want to deploy.
2. Click Next to proceed.







 Step 2: Create definition 



1. Provide a name and a version for the smart contract in the appropriate input fields. By default these parameters will be filled by the name and version of the package.
2. (Optional) Enter a customendorsement policyin the appropriate input field.
3. (Optional) Select Add file to browse to your collection configuration file if your smart contract uses private data, such as the Private Data Contract example.
4. Click Next to proceed.







 Step 3: Deploy 



1. Click Deploy to automatically install, approve, and commit the smart contract on all of the networks peers.
2. (Optional) Use the Perform commit toggle to enable or disable committing this smart contract definition to the channel.
3. (Optional) Click Additional peers to endorse commit transactions to select or deselect any available additional peers that you need to approve this smart contract definition.



At this point, you smart contract is now "committed" on the channel. If you have changed your smart contract code and then repackaged it, you can use the deploy view and follow the same steps as above to upgrade the smart contract definition that you have deployed to the network.







 Deploying your smart contract (channel application capability V1)
* [Set up a Load Balancer for VPC to expose your app publicly](https://cloud.ibm.com/docs/containers?topic=containers-vpc_ks_tutorialvpc_ks_vpc_lb)
* [What's next?](https://cloud.ibm.com/docs/containers?topic=containers-vpc_ks_tutorialvpc_ks_next)







 Migrating an app from Cloud Foundry to a cluster 

[Migrating an app from Cloud Foundry to a cluster](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_tutorial)



* [Objectives](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_objectives)
* [Audience](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_audience)
* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_prereqs)
* [Download app code](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_1)
* [Create a Docker image with your app code](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_2)
* [Deploy a container from your image](https://cloud.ibm.com/docs/containers?topic=containers-cf_tutorialcf_3)







 Installing the CLI and API 

[Installing the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-install)



* [Understanding the CLI tools](https://cloud.ibm.com/docs/containers?topic=containers-cli-installcli-understand)
* [Next steps](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-plan-wkssch-plan-wks-nextsteps)



[Running a workspace apply](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wkssch-deploy-wks)



* [Before you begin](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksdisplay-prerequisites)
* [Perform a workspace apply using the UI](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksdeploy-wks-ui)



* [Verifying workspace apply](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksverify-wks-list-ui)



* [Perform a workspace apply using the CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksdeploy-wks-cli)



* [Verifying workspace deploy](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksverify-wks-deploy-cli)



* [Perform the workspace deploy using the API](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksdeploy-wks-api)



* [Verifying workspace deploy](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksverify-wks-deploy-api)



* [Perform the workspace deploy with Terraform](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-deploy-wksdeploy-wks-terraform)
For more information, see [Integrating with phone](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-phone).



 Integrating SMS with Twilio 



 Before you begin 

If you don't have a text messaging phone number, set up an SMS with Twilio account and get a phone number.



1. Go to the [Twilio website](https://www.twilio.com/).
2. Create an account or start a free trial.
3. From the Develop tab in the sidebar, click Phone Numbers. If Phone Numbers is not present, go to the Search Bar at the top and search for 'Phone Numbers', then select Buy a number.
4. Follow the instructions to Buy a number.

When you get a Twilio phone number, it supports voice, SMS, and MMS automatically. Your new phone number is listed as an active number.



Keep the Twilio web page open in a web browser tab so you can refer to it again later. You can also pin Phone Numbers to the sidebar.





 Set up the integration 

To set up the integration, complete the following steps:



1. Go to the Integrations page by clicking the integrations icon (![Integrations icon](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/integrations-icon.png)) in the left menu.
2. Click Add on the SMS tile.
3. Click SMS with Twilio tile.
4. Click Confirm.
5. From the Twilio site, click on your account name in the upper left menu to go to your account dashboard.

Copy the following values and store them temporarily, so you can paste them into the SMS with Twilio integration setup page in the upcoming steps.



* Account SID
* Auth token



6. Return to the SMS with Twilio integration setup page.
buildctl github.com/moby/buildkit v0.10.6 0c9b5aeb269c740650786ba77d882b0259415ec7

 helm version --client
version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}

 ibmcloud -version
ibmcloud version 2.12.1+b8488a1-2022-10-31T15:08:10+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.61 false
cloud-internet-services[cis] 1.14.9 true
code-engine[ce] 1.40.1 true
container-registry 1.0.2 true
container-service[kubernetes-service/ks] 1.0.459 false
cra 1.0.4 false
doi 0.4.0 false
schematics 1.12.4 true

 ibmcloud dev --version
ibmcloud dev version 2.15.0

 java -version
openjdk version "17.0.5" 2022-10-18
IBM Semeru Runtime Open Edition 17.0.5.0 (build 17.0.5+8)
Eclipse OpenJ9 VM 17.0.5.0 (build openj9-0.35.0, JRE 17 Linux amd64-64-Bit Compressed References 20221018_325 (JIT enabled, AOT enabled)
OpenJ9 - e04a7f6c1
OMR - 85a21674f
JCL - 32d2c409a33 based on jdk-17.0.5+8)

 ant -version
* If you configured Slack, the toolchain is set up to send notifications about deployment status to the Slack channel that you specified.





After the toolchain is created, a notification appears that provides a link to a tutorial to learn more about how to use the template.





 Next steps 

Check out the available [toolchain templates and tutorials](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_about).



 Terraform resources and data sources, SDKs, and HTTP APIs 

You can use Terraform to create and manage toolchains, tool integrations, and Tekton delivery pipelines as code. For more information about using Terraform with Continuous Delivery, see [Setting up Terraform for Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-terraform-setup) and try the Terraform toolchain template to [Develop a Kubernetes app with Helm toolchain](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-cd-toolchain-simple-helm).

You can use HTTP APIs and programming language SDKs to create, read, update, delete, and more against toolchains, tool integrations, and Tekton delivery pipelines. For more information about these APIs and SDKs, see [Continuous Delivery Toolchain v2](https://cloud.ibm.com/apidocs/toolchain) and [Continuous Delivery Tekton Pipeline v2](https://cloud.ibm.com/apidocs/tekton-pipeline) in the [API & SDK reference library](https://cloud.ibm.com/docs?tab=api-docs).
[Subscribing to Object Storage events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialsubscribe-cos-tutorial)



* [Determine your Object Storage bucket and region](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialdetermine-cos-bucket-and-region)
* [Assigning the Notifications Manager role to Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialnotify_mgr)
* [Create your app (or job)](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialcreate-app-cos)
* [Create a subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialcreate-subscription-cos)
* [Testing your subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialtest-subscription-cos)
* [Update your Object Storage subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialupdate-subscription-cos)
* [Clean up for Object Storage tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialclean-subscription-cos)



[Subscribing to Kafka events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialsubscribe-kafka-tutorial)
The name of the subscription must be unique within your project.
2. Run [ibmcloud ce app list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-list) or [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-list) to make sure that your destination app or job exists. If the app or job doesn't exist, create the application with the [ibmcloud ce app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command or create the job with the [ibmcloud ce job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create) command.



If these solutions do not solve your issue, try one of the resources in [getting support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-get-support).
If you are using the [IBM Developer Tools](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscode) to develop and package your smart contract, the tooling performs the vendoring for you. This process is not required for smart contracts that are written in Java or Node.js, nor for Go smart contracts that use the [Go contract-api](https://github.com/hyperledger/fabric-contract-api-go).

Java
The build.gradle file for the smart contract must be updated:



1. If the smart contract uses the shadowjar 2.x plugin, then it should be updated to version 5 by using the following code:

plugins {
id 'com.github.johnrengelman.shadow' version '5.1.0'
id 'java'
}
2. The repositories section of the file must contain the maven URL for jitpack, for example:

repositories {
...
maven {
url 'https://jitpack.io'
}
}



Init functions

If the smart contract was written using the low-level APIs provided by the Fabric Chaincode Shim API, your smart contract needs to contain an Init function that is used to initialize the chaincode. This function is required by the smart contract interface, but does not necessarily need to be invoked by your applications. Because you cannot use the console to deploy a smart contract that contains an Init function, you need to move that initialization logic into the smart contract itself and call it separately. For example, the smart contract can use a reserved key to check whether the smart contract has already been initialized or not. If not, then call the initialization logic, otherwise proceed as usual.