vania-janet/multiturn-rag-retrieval-data huggingface dataset:
How do I address a failed validation when using projects? 

You tried to validate changes to a configuration in a project, but the validation failed.

  What’s happening 

The project displays a Needs attention alert and a message displays on the Activity tab that states that the validation failed.

  Why it’s happening 

An issue occurred with the configuration during the validation process. You can't deploy your changes until issues are resolved. Go to the needs attention widget on the Overview tab and select Changes failed validation to view more information about the failure.

  How to fix it 



*  If the plan failed, it likely means that a required input value, such as an authentication method, hasn't been supplied yet. Or, one of the provided inputs isn't valid. The plan can also fail if the deployable architecture that your configuration is based on is invalid. Determine the exact problem from the logs, and update the input values if needed. If the logs indicate an error with the Terraform version, your settings in IBM Cloud® Schematics might need to be updated. For more information, see [How do I update my Terraform version?](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-troubleshoot-terraform-version&interface=ui)
*  If the compliance check failed, the deployment is not compliant with the compliance profile. The failure might be caused by input values or because of compliance issues with the current version of the deployable architecture that you're configuring. Review which controls failed and adjust the inputs or update the deployable architecture until the validation is successful. If it's necessary, [an administrator can override and approve changes](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-approve-failed-validation) that failed due to the Code Risk Analyzer scan.
// of the vulnerability management process by using standards for:..
// SA-11 DEVELOPER SECURITY TESTING AND EVALUATION | DYNAMIC CODE ANALYSIS
// The organization requires the developer of the information system, system component, or information system service to employ dynamic code
// analysis tools to identify common flaws and document the results of the analysis.
// Control passed if:
// 1- the script is one of the blessed ones AND
// 2- the status is passed OR
// 3- the status is failed AND issues have been opened AND there are no expired issues AND prod CR approved manually
"evidence_type_id": "com.ibm.dynamic",
"version": "1.0.0",
"date": "2020-05-06T12:00:00Z", // date of task run
"origin": {
"url":"https://us-south.git.cloud.ibm.com/open-toolchain/compliance-pipelines/-/blob/master/definitions/mytask.yaml", // where the task is taken from
"version": "423792" // commit id representing the task version used to produce the evidence
}
"toolchain_crn": "crn:v1:bluemix:public:toolchain:us-south:a/190e0b4ce4cd013159917665213ddc51:7467a214-f404-4e23-acab-2e57e935d138::" // CRN of the toolchain
"pipeline_id": "b1cfb6a4-813d-4fec-bbf7-ce662e8ce4e0", // the id of the pipeline that generated this piece of evidence
"pipeline_run_id": 12345, // this is the id of the pipeline run that generated this piece of evidence
"last_scan_date": "24-03-2020 UTC", // the last time the scan was run
I have used targeting to override flag and property values for a segment, but the default values are still being applied. 

  What’s happening 

Override values are not being assigned to segments.

  Why it’s happening 

Attributes in your code may be missing or inconsistent with the attributes used in your segment rule.

Segments are defined in the App Configuration service using attributes, and attributes are defined in your application code. If an attribute in a segment rule does not exist in your application, or has a value that is not part of the rule, then the app instance will not be recognized as part of a segment, and the default value will be assigned.

  How to fix it 

In your app code, include a JSON object that contains the various attribute values you want to use in your segment rules.

Also, be sure the keys and values found in your app match the keys and values used in your App Configuration segment rule. See example below.

const entityId = "john_doe";
const entityAttributes = {
'city': 'Bangalore',
'country': 'India'
}
let feature = client.getFeature(<feature_id>);
let featureValue = feature.getCurrentValue(entityId, entityAttributes);

Entity attributes are used to evaluate if the entity is valid for the segment, and the corresponding value of the segment is returned for the feature flag.

The same fix is applicable for properties.
Error executing docker build cmd for stage-0: exit status 1
...
COPY file-to-copy.js file-to-copy.js:
------
failed to compute cache key: "/file-to-copy.js" not found: not found

By default, the Code Risk Analyzer bom-generate command builds the Dockerfiles from the context of the location of the Dockerfile itself. If you want to build the Dockerfiles from the context of the root project directory, use the cra-docker-build-context parameter to allow the Code Risk Analyzer to build the Dockerfiles from this context.







 Removing stored Code Risk Analyzer data 

The Code Risk Analyzer plug-in does not store any client data in its databases. However, earlier versions of Code Risk Analyzer Tekton tasks securely stored the results of vulnerability scans in its database.

To request the removal of any client data that might be stored in the Code Risk Analyzer, contact [IBM Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 FAQs 

Get answers to frequently asked questions about using the Code Risk Analyzer CLI.



 How can I determine why the CLI failed? 

Before you call the Code Risk Analyzer CLI, set the IBMCLOUD_TRACE environment variable to true to turn on the debug log.

export IBMCLOUD_TRACE=true

Observe the API calls and the responses that are shown in the log to determine the exact reason for failure.





 How can I debug a BOM command that fails to pull a base image from a private registry. 

Make sure that you are authenticated with the registry where the base image resides by using the ibmcloud cr login command or the docker login command.





 How can I debug a BOM command that is failing to analyze a Dockerfile? 



* Verify that the Dockerfile does not have any issues by running the docker build command and making sure that it passes.
* If your Dockerfile requires ARG to be passed, make sure that the ARG is set as an environment variable.
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.



To update an environment variable that references a secret, see [updating environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvarenvvar-update-ui) and [considerations for updating environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvarenvvar-upd-consider).

To remove an environment variable that references a secret, see [deleting environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvarenvvar-delete-ui).

For example, let's use the previously defined mysecret secret that you defined from the console with a job and fully reference this secret with an environment variable.



1. [Create and run a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan). For this example, create a Code Engine job that uses the icr.io/codeengine/codeengine image and then run the job. When a request is sent to this sample job, the job reads the TARGET environment variable, and the job prints Hello ${TARGET} from Code Engine and prints a listing of environment variables. If the TARGETenvironment variable is empty, Hello World from Code Engine is returned.

From the Jobs page,



1. Create a job; for example, myjob.
2. Specify icr.io/codeengine/codeengine as the image reference.
3. Click Create to create the job.
Click Environment variables to open the tab and then click Add environment variable. Add a literal environment variable with the name of TARGET with a value of Sunshine. The icr.io/codeengine/testjob outputs the message, Hello <value_of_TARGET>!>.
8. Click Done.
9. Click Save to save the update to the job.
10. Click Submit job to submit the updated job.
11. From the Submit job pane, this time change the CPU value to one of the valid CPU choices for the specified memory. Notice that you must use [valid memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo). Click Submit job again to run this job. The system displays the status of your job on the Job details page. Notice the updated CPU value in the Configuration section of the job details.
12. By [viewing job logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-joblogs-ui) for this job, the output of the updated job is Hello Sunshine!.







 Updating a job with the CLI 

With the CLI, you can update an existing job configuration or specify your changes on a new job run.



 Updating a job configuration with the CLI 

You can update an existing job configuration with the [ibmcloud ce job update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-update) command.



1. Use the job update command to update the myjob job to reference a different image.

ibmcloud ce job update --name myjob --image icr.io/codeengine/testjob

Run the ibmcloud ce job get -n myjob command to display details of the updated job.

Example output

Name: myjob
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
* You can also [create a custom domain mapping](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappings) for your app.



Each update of an application configuration property creates a new revision of the application.



* Find information to [update your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-app).



You can use Iter8 to [validate your application code and latency](https://cloud.ibm.com/docs/codeengine?topic=codeengine-slovalidationtut) and then determine if your revision is ready to use or if you must roll back to a more stable version.

Need help? Check out [troubleshooting tips for applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-apps). If you need more help, try [getting support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-get-support).





 Run your job 

To get started, read [plan a container image for Code Engine jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-containerimage) and [Batch job workloads](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cebatchjobs).

Do you want to create a job definition?

By creating a job definition, you can more easily run your job multiple times based on your configuration.



* [Create a job from a public repository](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job).
* [Create a job from images in Container Registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job-crimage).
Adding conditions to a step 

An action represents a business process that helps customers answer their questions or solve their problems. Such a process must adapt to different specifics, based on information provided by customers or otherwise available at run time. For example, the steps for withdrawing money from a savings account might be slightly different from the steps for withdrawing for a checking account.

A step condition is a boolean test, based on some runtime value; the step executes only if the test evaluates as true. This test can be applied to any variable, such as an action variable containing the customer response from a previous step. By defining step conditions, you can create multiple pathways through an action based on different possible runtime values.

For more information about variables, see [Using variables to manage conversation information](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-manage-info).

A basic step condition is expressed in the following form:

If{variable}{operator}{value}

where:



* {variable} is the name of a variable or an expression.
* {operator} is the type of test to apply to the variable value (for example, is or is not).
* {value} is the value to compare to the variable.



For example, a step condition might read:

IfWithdraw from which account?isChecking

This condition evaluates as true if the customer's response to the previous Withdraw from which account? step is Checking.

Conditions can be grouped together to construct complex tests.

To add a step condition:



1. Open the step. Click the condition field at the beginning of the step:

Zoom

![Step editor with condition field highlighted](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/step-condition.png)

Condition field
2. Select with conditions from the drop-down list. The Conditions section expands.
3.
Limitations & Exclusions 

Maximo Application Suite Dedicated is implemented using a defined set of technologies and operates within a security profile designed to ensure our client's data is secure and the applications operate efficiently and effectively. As a result of the decisions made regarding technologies and to meet the high security standards, there are differences between what is available using the Dedicated Services and what a client could do if they hosted and operated the Suite themselves.

The following items are not included or allowed in the Maximo Application Suite Dedicated offering:



 Databases 

The following are database limitations of the MAS-Dedicated offering:



* Only DB2 is supported. Oracle and SQLServer are not supported. Conversion services are available.
* If converting from Oracle to DB2, Oracle compatibility mode is not supported.
* DB2 Text Search is not supported.
* Running SQL statements (update/insert/delete) directly on databases is not allowed and IBM SRE team will not be able to execute those statements for you. DBC scripts are not allowed. Customers must carry out these changes using the UI via different means for example using Automation scripts or MIF. For further details on use of automation scripts, please see document below:



[https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/introduction/whatisautoscript](https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/introduction/whatisautoscript)



* SQL Scripts can be run on Production databases on an exception-only basis. Please see [Running SQL Scripts in Production](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-supportrunning-sql-scripts) for details.







 Manage Application 

No Java extensions are supported. It is assumed the Manage auomation scripting capability will be used for these types of extensions. Existing Maximo customers who have Java extensions will need to move these functions into automation scripts within the application. See link above for further details





 LA Fixes 

LA (Limited Availability) aka "one off" or "hot" fixes are the customer's responsibility to manage.
Applying autolearning 

You can apply autolearning when the following conditions are met:



* Ask clarifying questions is enabled in global settings. For more information, see [Asking clarifying questions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-understand-questionsunderstand-questions-ask-clarifying-question).
* You publish a version of your assistant to the live environment. For more information, see [Publishing your content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish).
* Your customers are interacting with a channel or custom application that is connected to the live environment.



To apply autolearning improvements to your assistant responses:



1. On the Actions page, click Global settings![Gear icon](https://cloud.ibm.com/docs-content/v1/content/icons/settings.svg).
2. Click the Autolearning tab.
3. Ensure the Use autolearning to modify responses with training from live environment switch is set to On.
4. In the draft environment, you can preview your actions or your assistant. With autolearning set to On, preview in the draft environment uses the autolearning training from the live environment. For more information, see [Using Preview to test your action](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-reviewreview-test) or [Previewing your assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-preview-share).
5. If you are happy with the results from testing the autolearning improvements in the draft environment, publish a new version of your assistant to the live environment to apply the improvements. For more information, see [Publishing your content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish).







 Learning from your data 

Observations are made of only your customers' choices to improve only your assistant.
Any lines in the specified file that are empty or begin with are ignored. For this example, use a file that is named colors_multi.txt that contains the key-value pairs: color1=yellow, color2=orange, and color3=purple.

ibmcloud ce configmap create --name mycolorconfigmapmulti --from-env-file colors_multi.txt







 Listing configmaps with the CLI 

Now that the configmap is created, use the configmap list command to list all configmaps in your project or use the configmap get command to display details about a specific configmap. For example,

ibmcloud ce configmap get --name mycolorconfigmap

Example output

Getting configmap 'mycolorconfigmap'...
OK

Name: mycolorconfigmap
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 11s
Created: 2020-10-14 14:10:57 -0400 EDT

Data:
---
TARGET: blue, green, red









 Updating configmaps 

You can change key-value pairs for existing configmaps.



 Updating configmaps from the console 

You can update an existing configmap and its key-value pairs from the console.



1. You can update key-value pairs for your defined configmaps from the console in one of the following ways.



* Go to the Secrets and configmaps page for your project and locate the configmap that you want to update. Click the name of the configmap that you want to update to open it.
* If your configmap is referenced by an app or job, then use the links in the environment variables table on the Environmental variables tab of your app or job.
By clicking a violation on the [control pane](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-compliance-cp) the issues comprising the violation are displayed. By clicking an issue the resources that are passing, failing, or have temporary accepted exceptions are displayed.

By clicking an issue the available remediation options are displayed.

You can see the impact of the remediation, review the resource attributes, and, if needed, enter required values into the patch code.

If a required value can be auto-detected, it will be inserted automatically and the Value input field will be read-only.





 Verifying patches 

Patch code will be displayed for you to review. Patch code will be displayed if the patch will be applied manually.

You can download the code in the Continure Remediation section (preferred) or copy it using cut and paste.





 Applying patches 



 Applying patches manually 

If Git has not been integrated with IBM Cloud Security and Compliance Center Workload Protection, you can do a manual remediation.



1. Click Manually Apply Patch.
2. Click Download to download the patch.
3. Apply the patch to your environment.









 Accepting violation risks 

In some cases a failing control can be safely ignored for a period of time. Accepting the risk will allow the resource to pass and the compliance score for the zome will improve.

In the Remediation page:



1. Click Accept Risk.
2. Enter the required fields to comply with your organization's audit and best practices.

Valid reasons are: Risk Owned, Transferred, Avoided, Mitigated, Not Relevant or Custom.

In the details explain to an auditor the reason for accepting the risk, or the risk management action taken.

Indicate when you want the risk acceptance to expire and the resource to return to a failed state. Options are 7, 30, 60, or 90 days, a custom time frame, or never.
3. Click Save.
If you define step conditions that check the Ran successfully variable, you can create steps that enable your assistant to respond differently depending on whether the call to the extension succeeded. (For more information about step conditions, see [Step conditions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-step-conditions).)

The following example shows a step condition that checks for a failure from an extension in step 3. By using this condition, you can create a step that tells the customer there was an error, and perhaps offers to connect to an agent for more help.

![Step condition checking for extension failure](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/extension-check-failure.png)





 Conditioning on HTTP status 

In addition to the Ran successfully variable, you might also want to create a step condition based on the HTTP status of the response. By doing this, you can create steps that handle the situation differently depending on the cause of the failure. For example, if the call failed because of a timeout error (HTTP status 408), you might want to retry the call.

There are many possible HTTP status codes, and different methods use different status codes to indicate various types of success or failure. To condition on the HTTP status, you need to know what HTTP status codes the external service returns, and under what circumstances. These status codes are typically specified in the OpenAPI document that describes the external API.

To create an step condition based on the HTTP status code, follow these steps:



1. For the value you want to test, click Expression.
2. In the expression field, type a dollar sign ($) to show the list of available variables.
3. Select any variable that is a response value from the extension. (It doesn't matter which variable you select, as long as it is an extension response variable).