vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Speech to Text Node.js App - React app using the Watson Speech to
Text service to transform voice audio into written text.

6. Text to Speech Node.js App - React app using the Watson Text to
Speech service to transform text into audio.

7. Visual Recognition Node.js App - React app using the Watson
Visual Recognition service to analyze images for scenes, objects, text,
and other subjects.

-------------------------
0. Return to the previous selection

===============================================================================
? Enter selection number:> 3

The hardest option for developers everywhere is still required: naming your app. Follow the example and type webapplication, then press enter.

? Enter a name for your application> webapplication

Later, you can add as many services, like data stores or compute functions, as needed or wanted through the web console. However, type 'n' for no when asked if you want to add services now. Also, if you haven't already set a resource group, you may be prompted at this time. You may skip this by typing 'n' at this prompt.

Using the resource group Default (default) of your account

? Do you want to select a service to add to this application? [Y/n]> n

One way to manage a containerized application is with orchestration software, like Kubernetes, which is a de facto standard in development. But for this tutorial, we can let the Cloud Foundry service manage a single Docker container that holds the code, libraries, and configuration needed by your app.

Type '4' and press enter to use 'IBM DevOps' for integrating CD within your project lifecycle.
Terraform automation modules are written not to return on initial resource creation, but to return only when the resource is fully initialized and available to be used by subsequent automation modules. This is different compared to the experience of creating resources through the UI. In the UI control is returned immediately and initialization continues in the background. With automation modules the perception is that they can take significantly longer to run.





 How do you configure the version of Terraform to used? 

The version of Terraform used for an environment is user determined by the blueprint template TF_VERSION parameter. This parameter can be used to control when the Terraform version for environment is updated to the next release or version.

The Terraform version in use and allowable for modules is constrained by the value of required_ version in the Terraform module code.

During Apply operations Terraform programmatically determines the Terraform version that is supported by the automation modules, looking for a terraform block with a [required_version](https://developer.hashicorp.com/terraform/language/settingsspecifying-a-required-terraform-version) parameter. If the module required_version constraint does not support the desired template version, the operation will be failed.





 Is it possible to specify the CLI parameters as a file? 

A number of ways to create a blueprint configuration using the CLI.

For Schematics Blueprints, the [Schematics plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin) version must be greater than the 1.12.5.



1. Using a local file in JSON format.

Example

ibmcloud schematics blueprint create --file payload_complex.json
2. Using command-line arguments.

Example
For example, if /farms/{farm_id}/barns/{id} is used to retrieve, mutate, or delete a barn, the path used to list or create barns MUST be /farms/{farm_id}/barns and not /farms/{id}/barns.

As in the example above, and where otherwise sufficient, the singular form of the prior path segment SHOULD be used to disambiguate a parent resource's identifier from its child's identifier. For example, /farms/{farm_id}/barns/{barn_id}/cows/{id} SHOULD be used instead of /farms/{farm_id}/barns/{farm_barn_id}/cows/{id}.



 Children without identifiers and custom operations 

Where there is no ambiguity, path parameters SHOULD NOT be qualified. For example, if a book resource type allows genres wholly represented by strings to be added with the path PUT /books/{id}/genres/{genre} where {genre} is a string such as "sci-fi," and there is no request- or response-body representation of a genre and no genre identifier, the book identifier path parameter SHOULD remain unqualified as {id}.

Similarly, if a resource supports a custom operation modeled as an appended verb in a path segment, such as POST /servers/{id}/reboot, the server identifier path parameter SHOULD remain unqualified as {id}.









 Defining path parameters 

In an OpenAPI definition, path parameters SHOULD be defined in such a way as to maximize reuse and minimize duplication and potential inconsistency. To this end, path parameters MUST be enumerated in the [Path Item](https://spec.openapis.org/oas/v3.0.3path-item-object) object and not the [Operation](https://spec.openapis.org/oas/v3.0.3operation-object) object. Further, path parameters SHOULD be defined as [Components](https://spec.openapis.org/oas/v3.0.3components-object) and referenced in Path Item objects.
* [Considerations and Limitations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansibleansible-limits)
* [Getting started](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansibleansible-getting-started)
* [Next steps](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansibleansible-next-steps)
* [Where to find support](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansibleansible-support)



[Building an IBM Blockchain Platform network using Ansible playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build)



* [Prerequisites](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build-prereqs)
* [Step one: Gather console connection information](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build-console)
* [Step two: Clone the Ansible collection](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build-clone)
* [Step three: Get started with using the playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build-get-start)
* [Step four: Run a playbook](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build-run-playbook)
* [Step five: Run a script](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ansible-buildansible-build-run-script)
For more information about exporting the definition for an entire pipeline, see [Modifying, exporting, and deleting Continuous Delivery pipeline data](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_personal_datamanaging_pipeline_data).





 Can I manage delivery pipelines by using Terraform? 

You can use Terraform to provision, update, and de-provision Tekton pipelines, definitions, properties, triggers, and trigger properties. For more information about using Terraform with Tekton pipelines, see [Working with Tekton pipelines](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines), and the [ibm_cd_tekton_pipeline resources documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline).

You cannot use Terraform to trigger Tekton pipeline runs, or to manage Tekton pipeline runs and logs. You can perform these tasks with the Tekton pipeline APIs, or by using the console.

You cannot use Terraform to manage Classic pipelines. You can manage Classic pipelines only by using the console.





 Can I manage delivery pipelines by using an API? 

You can use HTTP APIs or selected programming language SDKs to provision, update, and de-provision Tekton pipelines, definitions, properties, triggers, and trigger properties. You can also use the APIs and SDKs to trigger Tekton pipeline runs, and to manage Tekton pipeline runs and logs. For more information about using Tekton pipelines with the API, see [Working with Tekton pipelines](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines), and the [CD Tekton Pipeline API docs](https://cloud.ibm.com/apidocs/tekton-pipeline).

You cannot use APIs to manage Classic pipelines. You can manage Classic pipelines only by using the console.
To use any of the predefined [Schematics images](https://cloud.ibm.com/docs/schematics?topic=schematics-version-constraintsschematics-image-ov), you must explicitly declare the version of the IBM Cloud Provider plug-in in your Terraform template that includes the provider versions that you want.

If IBM Cloud Provider plug-in version is not declared in your Terraform template, the latest version of the provider plug-in is automatically used in Schematics.

Example to specify a predefined Schematics image:

The following example shows how to use the Schematics image that was built for the IBM Cloud Provider plug-in v1.39.1. This image includes specific versions for other providers, such as the REST API provider.

terraform {
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
version = "v1.39.1"
}
}

Example to use specific Terraform provider versions:

To use a different IBM Cloud Provider plug-in version, or to pin your Terraform configuration file to a specific version of another external provider, such as AWS, Helm or Kubernetes, use the following syntax.

terraform {
required_providers {
ibm = {
source = "IBM-Cloud/ibm"
version = "> 1.38.1"
}
aws = {
version = ">= 2.7.0"
source = "hashicorp/aws"
}
}







 Specifying version constraints in Ansible 

Schematics currently supports the latest Ansible version v2.9.23 only. When you create a Schematics action, you must ensure that your Ansible playbooks can be run with this version. You cannot specify a specific Ansible version for your playbook.

However, if you use existing Ansible roles or collections in your playbook, you can specify the version of the role or collection that you want to run by using a requirements.yml file.
Design your application for high availability (recommended)](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-high-availability)
* [14. Use endpoint detection and remediation (EDR) tooling to detect malicious code](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-endpoint-detection-remediation)
* [15. Regularly scan for open ports / protocols](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-network-threat-detection)
* [16. Secure and manage secrets and certificates](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-secrets-management)
* [17. Tag all IBM Cloud resources with security attributes](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-security-attributes)
* [18. Monitor for security and compliance against a baseline configuration](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-security-compliance-monitoring)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-next-steps)



[Best practices and requirements for software](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practices-softwarebest-practices-software)



* [1.
Use the beta 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).

Important: Starting with Liberty for Java buildpack v3.28, the beta runtime is no longer included.

The Liberty beta features provide early access to new functionality and programming models that might be included in a future Liberty release. Most of the beta features can also be used in apps deployed to IBM Cloud®.

Important: The beta features are for development and test purposes only and cannot be used in production. For the complete terms of use, see the [beta license agreement](http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/downloads/wlp/beta/lafiles/en.html).



Table 1. Liberty Beta features available in Liberty for Java in IBM Cloud

 Features 

 jdbc-4.3 
 logstashCollector-1.1 
 validator-1.0 



To use the Liberty beta features in IBM Cloud, you will need to do the following:



1. [Deploy a server directory or a packaged server](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushing) with one or more beta features enabled in the server.xml file as in the example that follows:

<server>
<featureManager>
<feature>jdbc-4.3</feature>
</featureManager>
</server>
2. Set the IBM_LIBERTY_BETA environment variable to true. This variable directs the Liberty buildpack to install and enable the beta features for your app. For example:



* Using the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli):
[Satellite reference architecture use cases](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-use-casessatellite-architecture-use-cases)



* [US regional bank](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-use-casessatellite-architecture-use-cases-1)
* [Multinational bank](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-use-casessatellite-architecture-use-cases-2)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-use-casesnext-steps)



[Satellite reference architecture shared responsibility model](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-shared-responsibilitiessatellite-architecture-shared-responsibilities)



* [Shared responsibilities for IBM Cloud products](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-shared-responsibilitiessatellite-architecture-shared-responsibilities-roles)
* [Additional roles for shared responsibility matrix](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-shared-responsibilitiessatellite-architecture-shared-responsibilities-roles)
* [Overview of shared responsibilities](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-shared-responsibilitiesoverview-by-resource)
* [Satellite location control plane and workload clusters](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-shared-responsibilitiessatellite-location-control-plane-workload-clusters)
* [Installing Terraform and configuring resources for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceinstall-terraform)
* [What's next?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceterraform-setup-next)



* [Resources](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceterraform-supported-resources)
* [Data Sources](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceterraform-supported-data-sources)









 Getting started with Code Engine workloads in Satellite 

[Getting started with Code Engine workloads in Satellite](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce)



* [Limitations for Beta](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-beta-limits)
* [Prerequisites for running Code Engine workloads in Satellite](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-prereqs)
* [Setting up service-to-service access](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-authority)
* [Setting up Code Engine on Satellite](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-setup)
* [Creating a project in a compute environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-project)
* Generate a map visualization of COVID-19 cases around the world.



This tutorial requires some basic knowledge of the Command Line Interface (CLI) and basic knowledge of Node.js.

Because the MongoDB instance you require is not free, this tutorial is not cost-free. However, if you deprovision your resources after completion, the cost should not be more than a few dollars.



 What you need 

Before you begin, it's a good idea to have:



* An [IBM Cloud](https://cloud.ibm.com/login) pay-as-you-go account, [logged in to your account](https://cloud.ibm.com/docs/cli?topic=cli-getting-startedstep4-configure-idt-env).
* [Terraform](https://learn.hashicorp.com/tutorials/terraform/install-cli) - automates your resource provisioning.
* Access to a Mac or Linux terminal.
* [Node.js and npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm).
* [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - a free and open source-distributed version control system.
* [MongoDB Compass](https://www.mongodb.com/try/download/compass) to look at your data (optional).
* Tableau, to visualize your data. You need to set up a [30-day free trial](https://www.tableau.com/products/trial).







 Step-by-step instructions 



 Step 1: Obtain an API key to deploy infrastructure to your account 

Follow the steps [here](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uicreate_user_key) to create an API key. This key is used in Step 2.
The --force option can be used with the [app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create), [app update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-update), [job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create), [job update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-update), [jobrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-submit), or [jobrun resubmit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-resubmit) commands.

When you use the --force option with these commands, the action to create, update, or run the app or job completes; however, the app or job will not run successfully until the referenced configmap exists. If you add the --no-wait option in addition to the --force option to the command, the system completes the action and does not wait for the app or job to successfully run.

The following example describes how to reference a configmap that is not yet defined with an app by using the CLI.



1. [Create an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads) and reference the undefined myliteralconfigmap3 configmap. For this example, create a Code Engine app that uses the icr.io/codeengine/hello image. When a request is sent to this sample app, the app reads the environment variable TARGET and prints Hello ${TARGET}. If this environment variable is empty, Hello World is returned. Reference the myliteralconfigmap3 configmap.
Use an approved reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-reference-architecture)
* [2. Use only services that are IBM Cloud for Financial Services Validated](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-financial-services-validated-services)
* [3. Ensure all deployed software meets all controls](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-self-installed-software)
* [4. Implement a system of account, identity, and access management to enable a zero-trust environment](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-zero-trust)
* [5. Use and maintain non-production environments for development and testing](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-non-production-environments)
* [6. Enforce information flow policies and protect the boundaries of your application](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-boundary-protection)
* [7. Ensure all operator actions are executed through a bastion host](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-bastion-host)
* [8. Capture audit events and forward to a SIEM](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-audit-logs)
* [9.
The Terraform [parallelism](https://www.terraform.io/docs/cloud/workspaces/variables.htmlparallelism) flag is used to control the number of concurrent operations allowed for Terraform plan, Terraform apply, and Terraform destroy. A larger number can result in faster overall cluster create and destroy times. However, too large a value might result in operation failures. For plan and apply, it's recommended to use values up to 250, and for destroy, it's recommended to use values up to 100. Note that setting the values for parallelism is not possible when using the [Schematics UI](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-creating-workspace&interface=ui). However, the values for that flag can be set in the config.json file that is used when creating the [Schematics workspace](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-creating-workspace&interface=clicreate-workspace-cli) through the CLI:

"env_values":[
{
"TF_CLI_ARGS_apply": "-parallelism=250"
},
{
"TF_CLI_ARGS_plan": "-parallelism=250"
},
{
"TF_CLI_ARGS_destroy": "-parallelism=100"
}]
* Why is "Default" not working as the value for resource_group?

If you find that the "Default" value for resource_group does not work for you, check the resource groups setting on your account to determine what the actual name of the default resource group is. For instance, it might be "default" instead.



VMware Solutions



* What user accounts do I need for VMware Solutions?



* IBMid account. This account is required to access the IBM Cloud for VMware Solutions console. The console is a stand-alone user interface that is separate from the IBM Cloud infrastructure customer portal.
The sample shows how a producer sends messages to a consumer by using a topic. The same sample program is used to consume messages and produce messages.

Use the steps that are detailed in [Event Streams Getting Started](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-getting-started) to run the sample application.

Alternatively, you can also use your own applications to perform this validation.





 Step 4: (Optional) Test the Event Streams CLI 

In the previous step, you used the sample application to produce and consume messages. You can optionally use the information in [Event Streams CLI reference](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-cli_reference) to verify that the Event Streams CLI can communicate with your Event Streams deployment. With the Event Streams CLI you can easily work with topics and consumer groups.

Alternatively, you can also use your own applications to perform this validation.