vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Any lines in the specified file that are empty or begin with are ignored. This value is required if --from-literal or --from-file is not specified.

--from-file, -f
: Create a configmap from a file. You must provide the path to the file as a value. This value is required if --from-literal or --from-env-file is not specified.

--from-literal, -l
: Create a configmap from a key-value pair. Must be in KEY=VALUE format. This value is required if --from-file or --from-env-file is not specified. This option can be specified multiple times.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

The following example creates a configmap that is named configmap-fromliteral with two key pair values: color=blue and size=large.

ibmcloud ce configmap create --name configmap-fromliteral --from-literal color=blue --from-literal size=large





 Example output 

Creating Configmap 'configmap-fromliteral'...
OK
Run 'ibmcloud ce configmap get -n configmap-fromliteral' to see more details.





 Example of a configmap with values from multiple files 

The following example creates a configmap that is named configmap-fromfile with values from multiple files.

ibmcloud ce configmap create --name configmap-fromfile --from-file ./color.txt --from-file ./size.txt
Any lines in the specified file that are empty or begin with are ignored.



 Creating a configmap with the CLI 

Create a configmap with the configmap create command in one of the following ways,



* Create a configmap directly on the command line by using the --from-literal option in KEY=VALUE format. For example,

ibmcloud ce configmap create --name myliteralconfigmap --from-literal TARGET=Sunshine
* Create a configmap by using the --from-file option to point to a file. By using this option, all the contents of the file become the value for the key-value pair. For this example, use a file that is named colors.txt, which contains the text blue, green, red.



* The following example uses the --from-file KEY=FILE format with the configmap create command:

ibmcloud ce configmap create --name mycolorconfigmap --from-file TARGET=colors.txt
* The following example command uses the --from-file FILE format with the configmap create command. In this example, TARGET (no extension) is the name of the file, which is the same as the name of the environment variable that is known to the example myjob job.

ibmcloud ce configmap create --name mycolorconfigmap2 --from-file TARGET



* Create a configmap by using the --from-env-file option to point to a file that contains one or more lines that match the format KEY=VALUE. Each line from the specified file is added as a key-value pair. 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
Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan

data.ibm_resource_group.resource_group: Reading...
data.ibm_resource_group.resource_group: Read complete after 1s [id=<your_resource_group_id>]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

 ibm_code_engine_project.code_engine_project_instance will be created
+ resource "ibm_code_engine_project" "code_engine_project_instance" {
+ account_id = (known after apply)
+ created_at = (known after apply)
+ crn = (known after apply)
+ href = (known after apply)
+ id = (known after apply)
+ name = "<your_project_name>"
+ project_id = (known after apply)
+ region = (known after apply)
+ resource_group_id = "<your_resource_group_id>"
+ resource_type = (known after apply)
+ status = (known after apply)
}

Plan: 1 to add, 0 to change, 0 to destroy.
2. Run terraform apply to create the resources that are defined in the plan.

terraform apply

data.ibm_resource_group.resource_group: Reading...
data.ibm_resource_group.resource_group: Read complete after 1s [id=<your_resource_group_id>]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

 ibm_code_engine_project.code_engine_project_instance will be created
+ resource "ibm_code_engine_project" "code_engine_project_instance" {
+ account_id = (known after apply)
+ created_at = (known after apply)
+ crn = (known after apply)
[SonarQube tool](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops_set-up_sonarqube_orig.png)

Figure 19. SonarQube tool









 Step 4: Create the CI toolchain 

Create toolchain:



* Click Create in the Summary step and wait for the toolchain to be created.

You can configure the individual toolchain integrations after the pipeline is created.



Zoom

![DevSecOps Summary](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-ci-summary.png)

Figure 20. DevSecOps Summary





 Step 5: Explore the CI toolchain 

The created CI toolchain looks like this:

Zoom

![DevSecOps Continuous Integration Toolchain](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-ci-explore-pipeline-created.png)

Figure 21. DevSecOps Continuous Integration Toolchain

It contains two pipelines:



* PR: triggers when a new PR is submitted in the app repository
* CI: manually run or triggers when a PR is merged to master in the app repository







 Run the PR-CI Pipeline 

To start the PR pipeline, you should create a merge request in your application repository. To achieve this, do the following:



1. On the CI toolchain page, click the application repository tile. By default, it gets created with a name compliance-app-<timestamp>.
* [Creating a virtual server instance with the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=uicreating-virtual-servers-ui)
* [Creating a virtual server instance with the CLI - provision with a stock or custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cliinstance-create-from-image-cli)
* [Creating a virtual server instance with the API - provision from a stock or custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=apicreate-instance-stock-custom-image-api)
* [Creating an instance using Terraform](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=terraformcreate-instance-using-terraform)







 Prerequisites and limitations 

Before you create a custom image, you must verify that your custom image meets the custom image requirements and that the operating system is supported.



 Custom image considerations 

All custom images must meet the following requirements：



* Contain a single file or volume
* Is in qcow2 or vhd format
* Is cloud-init enabled
* The operating system is supported as a [stock image](https://cloud.ibm.com/docs/vpc?topic=vpc-about-imagesstock-images)
* Size doesn't exceed 250 GB
* The minimum size is 10 GB. For any image that is less than 10 GB, the size is rounded up to 10 GB.







 Operating system considerations 



* Make sure that your image is supported as an [x86 stock image](https://cloud.ibm.com/docs/vpc?topic=vpc-about-images) or an [s390x stock image](https://cloud.ibm.com/docs/vpc?topic=vpc-vsabout-images) on IBM Cloud® Virtual Private Cloud.
[Creating a job from images in a private registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job-privatecreate-job-private)



* [Creating a job that references an image in a private registry with the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job-privatecreate-job-private-console)
* [Creating a job with an image from a private registry with CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job-privatecreate-job-private-cli)
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-create-job-privatenextsteps-jobcreatepriv)



[Creating a job from repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-coderun-job-source-code)



* [Creating your job from repository source code from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-coderun-job-source-code-ui)
* [Creating your job from repository source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-coderun-job-source-code-cli)
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-source-codenextsteps-jobcreatesource)



[Creating your job from local source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-local-source-codejob-local-source-code)
Attributes: []iampolicymanagementv1.ResourceAttribute{
accountIDResourceAttribute, serviceNameResourceAttribute,
serviceInstanceResourceAttribute, resourceTypeResourceAttribute,
resourceResourceAttribute},
}

options := iamPolicyManagementService.NewCreatePolicyOptions(
"authorization",
[]iampolicymanagementv1.PolicySubject{policySubjects},
[]iampolicymanagementv1.PolicyRole{policyRoles},
[]iampolicymanagementv1.PolicyResource{policyResources},
)

policy, response, err := iamPolicyManagementService.CreatePolicy(options)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(policy, "", " ")
fmt.Println(string(b))

const policySubjects = [
{
attributes:
{
name: 'accountId',
value: exampleAccounId,
},
{
name: 'serviceName',
value: exampleSourceServiceName,
},
{
name: 'serviceInstance',
value: exampleSourceServiceInstaceId,
},
],
},
];
const policyRoles = [
{
role_id: 'crn:v1:bluemix:public:iam::::serviceRole:Reader',
},
];
const accountIdResourceAttribute = {
name: 'accountId',
value: exampleAccountId,
operator: 'stringEquals',
};
const serviceNameResourceAttribute = {
name: 'serviceName',
* [Capturing multiple values](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-multiple-entity-values)
* [Reformatting values](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-reformat-values)
* [Dealing with zeros](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-zero)
* [Getting confirmation](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-get-confirmation)
* [Replacing a slot context variable value](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-found-handler-event-properties)
* [Avoiding number confusion](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-avoid-slot-confusion)
* [Adding conditions to Found and Not found responses](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-handler-next-steps)
* [Moving on after multiple failed attempts](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-stop-trying-after-3)
* [Preventing a Found response from displaying when it is not needed](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-stifle-found-responses)
* [Handling requests to exit a process](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-node-level-handler)





 Asking for everything at once
<br> * StringTimeSeries<br> * StringArrayTimeSeries<br> * StringSegmentTimeSeries<br> * StringArraySegmentTimeSeries<br><br><-- </ul> --><br> || SegmentTimeSeries | Represent any of the following data types: - DoubleSegmentTimeSeries<br><br><-- <ul> --><br><br> * DoubleArraySegmentTimeSeries<br> * StringSegmentTimeSeries<br> * StringArraySegmentTimeSeries<br><br><-- </ul> --><br> || ArrayTimeSeries | Represent any of the following data types: - DoubleArrayTimeSeries<br><br><-- <ul> --><br><br> * DoubleArraySegmentTimeSeries<br> * StringArrayTimeSeries<br> * StringArraySegmentTimeSeries<br><br><-- </ul> --><br> |<-- </table ""> --><-- <table> -->Table 3.
* Select either the Public or Private network for the subnet. Global IP addresses are only available on the public network.
* Select between IPv4 or IPv6. IPv6 is only available on the public network.
* Select the Size, which refers to a CIDR notation prefix.
* Select a Routing type.



6. In the Endpoint section (only valid for portable and static routing types):



* Select the destination for the subnet routing. Selections made in the previous sections determine what IP addresses or VLANs are available for your secondary subnet. Use the table's search bar to search within these results.



* For static subnets, the endpoint table is populated with subnets. Expand the subnet row to see a list of IP addresses that are available to route your new subnet to.
* For portable subnets, a table of selectable VLANs appears.





7. Review the summary, read and agree to the Master Service Agreement, and click Create.







 Next steps 

A new subnet with your configuration appears on your account within a few minutes. For information on how to manage global IP addresses, see [Working with global IP addresses](https://cloud.ibm.com/docs/subnets?topic=subnets-work-with-global-ip-addresses). For information on how to route and unroute secondary subnets, see [Re-routing secondary subnets](https://cloud.ibm.com/docs/subnets?topic=subnets-re-routing-secondary-subnets).
* Select a traffic type and optional traffic source:



* Egress (default) - Optionally, select to accept traffic from an IBM Cloud VPN server or VPN gateway.

Selecting VPN server allows VPN server resources to create routes in this routing table.
* Ingress - Ingress options are available for use on one routing table per VPC. You must choose at least one of the following traffic sources to enable ingress routing.



* Direct link - Allows ingress traffic from an [IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl) Dedicated or Connect connection to an on-prem location.
* Transit gateway - Allows ingress traffic from an [IBM Cloud Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started) to another VPC or classic infrastructure.
* VPC zone - Allows ingress traffic to another availability zone of the same VPC.
* Public internet - Allows public internet ingress traffic destined to a floating IP to be routed to a VPC next-hop IP.

The next-hop must be within the same zone of the specified VPC.







4. Click Create routing table.







 Creating a routing table from the CLI 

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).

To create a routing table by using the CLI, run the following command:

ibmcloud is vpc-routing-table-create VPC [--name NAME] [--direct-link-ingress false | true] [--internet-ingress, --internet false | true] [--transit-gateway-ingress false | true] [--vpc-zone-ingress false | true] [--accept-routes-from-resource-type-filters, --ar-rtf vpn_server | vpn_gateway] [--output JSON] [-q, --quiet]

Where:

VPC
token_url optional, updatable String token_url The token URL that is used to authorize with the Git Repos and Issue Tracking server. 
 type required, immutable String type The operation to perform to initialize the new tool integration. Use new to create a Git repo, clone to clone an existing Git repo into a new Git repo, fork to fork an existing Git repo, or link to link to an existing Git repo. 







 Learn more about Git Repos and Issue Tracking 

To learn more about Git Repos and Issue Tracking, see the [Git Repos and Issue Tracking: Social coding hosted by IBM article](https://www.ibm.com/garage/method/practices/code/tool_git_repos_and_issue_tracking/) on the IBM Cloud Garage Method.
"SIRE_ENTITY_LEVEL" : "NONE",
"SIRE_ENTITY_SUBTYPE" : "NONE",
"SIRE_MENTION_ROLE" : "FURNITURE_PATIO",
"SIRE_MENTION_TYPE" : "NONE"
},
"type" : "FURNITURE_PATIO",
"begin" : 3221,
"end" : 3234,
"inCoref" : false
},
Show more

Don't forget to rename the parent mention labels.

For example, find mentions that specify "SIRE_ENTITY_SUBTYPE" : "OTHER", and then change the value from OTHER to NONE.

Change the value of the SIRE_MENTION_ROLE and type for the mention to the new parent entity type label.

For example, change the SIRE_MENTION_ROLE and type values for these mentions from FURNITURE to FURNITURE_NONE, and the SIRE_ENTITY_SUBTYPE to NONE.

{
"id" : "Sports_herald.com_be99aca94a7cff5abb74476b844a11b6.en-M75",
"source" : "IMPORT",
"properties" : {
"SIRE_MENTION_CLASS" : "SPC",
"SIRE_ENTITY_LEVEL" : "NONE",
"SIRE_ENTITY_SUBTYPE" : "NONE",
"SIRE_ENTITY_CLASS" : "SPC",
"SIRE_MENTION_TYPE" : "NONE",
"SIRE_MENTION_ROLE" : "FURNITURE_NONE"
},
"type" : "FURNITURE_NONE",
"begin" : 2063,
"end" : 2071,
"inCoref" : false
},
Show more
7. Add annotations for relationships that are missing based on the new flattened entity types.
8. Create a Knowledge Studio workspace, and then upload the converted type system.

Follow the appropriate steps for uploading a type system based on your Knowledge Studio deployment type:



IBM Cloud
* You can manage targets from the public network using an API endpoint with the following format: https://REGION.atracker.cloud.ibm.com
* You can disable the public endpoints by updating the account settings. For more information, see [Enforcing private endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-mng-endpoints).









 Target types 

You can configure any of the following target types:



Table 1. List of targets

 Target Type Learn more 

 IBM Cloud Object Storage (COS) cloud_object_storage [Managing IBM Cloud Object Storage (COS) targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_cos) 
 IBM Cloud Activity Tracker Event Routing AT hosted event search logdna [Managing IBM Cloud Activity Tracker Event Routing hosted event search targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_at). 
 IBM® Event Streams for IBM Cloud® (Event Streams) event_streams [Managing IBM® Event Streams for IBM Cloud® (Event Streams) targets](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_ies) 







 IAM Access 

You must grant users IAM permissions to manage targets. For more information, see [Assign access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).

When you define a policy, you can indicate the scope of the permissions. You can choose from granting permissions for a specific region or for the entire account.

Users with regional scope will be limited to access targets in their authorized region.



Table 2. Required IAM roles

 IAM action IAM Policy scope IAM Roles Description 

 atracker.target.read Region Administrator <br>Editor <br>Viewer <br>Operator Read (view) information about a target 
 atracker.target.create Region Administrator <br>Editor Create a target
Selecting the service and configuring basic options 

To begin creating your new IBM Cloud® Load Balancer, select IBM Cloud® Load Balancer from the Load Balancer page of the [IBM Cloud catalog](https://cloud.ibm.com/catalog/infrastructure/load-balancer-group), then click Create.

When the configuration page appears, follow these steps:



1. Enter the name for the load balancer instance. The fully qualified domain name (FQDN) of the load balancer is based on this name.
2. Enter a description for the load balancer (optional).
3. Select the data center where the load balancer instance is to be created.

For multi-zone availability, all requirements for [MZR](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-multi-zone-region-mzr-overview) must be satisfied.
4. Select the type of load balancer you want to create from the options Public-to-Private , Private-to-Private, or Public-to-Public. Refer to [IBM Cloud® Load Balancer basics](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-ibm-cloud-load-balancer-basics) for details on each type.
5. Select the subnet where you want to deploy your new load balancer.

This option applies to only Public-to-Private and Private-to-Private load balancer types. Your load balancer service instance has one of its network interfaces on this subnet. Ensure that your application servers are either on this subnet or reachable from this subnet. If necessary, enable VLAN spanning.
6. Select the allocation of public IPs for the load balancer.

This option applies to only the Public-to-Private load balancer type. If you select the option Allocate from a public subnet in this account, you must ensure that you have at least two public IPs available in a public subnet in the same data center.
Load balancer Delete Editor for the load balancer<br><br>Operator for security groups 
 Load balancer View, List Viewer for the load balancer 
 Load balancer pools and listeners Create, Update, Delete Editor for the load balancer 
 Load balancer pools and listeners View, List Viewer for the load balancer 
 ———————— ————————— ———————— 
 Placement group View Viewer for placement groups 
 Placement group Create, Delete, Update Editor for placement groups 
 ———————— ————————— ———————— 
 Public gateway Create Editor for Public Gateway resources<br><br>Operator for the VPC and Floating IP resources 
 Public gateway Update, Delete Editor for the public gateway 
 Public gateway View, List Viewer for the public gateway 
 —————— ——————— ———————— 
 Shares View, List Viewer for file shares and mount targets 
 Shares Create Editor for creating file shares 
 Shares Create Operator role for creating mount targets 
 Shares Update, Delete Editor for updating and deleting file shares 
 Shares Update Editor role for updating mount targets 
 Shares Delete Operator role for deleting mount targets 
 Share profiles View, List Any account user 
 —————— ——————— ———————— 
 Security group View, List Viewer for the security group 
 Security group Create Viewer for the VPC and the resource group of the security group<br><br>Editor for security group for VPC resources 
 Security group Update, Delete Editor for the security group 
 Security group rule View, List Viewer for the security group 
 Security group rule Create, Update, Delete Editor for the security group 
 Security group target View, List Viewer for the security group 
 Security group target Attach, Detach Operator for the security group<br><br>Editor for instance if the target is a network interface<br><br>Editor for load balancer if the target is a load balancer 
 ———————— ————————— ————————