vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"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
"result": "passed" | "failed"], // status of the check
"status": "enabled"|"disabled"], // status of the configuration
"issues": // link(s) to the issue(s) created to fix the github configuration (should be populated only if result is failed)
"https://acme.org/foo/123",
"https://acme.org/foo/124",
"https://acme.org/foo/125",
],
"required": "yes" | "no" ] // yes: this is an auditable step; no: this is a non auditable step
}, {
// SA-11(4) DEVELOPER SECURITY TESTING AND EVALUATION | MANUAL CODE REVIEWS
// The organization requires the developer of the information system, system component, or information system service to perform a
// manual code review of Assignment: organization-defined specific code] using Assignment: organization-defined processes, procedures, and/or techniques].
// Partial: CM-3(b) Reviews proposed configuration-controlled changes to the information system and approves or disapproves such changes with explicit consideration
// for security impact analyses;
// Control passed if:
* [Open-source statement](https://cloud.ibm.com/docs/blockchain?topic=blockchain-disclaimerdisclaimer-open-source-statement)
* [Chaincode support statement](https://cloud.ibm.com/docs/blockchain?topic=blockchain-disclaimerdisclaimer-chaincode-support-statement)







 Getting started 

[Build a network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network)



* [Sample network tutorial series](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-sample-tutorial)



* [The structure of this network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-structure)



* [Step one: Create a peer organization and a peer](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-create-peer-org1)



* [Creating your peer organization's CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-create-CA-org1CA)
* [Associating the CA admin identity](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-ca-admin)
* [Using your CA to register identities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-use-CA-org1)
This list is not exhaustive of all of the relevant commands that are available to use with projects. Rather, this list is a starting point for you to explore other commands that you can use with projects.Some of the following commands might require the installation of their specific plug-ins before you can run them.Run ibmcloud resource tag-attach]ibmcloud resource tag-attach] to attach tags to a project: ibmcloud resource tag-attach --tag-names TAG --resource-id PROJECT-CRN
Run ibmcloud resource search]ibmcloud resource search] to retrieve all of the resources in an account created by configurations in a project: ibmcloud resource search "service_tags:"schematics::project_id:PROJECT_ID""
Run ibmcloud schematics logs]ibmcloud schematics logs] to retrieve the log files for a Schematics workspace: ibmcloud schematics logs --id WORKSPACE_ID --act-id ACTION_ID] ! ! ! ! ! ! ! ] ]
<-- </section "id="section-project-relevant-commands-other" "> --><-- <section "id="section-project-schema-examples" "> --> Schema examples The following schema examples represent the data that you need to specify for a command option. These examples model the data structure and include placeholder values for the expected value type. When you run a command, replace these values with the values that apply to your environment as appropriate.<-- <section "id="section-cli-project-config-auth-example-schema" "> --> ProjectConfigAuth The following example shows the format of the ProjectConfigAuth object. {
"trusted_profile" : {
"id" : "exampleString",
"target_iam_id" : "exampleString"
},
"method" : "exampleString",
"api_key" : "exampleString"
}
Setting up Terraform for Code Engine 

Terraform on IBM Cloud® enables predictable and consistent creation of IBM Cloud services so that you can rapidly build complex, multi-tier cloud environments following Infrastructure as Code (IaC) principles. Similar to using the IBM Cloud CLI or API and SDKs, you can automate the creation, update, and deletion of your Code Engine workloads by using HashiCorp Configuration Language (HCL).

Looking for a managed Terraform on IBM Cloud® solution? Try out [IBM Cloud® Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started). With Schematics, you can use the Terraform scripting language that you are familiar with, but you don't have to worry about setting up and maintaining the Terraform command line and the IBM Cloud® Provider plug-in. Schematics also provides pre-defined Terraform templates that you can easily install from the IBM Cloud® catalog.



 Installing Terraform and configuring resources for Code Engine 

Before you can create workloads with Terraform, make sure that you have completed the following prerequisites.



* Make sure that you have the [required access](https://cloud.ibm.com/docs/codeengine?topic=codeengine-iam) to create and work with Code Engine resources.
* Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform. For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://developer.hashicorp.com/terraform/language).





1.
* IBM Cloud CLI - This CLI tool will enable you to interact with IBM Cloud.



* code-engine/ce plugin (code-engine/ce) v 1.29.1 or higher - Plugins extend the capabilities of the IBM Cloud CLI with commands specific to a service. The Code Engine plugin will give you access to Code Engine commands on IBM Cloud.
* Optional Container Registry plugin (container-registry)



* git to clone source code repository.
* Optional, if you want to test running the app locally you will need to [install Node.js](https://nodejs.org/).



You will find instructions to download and install these tools for your operating environment in the [Getting started with tutorials](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorials) guide.

To avoid the installation of these tools you can use the [Cloud Shell](https://cloud.ibm.com/shell) from the IBM Cloud console.





 Step 1: Create an instance of MongoDB database in the cloud 

In this section, you will create a Databases for MongoDB instance in the cloud. Databases for MongoDB is a database-as-a-service that is easy to configure and provides built-in backups and scaling. You can find many different types of databases in the [IBM Cloud catalog](https://cloud.ibm.com/catalog?category=databasesservices). To create a Databases for MongoDB instance follow the steps below.



1. If you are not logged in, use ibmcloud login or ibmcloud login --sso to log in interactively. Target your preferred IBM Cloud region and resource group. In the example below we will use the ca-tor (Toronto) region and the default resource group.

ibmcloud target -r ca-tor -g default

You can find more CLI commands in the [General IBM Cloud CLI (ibmcloud) commands](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cli) topic in the documentation.
2.
Sample Apps 

Explore our sample applications to learn more about what you can develop with Discovery.

[Learning path: Getting started with Discovery](https://developer.ibm.com/series/learning-path-watson-discovery/) This learning path is designed for developers interested in quickly coming up to speed on what Discovery offers and how to use it. It consists of step-by-step tutorials, deep-dive videos, and complete examples of working code. As you proceed through the learning path, you'll work with more complex features as well as different use cases for applying the service.

[Understanding Customer Feedback App](https://developer.ibm.com/patterns/get-customer-insights-from-product-reviews/?cm_sp=Developer-_-code-_-customer_insights) Easily extract insights from raw text review data. It walks you through a working example of a web application that queries and manipulates data from Discovery. And, with the aid of custom models using Watson Knowledge Studio (WKS), the data has additional enrichments that provide improved insights for user analysis.



* [Get the Code](https://github.com/IBM/watson-discovery-food-reviews?cm_sp=Developer-_-develop-your-own-watson-discovery-service-application-_-Get-the-Code)
* [View the Demo](https://www.youtube.com/watch?v=gzlUSyLccSg)



[Cognitive Search Web App](https://developer.ibm.com/patterns/create-an-app-to-perform-intelligent-searches-on-data/?cm_sp=Developer-_-code-_-search_pattern) Uses publicly available reviews on Airbnb listings to demonstrate how to use individual UI components to visualize insights. You can then easily switch out the dataset to adapt it to your own use cases.



* [Get the Code](https://github.com/IBM/watson-discovery-ui?cm_sp=Developer-_-develop-a-fully-featured-web-app-built-on-the-watson-discovery-service-_-Get-the-Code)
This example will only replicate the new version of the object created by the PUT copy request. In order to replicate all versions of the object, it would be necessary to copy each individual version as well.

The following example is written in Python, but the algorithm could be applied in any programming language or context.

import os
import sys
import ibm_boto3
from ibm_botocore.config import Config

 Create client connection
cos = ibm_boto3.client("s3",
ibm_api_key_id=os.environ.get('IBMCLOUD_API_KEY'),
ibm_service_instance_id=os.environ['SERVICE_INSTANCE_ID'],
config=Config(signature_version="oauth"),
endpoint_url=os.environ['US_GEO']
)

 Define the bucket with existing objects for replication
bucket = os.environ['BUCKET']

def copy_in_place(BUCKET_NAME):
print("Priming existing objects in " + bucket + " for replication...")

paginator = cos.get_paginator('list_objects_v2')
pages = paginator.paginate(Bucket=bucket)

for page in pages:
for obj in page['Contents']:
key = obj['Key']
print(" * Copying " + key + " in place...")
try:
headers = cos.head_object(
Bucket=bucket,
Key=key
)
md = headers["Metadata"]
cos.copy_object(
CopySource={
'Bucket': bucket,
'Key': key
},
Bucket=bucket,
Key=key,
TaggingDirective='COPY',
MetadataDirective='REPLACE',
Metadata=md
)
print(" Success!")
' --name=exampleString --labels=exampleString --description=exampleString --authorizations='{"trusted_profile": {"id": "exampleString", "target_iam_id": "exampleString"}, "method": "exampleString", "api_key": "exampleString"}' --compliance-profile='{"id": "exampleString", "instance_id": "exampleString", "instance_location": "exampleString", "attachment_id": "exampleString", "profile_name": "exampleString"}'
<-- </section "id="section-project-config-update-examples" "> --><-- <section "id="section-project-config-update-cli-output" "> --> Example output Sample response for a project configuration draft. {
"id" : "293c3c36-a094-4115-a12b-de0a9ca39be5",
"definition" : {
"name" : "env-stage",
"description" : "Stage environment configuration, which includes services common to all the environment regions. There must be a blueprint configuring all the services common to the stage regions. It is a terraform_template type of configuration that points to a GitHub repo hosting the Terraform modules that can be deployed by a Schematics workspace.",
"labels" : "env:stage", "governance:test", "build:0" ],
"locator_id" : "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global",
"type" : "terraform_template",
"input" : {
"name" : "account_id",
This tutorial is part 2 of a 4-part tutorial series where you learn IBM Cloud® DevSecOps best practices by using a complete reference implementation that is available as a service and powered by IBM Cloud® Continuous Delivery. In part 2 of this tutorial series, you use the toolchain template for continuous integration (CI) with security and compliance-related best practices in DevSecOps. It is preconfigured for continuous deployment with inventory integration, change management with Git Repos and Issue Tracking, evidence collection, and deployment to IBM Cloud Kubernetes Service.

Kubernetes service Continuous Delivery

+1

DevSecOps



* 1 hour
* 2023-06-06



[Part 3: Set up a CD toolchain for Infrastructure as Code](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac-cd)Part 3: Set up a CD toolchain for Infrastructure as Code

This tutorial is part 3 of a 3-part tutorial series where you learn IBM Cloud® DevSecOps best practices by using a complete reference implementation that is available as a service and powered by IBM Cloud® Continuous Delivery. In part 3 of this tutorial series, you use the toolchain template for continuous deployment (CD) with security and compliance-related best practices in DevSecOps.

Schematics Continuous Delivery

+1

DevSecOps



* 1 hour
* 2023-05-22



[Part 2: Set up a CI toolchain for Infrastructure as Code (Terraform)](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac-ci)Part 2: Set up a CI toolchain for Infrastructure as Code (Terraform)

This tutorial is part 2 of a 3-part tutorial series where you learn IBM Cloud® DevSecOps best practices by using a complete reference implementation that is available as a service and powered by IBM Cloud continuous delivery.
Movies demo database example 

The following example uses HTTP to create a text index for your sample database.

POST /my-movies/_index HTTP/1.1
Host: $SERVICE_URL
Content-Type: application/json
{
"index": {},
"type": "text"
}

See the following example that uses the command line to create a text index for your sample database:



* Curl
* Java
* Node
* Python
* Go



curl "$SERVICE_URL/my-movies/_index" 	-X POST 	-H "Content-Type: application/json" 	-d '{"index": {}, "type": "text"}'

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.IndexDefinition;
import com.ibm.cloud.cloudant.v1.model.IndexResult;
import com.ibm.cloud.cloudant.v1.model.PostIndexOptions;

Cloudant service = Cloudant.newInstance();

IndexDefinition indexDefinition = new IndexDefinition.Builder()
.build();

PostIndexOptions indexOptions = new PostIndexOptions.Builder()
.db("my-movies")
.index(indexDefinition)
.type("text")
.build();

IndexResult response =
service.postIndex(indexOptions).execute()
.getResult();

System.out.println(response);

import { CloudantV1 } from '@ibm-cloud/cloudant';

const service = CloudantV1.newInstance({});

let index: CloudantV1.IndexDefinition = {}

service.postIndex({
db: 'my-movies',
index: index,
type: 'text'
}).then(response => {
The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image updated its version of node.js to the current LTS version 16.15.1. If you need to use a different version of node.js, use nvm install v<node version> at the beginning of your script.

This image includes the following tools:

 node --version
v16.15.1

 npm --version
8.11.0

 jq --version
jq-1.6

 yq --version
yq version 2.4.1

 yq3 --version
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version 4.25.2

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.11", GitCommit:"38d3c1f3d5306401bcf39a71bad3b5a5106033d7", GitTreeState:"clean", BuildDate:"2022-03-16T14:08:11Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.10.3 c8d25d9a103b70dc300a4fd55e7e576472284e31

 helm version --client
Creative Commons Attribution Share Alike 3.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by-sa/3.0/legalcode](https://creativecommons.org/licenses/by-sa/3.0/legalcode)

REGULAR_EXPRESSIONS [posix-character-classes](https://en.wikibooks.org/wiki/Regular_Expressions/POSIX_Basic_Regular_Expressions), TEXT IN FOREIGN LANGUAGE [golang/text](https://github.com/golang/text/archive/cbf43d21aaebfdfeb81d91a5f444d13a3046e686.zip), NEP-0012-MISSING-DATA.RST [NumPy](https://github.com/numpy/numpy/blob/master/doc/neps/nep-0012-missing-data.rst), VIETNAMESE TEXT [golang.org/x/text](https://proxy.golang.org/golang.org/x/text/@v/v0.3.3-0.20200430171850-afb9336c4530.zip), RAMDA LOGO [RAMda](http://registry.npmjs.org/ramda/-/ramda-0.27.1.tgz), NEP-0012-MISSING-DATA.RST [NumPy](https://pypi.org/project/numpy/files), DATA LICENSE (GEOLITE COUNTRY AND CITY DATABASES) [geoip](https://github.com/maxmind/geoip-api-c/releases/tag/v1.6.12), NEP12 [NumPy], MAP_TEST.GO [x/text]





 Creative Commons Attribution Share Alike 4.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons.
[carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/devsecops//images/CI_toolchain_thumbnail.png)<br><br>Getting Started with DevSecOps in IBM Cloud - Part 1 - Continuous Integration Toolchain](https://video.ibm.com/embed/recorded/130714354)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/devsecops//images/CD_toolchain_thumbnail.png)<br><br>Getting Started with DevSecOps in IBM Cloud - Part 2 - Continuous Deployment Toolchain](https://video.ibm.com/embed/recorded/130714358)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>!
* Java smart contracts require the fabric-chaincode-shim at v1.4.6 or later, as this version is the first version that includes support for Java 11.
* For an example of a Java smart contract, see the [FabCar Java smart contract](https://github.com/hyperledger/fabric-samples/tree/release-1.4/chaincode/fabcar/java) from Fabric v1.4.



v2 APIs available

New IBM Blockchain Platform console APIs using the route /v2/ are now available. Use of the earlier /v1/ APIs continues to be supported. See [IBM Blockchain Platform APIs](https://cloud.ibm.com/apidocs/blockchain) for more information.

High Availability Certificate Authority

When a CA is deployed, replica sets can be configured to ensure High Availability of the node. Note that CA replica sets require a PostgreSQL database. Learn more in the [Building a high availability Certificate Authority (CA)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-ca) tutorial.





 6 February 2020 

Update default resource allocation

The default memory allocation for the peer container has been increased from 0.4GB to 1GB. When deploying a new peer, the peer container will now default to 1GB memory, but you can adjust this value according to your use case. Increasing the memory alleviates some resource contention that could occur during smart contract instantiation.

Existing peer containers are not impacted.

Peer and ordering node patch 1.4.3-1

The Ingress timeout for the gRPC web proxy has been increased to avoid an error during smart contract instantiation. It is recommended that you apply this patch to your existing peer and ordering nodes.





 11 December 2019 

Miscellaneous bug fixes





 15 November 2019 

Service availability in two new regions

The IBM Blockchain Platform for IBM Cloud is now available to be provisioned in two new IBM Cloud regions: US East, and AP South.
Preparing apps for actions 

Whether you bring an app with you, or you write a script specifically to respond to an event, your code must meet certain requirements before you create an action from it.

Each programming language has specific requirements to run, but most have the following general requirements:



* The expected name for the entry point into the code is main by default. If your entry point is not main, a custom name can be specified when the action is created, so take note of that name.
* Input parameters into your app and output results from your app must be formatted into a specific structure that can be passed between entities. The structure depends on your code language. For example, with Python apps, the input parameters must be a dictionary and the result of your app must be structured as a dictionary. Because you can also pass parameters in a structured object to your action. In JSON, for example, you might structure your code to expect an input parameter with JSON values from certain fields, like name and place.

JSON input example

{"name": "Dorothy", "place": "Kansas"}

JavaScript example

function main(params) {
return {payload: 'Hello, ' + params.person.name + ' from ' + params.person.place};
}
* If your app contains multiple files, they must be combined into one single file to be used in an action. You can either rewrite your code into one file or you can package the files and dependencies into a single archive file. If your runtime is not supported, you can package your app in a Docker image.

Code compilation is not required, but if possible for your runtime, compiling your code in advance can improve performance.





 Preparing JavaScript apps 

Before you create an action, get your JavaScript code ready. Confirm that your code is structured properly, then decide whether it needs packaged.



 Structuring JavaScript code 



* The expected name for the entry point function is main. If the function in your code is not main, take note of the name to specify it when the action is created.
* The input parameters are passed as a JSON object.