vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To confirm that the name of your app is valid, check that the name of your app consists of lowercase alphanumeric characters, '-', and that the name starts and ends with an alphabetic character.
3. To confirm that the image for your app exists, review the error message for information about the failure.

a. To deploy applications in Code Engine, you need to first create a container image that has all the runtime artifacts your application needs to run, such as runtime libraries. You can use many different methods to create the image, including building your app from source code by using the [build container images](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image) feature available in Code Engine. Your image can be downloaded from either a public or private image registry. For more information about accessing private registries, see [Adding access to a private container registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registry).

b. If you use the app create command in the Code Engine CLI, specify the name of the image that is used for your application by using the format REGISTRY/NAMESPACE/REPOSITORY:TAG where REGISTRY and TAG are optional. If REGISTRY is not specified, the default is docker.io. If TAG is not specified, the default is latest. For more information about the format to use to specify the repository for your image, see the [ibmcloud ce app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command.
4. To confirm that you can access the referenced image, verify the location of your image and confirm that you have permissions to access the image.

If the image is located in a container image registry, such as Docker Hub or IBM Cloud Container Registry, check that you added registry access to Code Engine and that you are using the correct registry secret.
Whether your code exists as source in a local file or in a Git repository, or your code is a container image that exists in a public or private registry, Code Engine provides you a streamlined way to run your code as an app.



* If you have a container image, per the [Open Container Initiative (OCI) standard](https://opencontainers.org/), then you need to provide only a reference to the image, which points to the location of your container registry when you create and deploy your app. You can deploy your app with an image in a [public registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app) or [private registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-private).
* If you are starting with source code that resides in a Git repository, you can choose to let Code Engine take care of building the image from your source and deploying the app with a single operation. In this scenario, Code Engine uploads your image to IBM Cloud® Container Registry. To learn more, see [Deploying your app from repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-source-code). If you want more control over the build of your image, then you can choose to [build the image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image) with Code Engine before you create and deploy your app.
* If you are starting with source code that resides on a local workstation, you can choose to let Code Engine take care of building the image from your source and deploying the app with a single CLI command. In this scenario, Code Engine uploads your image to IBM Cloud® Container Registry.
--file FILE
: Input through the file. File format Supported - JSON.





 Example 

To update description a feature with ID ibm-discount using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac feature update --environment_id "production" --name "Indian IBMers" --feature_id "ibm-discount" --description "Discount given to IBM Indian employees" --enabled_value true --disabled_value false --segment_rules '[{"rules":{"segments":"ibm_employees"]}],"value": true,"order": 1}]' --collections '[{"collection_id":"corporatediscount","enabled": true}]' --tags "discount,sale" --enabled true



 Output 

The command returns the following output:

updated_time 2021-02-02T18:06:03Z
description Discount given to IBM Indian employees
enabled_value true
disabled_value false
segment_rules <Array>
created_time 2021-02-02T17:52:46Z
name Indian IBMers
type BOOLEAN
enabled true
collections <Array>









 ibmcloud ac feature update-values 

You can update values of a feature (This method allows the update of feature name, feature enabled_value, feature disabled_value, tags, description, and feature segment rules, however this method does not allow toggling the feature flag and assigning feature to a collection.), by using the command:

ibmcloud ac feature update-values {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --tags TAGS --segment_rules SEGMENT_RULES}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
* When customizing the display of search results, the changes made sometimes do not save after clicking the Apply button. To work around this issue, refresh the browser and try to make the changes again. * When setting up a data source or web crawler for your collection, if you enter an incorrect configuration, then try to update it on the Processing settings page, the data source update or crawl may not start when you click the Apply changes and reprocess button. You can confirm this issue by opening the Activity page for your collection to see if processing has started. If you see that processing has not started for your data source, click the Recrawl button, then the Apply changes and reprocess button. If you see that processing has not started for your web crawl, click the Stop button, then the Recrawl button. IBM Cloud Pak for Data

When running Helm tests on the core deployment using helm test core, the core-discovery-api-post-install-test will return a FAILED status. This is due to a bug within the test pod's image. The test result can be ignored as the failure is not related to anything within the deployment.
* By default, Optical Character Recognition (OCR) is set to off when you create any Project type with the tooling. However, if you create a Project using the API, OCR is set to on. To work around this issue, open the Tooling and change the Project setting to off. * When Optical Character Recognition (OCR) is set to on for a Collection AND no trained Smart Document Understanding (SDU) model is applied, PNG, TIFF, and JPG files will not be processed for text recognition. Images embedded in PDF, Word, PowerPoint, and Excel documents will not be processed - only the non-image portion of these documents will be processed for text recognition. To work around this issue, import or train an SDU model and reprocess the collection. This will allow text to be extracted from the images. * After you create a Search Skill in Watson Assistant and are directed to the Watson Discovery tooling, the screen is blank. This happens because the URL is missing the Discovery instance ID. To work around this issue:
<-- <ol> -->
* If a custom data set exists for a toolchain, it can be used in the policy rules that are defined within the JSON file. You are not always required to define the custom data set within the JSON file.
* The sample JSON file that is provided for the policies-update command lists all of the possible rule types that you can specify in a policy. All of the fields in those rules are required.
* Use only one rule per data set.
* The name field within a rule is optional.







 Sample JSON file for the policies-update command 

This sample JSON file contains two custom data sets and two policies. The first policy, name: "Orders", contains all of the rule types that you can use within a policy.

{
"custom_datasets": [
. {
"lifecycle_stage": "integrationtest",
"type_of_test": "test",
"label": "Integration Test"
},
{
"lifecycle_stage": "covtest",
"type_of_test": "code",
"label": "Coverage Test"
}
],
"policies": [
{
"name": "Orders",
"description": "Composite Policy.",
"rules":
{
"name": "rule1",
. "description": "Unit Test Rule with regression",
"stage": "unittest",
"percentPass": 100,
"criticalTests":
"Get Weather with incomplete zip code"
],
"regressionCheck": true
},
{
"name": "rule2",
"description": "Unit Test Rule without regression",
"stage": "integrationtest",
"percentPass": 98,
"criticalTests":
"'Get Weather with incomplete zip code'"
],
},
{
"name": "rule3",
"description": "Functional test Rule",
Schematics Blueprints is a [beta feature](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitations) that are available for evaluation and testing purposes. It is not intended for production usage. Refer to the list of [limitations](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitationssc-bp-beta-limitation) for the beta release.



 Blueprint apply fails 

Review the following sections to help debugging blueprint apply failures.



 Blueprint apply fails with message "Install of module Failed" 

 What’s happening 

When you run the blueprint apply command, it fails with message that the install of a module fails.

 Why it’s happening 

When you Apply a configuration, Schematics runs Terraform Apply operation against all modules that which have pending updates. Errors when you run the Terraform operations against the modules result in a job failure, and cause the Apply job to fail.

Example error message

Modules to be installed
SNO Type Name Status
1 Workspace basic-resource-group ACTIVE
2 Workspace basic-cos-storage FAILED

Blueprint job running eu-gb.JOB.Blueprint-Basic-Example.0cebdb53

Waiting:0 Draft:0 Connecting:0 In Progress:0 Inactive:0 Active:1 Failed:1

Type Name Status Job ID
Blueprint blueprint Basic Example FULFILMENT_FAILED eu-gb.JOB.Blueprint-Basic-Example.0cebdb53
Workspace basic-resource-group ACTIVE
Workspace basic-cos-storage FAILED

Errors:
Install of module basic-cos-storage Failed

Error on Terraform Apply operation. Review log for cause of failure
Review job failure log yes/no [y/N]> y

Workspace Name basic-cos-storage
Workspace ID eu-gb.workspace.basic-cos-storage.7378a905
Log Summary (last few lines)..........
--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID for the feature flag.

--include INCLUDE (optional)
: Include the associated collections in the response.





 Example 

To get a feature with ID ibm-discount, run the following command:

ibmcloud ac feature get --environment_id "production" --feature_id ibm-discount



 Output 

The command returns the following output:

name type disabled_value updated_time feature_id description enabled_value created_time order rules value
IBMers BOOLEAN false 2021-02-02T17:52:46Z ibm-discount Discount given to IBM employees true 2021-02-02T17:52:46Z 1 <Array> true









 ibmcloud ac feature update 

You can update a feature, by using the command:

ibmcloud ac feature update {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --enabled ENABLED --tags TAGS --segment_rules SEGMENT_RULES --collections COLLECTIONS}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
: Feature name. Required field - input either as a flag or from file.

--feature_id FEATURE_ID
: Feature ID. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the feature. Required field - input either as a flag or from file.

--enabled_value ENABLED_VALUE
: Value of the feature when it is enabled. Required field - input either as a flag or from file.

--disabled_value DISABLED_VALUE
: Value of the feature when it is disabled. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the feature. Required field - input either as a flag or from file.

--enabled ENABLED
: The state of the feature flag.

--segment_rules SEGMENT_RULES
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg).
2. Preview how the information in the readme file is displayed to users when they install the Operator.
3. If you need to make changes, edit the information in the source code and import the updated code file to your private catalog.
4. Click Save.
5. Click Next.







 Step 6: Validate the software version 



1. From the Validate product tab, select the target cluster and project, and click Next.
2. Configure your Schematics workspace by entering the name of your workspace, selecting a resource group, selecting a Schematics region, and optionally adding tags. Then, click Next.

You can accept the default options that are displayed for your workspace name and resource group.
3. Click Validate.







 Step 7: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog. For more information, see [Formatting controls in your readme file](https://cloud.ibm.com/docs/sell?topic=sell-sell-format-controls).



 Manage compliance controls 

You can review the controls that were added from your readme file and add additional controls.



1. Click Add controls.
2. Choose a profile.
3. Select the controls that you want to add to your version.
4. Click Add.







 Run Code Risk Analyzer scan 

Scan your source code with Code Risk Analyzer to identify any security vulnerabilities that you need to assess.



1. Click Run scan.
2. Wait for the scan to finish.







 Add Security and Compliance Center scan 

Add the scans that you previously ran in Security and Compliance Center.
This value is required.<br><br><br><br> * The name must begin with a lowercase letter.<br> * The name must end with a lowercase alphanumeric character.<br> * The name must be 55 characters or fewer and can contain letters, numbers, and hyphens (-).<br><br><br> 
 --image The name of the image that is used for this application. This value is required. The format is REGISTRY/NAMESPACE/REPOSITORY:TAG where REGISTRY and TAG are optional. If TAG is not specified, the default is latest. For images in [Docker Hub](https://hub.docker.com/), you can specify the image with NAMESPACE/REPOSITORY, as the default for Registry is docker.io. For other registries, use REGISTRY/NAMESPACE/REPOSITORY or REGISTRY/NAMESPACE/REPOSITORY:TAG. 







 Next steps 



* After your app deploys, [access your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-access-service) through a URL.
* You can create a [custom domain mapping](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappings) and assign it to your app. For more information about deploying apps across multiple regions with a custom domain name, see [Configuring a highly available application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-multiple-regions).
* Now that your app is deployed, consider making your apps event-driven.
Building actions from templates 

When you create actions, you can choose a template that relates to the problem you’re trying to solve. Templates help tailor your actions to include items specific to your business need. The examples in each template can also help you to learn how actions work.

Templates are available for different use cases, for example, booking a meeting, creating a support ticket, or making a payment. Templates include all the pieces that make up an action, such as steps, conditions, and different response types to collect customer answers.

You can use templates in English-language assistants only.

Some or all of these features are included as examples in action templates:



Features

 Feature Description More information 

 Step conditions A step condition is a Boolean test, based on a runtime value. The step is used only if the test evaluates as true. [Adding conditions to a step](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-step-conditions) 
 Options synonyms Synonyms are variations of an option value that customers might enter. [Options](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-collect-infocustomer-response-type-options) 
 Customized response validation When you edit a step that expects a customer response, you can customize how validation errors are handled. [When your customer gives invalid answers](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-handle-errorsstep-validation) 
 Action variables When customers reply to your assistant, they share information about themselves and what they want. Your assistant remembers this information, and other information about a conversation, as variables. [Using variables to manage conversation information](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-manage-info) 
 Session variables A value that is not necessarily tied to a particular action can be stored as a session variable. Session variables are long-term memory: they persist throughout the user's interaction with the assistant, and your assistant can reference them from any action.
Both absolute and relative paths are accepted. 
 -I, --toolchainid Required If the TOOLCHAIN_ID environment variable is set, this flag is optional. If both the environment variable and the flag are provided, the value of the flag overrides the value of the environment variable. 
 -D, --dryrun Optional The option to simulate only the changes, with no updates. 
 --region Optional The ibmcloud region of the toolchain. 





 Example 

ibmcloud doi policies-update -F "policies/policy.json" -I b531487c-9c22-4f3b-9d20-5be408d57891 --region jp-tok
or
ibmcloud doi policies-update --file "policies/policy.json" --toolchainid b531487c-9c22-4f3b-9d20-5be408d57891





 JSON file structure for the updatepolicies command 

A valid JSON file structure contains two fields:

{
"custom_datasets": [],
"policies": []
}



* You can specify any number of policies (and custom data sets) for the array.
* If the specified policy (and custom data set) already exists for a toolchain, the policy is updated or created.
* Either the custom_datasets or policies array can be empty, or both can be empty.
* The only valid values for a type_of_test custom data set are test and code.
* If a custom data set exists for a toolchain, it can be used in the policy rules that are defined within the JSON file. You are not always required to define the custom data set within the JSON file.
* The sample JSON file that is provided for the policies-update command lists all of the possible rule types that you can specify in a policy. All of the fields in those rules are required.
* Use only one rule per data set.
* The name field within a rule is optional.







 Sample JSON file for the policies-update command
You can use the console to create environment variables for your apps and jobs that fully reference a secret or reference individual keys in a secret.

Before you can reference a secret, it must exist. See [create a secret](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secret-create-ui). For this example, create a secret that is named target-secret with the key-value pair of TARGET=Sunshine.



1. To reference a defined secret from your app or job, [create an environment variable](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvarenvvar-create-ui). The environment variable can fully reference an existing secret or reference an individual key in an existing secret. When you fully reference a secret (or configmap), you can optionally specify a prefix. For example, if you fully reference the mysecret secret from the myapp application and use the mysecret_ prefix, each key in the secret is prefixed with mysecret_.
2. After you create environment variables, you must restart your app or job for the changes to take effect. For apps, save and deploy your app to update the app with the environment variables that you defined. For jobs, submit your job to update the job with the environment variables that you defined.
3. After the app or job status changes to Ready, you can test the application or run the job. For an app, click Test application and then click Send request in the Test application pane. To open the application in a web page, click Application URL. In the myapp example, because a prefix was specified for the fully referenced mysecret secret, all the keys of this secret are referenced as environment variables and are prefixed with mysecret_. For example, these environment variables display as mysecret_secret1=mysecret1 and mysecret_secret2=mysecret2.
You must be within the context of a [project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project) before you use build commands.

For more information about working with builds, see [Building a container image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image).

You can use either build or bd in your build commands. To see CLI help for the build commands, run ibmcloud ce build -h.



 ibmcloud ce build create 

Create a build.

ibmcloud ce build create --name BUILD_NAME [--build-type BUILD_TYPE] [--commit COMMIT] [--context-dir CONTEXT_DIR] [--dockerfile DOCKERFILE] [--force] [--git-repo-secret GIT_REPO_SECRET] [--image IMAGE] [--output OUTPUT] [--quiet] [--registry-secret REGISTRY_SECRET] [--size SIZE] [--source SOURCE] [--strategy STRATEGY] [--timeout TIMEOUT]



 Command Options 

-n, --name
: The name of the build. Use a name that is unique within the project.



* The name must begin and end with a lowercase alphanumeric character.
* The name must be 63 characters or fewer and can contain lowercase alphanumeric characters and hyphens (-).



This value is required.

--build-type, --bt
: The type of build. Valid values are git and local. If the type of build is local, then the --source, --commit, and --git-repo-secret options are not valid. This value is optional. The default value is git.

--commit, --cm, --revision
: The commit, tag, or branch in the source repository to pull. The commit option is allowed if the --build-type option is git and not allowed if the --build-type option is local. This value is optional.
* To create and set an environment variable for your app, use the --env option with the [app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) or [app update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-update) command. The following example creates the myapp application that uses the icr.io/codeengine/codeengine image, and defines the envA and envB environment variables.

ibmcloud ce application create --name myapp --image icr.io/codeengine/codeengine --env envA=A --env envB=B
* To update environment variables for an existing application, use the --env option with the [app update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-update) command. The following example updates the myapp application to overwrite the value of envA and adds the envC environment variable.

ibmcloud ce application update --name myapp --env envA=AA --env envC=C







 Create and update environment variables for your job 

Set and update environment variables for your job as follows,



* To create and set an environment variable for your job, use the --env option with the [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) command.