vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"intent": "exit_app",
"confidence": 1.0
}
]
}
}
]
}
]
}
}
Show more







 pause 

Pauses before sending the next message to the channel, and optionally sends a "user is typing" event (for channels that support it).



 Fields 



 Name Type Description Required? 

 response_type string pause Y 
 time int How long to pause, in milliseconds. Y 
 typing boolean Whether to send the "user is typing" event during the pause. Ignored if the channel does not support this event. N 







 Example 

This examples sends the "user is typing" event while pausing for 5 seconds.

{
"output": {
"generic":[
{
"response_type": "pause",
"time": 5000,
"typing": true
}
]
}
}







 text 

Displays text. To add variety, you can specify multiple alternative text responses. If you specify multiple responses, you can choose to rotate sequentially through the list, choose a response randomly, or output all specified responses.



 Fields 



 Name Type Description Required? 

 response_type string text Y 
 values list A list of one or more objects defining text response. Y 
 values.[n].text string The text of a response. This can include newline characters () and Markdown tagging, if supported by the channel. (Any formatting not supported by the channel is ignored.) N 
 selection_policy string How a response is selected from the list, if more than one response is specified. The possible values are sequential, random, and multiline. N 
 delimiter string The delimiter to output as a separator between responses. Used only when selection_policy=multiline. The default delimiter is newline (). N 







 Example 

This examples displays a greeting message to the user.

{
"output": {
"generic":[
{
v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1createexample)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodecreateexample)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javacreateexample)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythoncreateexample) 
 Get user input example Get information about a user input example. v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1getexample)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodegetexample)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javagetexample)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythongetexample) 
 Update user input example Update the text of a user input example. v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1updateexample)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodeupdateexample)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javaupdateexample)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythonupdateexample) 
 Delete user input example Delete a user input example from an intent.
* [Calculations](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-calculations)

Add calculations to a view to enhance your analysis. Calculations are saved as part of the view in the Planning Analytics with Watson content store.
* [Find data](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-find-data)

Find data in Planning Analytics with Watson by using the intent bar or the data tree.
* [Sets](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-sets)

Create and edit sets of members in a dimension to limit the number of members that you see in a view. You can also create sets from hierarchies.
* [Create selectors](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-create-selectors)

You can create selectors for dimensions, members, sets, or levels. For example, suppose that you have a visualization and the overview is hidden. You can add a selector to the sheet so that you change the point of view.
* [Buttons](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-buttons)

You can create a button in Planning Analytics with Watson that lets you execute a TurboIntegrator process and/or open a new destination with a single click.
* [Websheets](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=views-websheets)

You can work with websheets in Planning Analytics with Watson. You can create and work with sandboxes in websheets, and you can combine websheets and views on the same sheet.
* [Explore scenarios with sandboxes](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-explore-scenarios-sandboxes)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 sysdig-monitor.integrations.read Access integrations. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 sysdig-monitor.manual-integrations.edit Edit manual integrations. !
"optional-param":"parameter required by your service"
}
}
Show more





 Creating a service instance by using the CLI 

When a user wants to create a service instance, they can use ibmcloud cli [ ibmcloud resource service-instance-create NAME SERVICE_NAME SERVICE_PLAN_NAME LOCATION ].

The IBM Cloud platform validates that the user has permission to create the service instance by using IBM Cloud IAM. After this validation occurs, your service broker's endpoint (PUT /v2/resource_instances/:resource_instance_id) is started. For the instance to be created, the following rules must be met:



* The IBM Cloud context is included in the context variable
* The X-Broker-API-Originating-Identity has the IBM IAM ID of the user that started the request
* The parameters section includes the requested location (and more parameters that are required by your service).



Example request for creating an instance:

PUT /v2/service_instances/crn%3Av1%3Abluemix%3Apublic%3Acompose-redis%3Aus-south%3Aa%2F46aa677e-e83f-4d17-a2b6-5b752564477c%3A416d769b-682d-4833-8bd7-5ef8778e5b52?accepts_incomplete=true HTTP/1.1
Host: https://broker.compose.cloud.ibm.com
Authorization: basic dXNlcjpwYXNzd29yZA==
X-Broker-Api-Version: 2.12
X-Broker-API-Originating-Identity: ibmcloud aWJtaWQtNDU2MzQ1WA==
{
"service_id": "0bc9d744-6f8c-4821-9648-2278bf6925bb", // your service's GUID from onboarding
0zq/6M8ERuXbRHvXiH663hUKS/gVfwgeRER7zitvhjY2g6KWwZ2hM9ATpb0PV8m4KNsmn7LKQsYTOFPZE02Ymw2CfnuXlY962/feq7oj9t4BZ+OwH5+YrQrem85/D75KXVYEX9eVaICv5fdmGw59WNqTsQYGc4dWs/qOstEcgiuC64KsHXONtMCKZEOJD7uINw29QhEf+QLWxrdahBb7Xk/rxFH3Fc6datY9MF9bTu9ltck27qSsKMXriUfEJ2LQ2ubtiRagop3AqvgN3DW/CuX2RmuAFBAJBKlz4UCJzyDevDIb3JEpeMNyHwoTtELbru3LqywHRtKyqPOwvIDIJxxKLwuol3YsoUcLdogYeDcu1yvb60vjGRi3VZZH1fPBHKcelJc6bL4mMm0VHFAMWYy4J/I6JAMzcItktET4+1WgCOknWYzueFUruJlC4pdmR3JhhaBVXL/TfwVOBnuolRvOEVNcbhAwE72SmusO2NiAesqa6gThq6jFBN7mKpObuDg0T8G9t3kjou0FGKTnt8uXS6X6okXNmYHAs/GimKR8tPAWx/mpJNoSjTSxAJaZnlWTinT+NEXmTw1GFsR+Ju32mNgTDf9O4uV3iaB6OW6Xn5ldX0bUqb2+2rv7g51SkjQfAZwqkwBxXBFzzbURKj6UVGxloFyAckE1RyNjfr3ckL44uoevxjDQNLBEbgGt7MC837NF6EeaIUjDnEao7nd9SjpGcaFt9DOyXDpmcNGSuGco8efQaAnWsJf0gP48V0H252qAXx1/IIhjg39tGYveuVJ7E4u+fkDrjxdEOhCj07Eoo31mZ2oBDjiFqQeNPlyXOf5dax4E2mCzHZMUuHVk3U
Show more
2. Create the env section of the contract. For more information about the env section of the contract, see [The env section](https://cloud.ibm.com/docs/vpc?topic=vpc-about-contract_sehpcr_contract_env).
Deploy Initial VM workload 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/deploy-workload/journey-map.png)



 Overview 

After provisioning your environment you may wish to test and validate your settings prior to bringing over your production virtual machines. Using content libraries and IBM Clouds internal mirrors this can be easily accomplished.

The steps involved in the exercise are:



1. Creation of a content library
2. Import of operating system .isos from IBM Cloud internal mirrors
3. Use of the content library in deploying a virtual machine.







 Create Content Library 



1. Log into vCenter using the IP address and credentials provided in the IBM Cloud for VMware Solutions portal.
2. From the default start page using the menu select Content Libraries.

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/deploy-workload/content-lib-menu-item.png)
3. Select Create to create a new content library.

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/deploy-workload/create-content-lib.png)
4. For configure content library leave the default (local content library) select and click Next.

!
ibmcloud hpvs instance-create MyHPVS lite-s dal13 -g Default --ssh "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCgguQtzV39LpP/iHAtjwo+4Z5QdASG73dwBlFIsTn5kPOaVYFHhzhvA/xMbLqDpxfYP/YzwU4rXNXMhCr4hlsruPXt5Ak4y83GmnNL8e+oq8lxU/afymje4PcYLnkm8WQvkreIEBaB73VOUKiLSSbdVljUk6a1LB347bCf72Oob8JpY4Pb3N4idrigSoCc+V4JVkz4pXD2Hoyar4J5I2527Ho+vUqdf5FoK9mFRUqtI8NTLKynL2/qVsCgTeUxnOknDjPE0+nqwyNI4toYozcISYb63K9Je6UBT4JaIQXMbdMhDH00wVH7R26SamKqS2iazcUBnZgN4//Vnic+US90ybsqvTuP/OQpHXwfdjshOEsz5PULZKbWgidsfA7aW3pjv1uijCPIrTFOsaAPktMCzhfJzaeFC0VIXweN7/2PT/Zl7U9Ys36CmmLaXfLotXxPWmbGUyRfavPN1Znhqph7v9w94E7JcngQ7sn+l+nkpYg5qdcBFZZ3kNhT4PVRbXE=" --hostname "test.ibm.com"

You can find more information about the create command [here](https://cloud.ibm.com/docs/hpvs-cli-plugin?topic=hpvs-cli-plugin-hpvs_cli_plugincreate_instance).

The newly created instance is marked as provisioning until provisioning completes.
7. Your simple contract is ready 

env: 
type: env
logging:
logDNA:
hostname: syslog-a.au-syd.logging.cloud.ibm.com
ingestionKey: xxxxxxxxxx
port: 6514
workload: 
type: workload
compose:
archive: H4sIADXNg2IAA+3W326CMBQGcK59it555XbanraMq70KlOLIJhjqzPb2q6g3S9xiIi7T75eQlj+hDYcP6vvVuo/hMZsQJc6YsU2+t2NfsmKyyhHLjKRUSmbCTDmpo/e4KQchsqHvNz9d99v5f8of6l/3/jUMi8Puw+fq7XJj7ApsmU/WX2m7r7/j9Abs6s/W2kzQ5aZw2p3XfxuG2PZdIeZ6Poth2LY+xGImRLdsu49dR4h2VS5DsT/yHF9KZWxRSU02NCGkxJJ0FQVSoSlrn8Jba5eyrEsOT55dlduq9sY55sbrhlJpda7HG6/7YRP3YyxETkVOhz6zLtI2++unc/tO5b+84AfgrPyn4JM0pDXyfw3I/32bMvdH5+SfOK0TpdZWIv/XgPzftynX/Udn/f/NmH+l8P+/CuQfAAAAAAAAAAAAAOD2fAEPQbuiACgAAA==
Show more







 Next steps 



* [Creating an instance by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers)
curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: $iam_token" -d '{
"encryption_key": {
"crn":"crn:[...key:...]"
},
"iops": 1000,
"name": "my-encrypted-share",
"profile": {
"name": "tier-5iops"
},
"resource_group": {
"id": "678523bcbe2b4eada913d32640909956"
},
"size": 100,
"mount_targets": [
{
"name": "my-share-target",
"subnet": {
"id": "7ec86020-1c6e-4889-b3f0-a15f2e50f87e"
}
}
],
"zone": {
"name": "us-south-2"
}
}'

A successful response looks like the following example.

{
"created_at": "2023-07-11T22:58:49.000Z",
"crn": "crn:[...]",
"encryption": "customer_managed",
"encryption_key": {
"crn": "crn:[...key:...]"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/a0c07083-f411-446c-9316-7b08d6448c86",
"id": "a0c07083-f411-446c-9316-7b08d6448c86",
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Creating screens ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) !
"target_crn": "crn:v1:bluemix:public:resource-catalog::a/e97a8c01ac694e308ef3ad7795c7cdb3::deployment:e62e2c19-0c3b-41e3-b8b3-c71762ecd489:us-south38399"
},
"parameters": {
"location": "us-south",
"optional-param":"parameter required by your service"
}
}





 Creating a service instance by using the API 

This action can be done only through the UI or CLI. To see the steps, switch to the UI or CLI instructions.

The IBM Cloud platform validates that the user has permission to create the service instance by using IBM Cloud IAM. After this validation occurs, your service broker's endpoint (PUT /v2/resource_instances/:resource_instance_id) is started. For the instance to be created, the following rules must be met:



* The IBM Cloud context is included in the context variable
* The X-Broker-API-Originating-Identity has the IBM IAM ID of the user that started the request
* The parameters section includes the requested location (and more parameters that are required by your service).



Example request for creating an instance:

PUT /v2/service_instances/crn%3Av1%3Abluemix%3Apublic%3Acompose-redis%3Aus-south%3Aa%2F46aa677e-e83f-4d17-a2b6-5b752564477c%3A416d769b-682d-4833-8bd7-5ef8778e5b52?accepts_incomplete=true HTTP/1.1
Host: https://broker.compose.cloud.ibm.com
Authorization: basic dXNlcjpwYXNzd29yZA==
X-Broker-Api-Version: 2.12
--------------------------------------------------------------------------------
? Enter selection number:> 5

Generating a new application reminds us that the toolchain used to deploy your app needs some additional configuration. As mentioned earlier, uploading your public key to GitHub (at the CD Toolchain instance on the IBM Cloud Platform), is required to deliver the deployed application by using GitHub.

Note: For successful connection to the DevOps toolchain, this machine
must be configured for SSH access to your IBM Cloud GitLab account at
https://git.cloud.ibm.com/profile/keys in order to download the
application code.

Further prompts confirm the application and toolchain name that you defined earlier. The example shows how you can alter the host and toolchain names, if you want. The hostname must be unique for the service endpoint of your application, but barring a conflict, you can simply press return when asked for confirmation.

The DevOps toolchain for this app will be: webapplication
? Press [Enter] to accept this, or enter a new value now>

The hostname for this app will be: webapplication
? Press [Enter] to accept this, or enter a new value now>

The app webapplication has been created in IBM Cloud.

DevOps toolchain created at
https://cloud.ibm.com/devops/toolchains/6ffb568a-e48f-4e27-aed0-00ca931dde66?env_id=ibm:yp:us-south

If you copy and paste the link that is returned by the ibmcloud dev create command, you can also access your CD Toolchain. You can access that from the console later, in case you missed capturing the link.
createOriginPath 

Creates an origin path for an existing CDN and for a particular customer. The origin path can be based on a Host Server or Object Storage. To create the origin path, the domain mapping must be in either a RUNNING or CNAME_CONFIGURATION state.



* Parameters- A collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Input.

You can view all of the attributes in the Input container here:

[Input container](https://cloud.ibm.com/docs/CDN?topic=CDN-input-container)

The following attributes are part of the Input container and can be provided when creating an origin path (attributes are optional unless otherwise noted):



* vendorName- (Required) Provide the name of a valid IBM Cloud CDN provider.
* origin- (Required) Provide the origin server address as a string.
* originType- (Required) Origin type can be HOST_SERVER or OBJECT_STORAGE.
* domain- (Required) Provide your hostname as a string.
* protocol- (Required) Supported protocols are HTTP, HTTPS, or HTTP_AND_HTTPS.
* path- Path from which the cached content is served. Must begin with the mapping path. For example, if the mapping path is /test, then your origin path might be /test/media.
* httpPort, httpsPort, or both- (Required) These two options must correspond to the wanted protocol. If the protocol is HTTP, then httpPort must be set, and httpsPort must not be set. Likewise, if the protocol is HTTPS, then httpsPort must be set, and httpPort must not be set. If the protocol is HTTP_AND_HTTPS, then bothhttpPort and httpsPortmust be set. Akamai has certain limitations on port numbers. See the [FAQ](https://cloud.ibm.com/docs/CDN?topic=CDN-faqsare-there-any-restrictions-on-what-port-numbers-are-allowed) for allowed port numbers.
* header- Specifies host header information that is used by the origin server.
* uniqueId- (Required) Generated after the mapping is created.
Packaging files to upload from source path '.'...
Submitting build run 'myapp-run-220999-210706331'...
Creating image 'private.us.icr.io/ce--6ef04-khxrbwa0lci/app-myapp:220418-0207-askql'...
Waiting for build run to complete...
Build run status: 'Running'
Build run completed successfully.
Run 'ibmcloud ce buildrun get -n myapp-run-220000-210706331' to check the build run status.
Waiting for application 'myapp' to become ready.
Configuration 'myapp' is waiting for a Revision to become ready.
Ingress has not yet been reconciled.
Waiting for load balancer to be ready.
Run 'ibmcloud ce application get -n myapp' to check the application status.
OK

https://myapp.abcdbwa0lci.us-south.codeengine.appdomain.cloud

And that's it. You now have an internet-facing application. The code in the application itself is the same as what is used for a Heroku application, it's just the Code Engine commands that are slightly different.

Let's take a deeper look at the previous app create command. Notice that the output of the app create command provides information about the progression of the build run before the app is created and deployed.



1. Code Engine receives a request to create an application from source code (instead of pulling directly from an image).
2. Code Engine checks for an IAM service ID and API key that is associated with the selected project. This service ID must be authorized to read and write to IBM Cloud Container Registry. If no service ID exists, Code Engine creates one for you. Note that this service ID is used for subsequent Code Engine build requests that are run from the same project.
3. This example builds code from a public GitHub repository (--build-source https://github.com/IBM/heroku-to-code-engine).
[Review configuration](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/decix-review-configuration.png)

Review configuration
12. After your direct link settings are accepted successfully, select a resource group, routing option, and billing type. Optionally, you can enable MD5 authentication to provide additional security for the BGP session, or update your network connection type.
13. Review your order summary, agree to the Direct Link Connect prerequisites, and then click Create to complete this order.

Zoom

![Finalize creation](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/decix-finalize-creation.png)

Finalize creation

Your direct link is created:

Zoom

![Direct Link created](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/decix-direct-link.png)

Direct Link created

If you switch back to the DE-CIX portal, you should see the following page after some time. The status on this page shows you that your direct link was created successfully.

Zoom

![Cloud order completed](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/dl//images/decix-order-completed.png)

Cloud order completed
ibmcloud hpvs instance-create MyHPVS lite-s dal13 -g Default --ssh "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCgguQtzV39LpP/iHAtjwo+4Z5QdASG73dwBlFIsTn5kPOaVYFHhzhvA/xMbLqDpxfYP/YzwU4rXNXMhCr4hlsruPXt5Ak4y83GmnNL8e+oq8lxU/afymje4PcYLnkm8WQvkreIEBaB73VOUKiLSSbdVljUk6a1LB347bCf72Oob8JpY4Pb3N4idrigSoCc+V4JVkz4pXD2Hoyar4J5I2527Ho+vUqdf5FoK9mFRUqtI8NTLKynL2/qVsCgTeUxnOknDjPE0+nqwyNI4toYozcISYb63K9Je6UBT4JaIQXMbdMhDH00wVH7R26SamKqS2iazcUBnZgN4//Vnic+US90ybsqvTuP/OQpHXwfdjshOEsz5PULZKbWgidsfA7aW3pjv1uijCPIrTFOsaAPktMCzhfJzaeFC0VIXweN7/2PT/Zl7U9Ys36CmmLaXfLotXxPWmbGUyRfavPN1Znhqph7v9w94E7JcngQ7sn+l+nkpYg5qdcBFZZ3kNhT4PVRbXE="





 Example output 

OK
Provisioning request for service instance 'crn:v1:staging:public:hpvs:dal13:a/1075962b93044362a562c8deebbfba2e:98338d1f-910b-4895-9410-453a9c4d9709::' was accepted.
To check the provisioning status run:
"name": "nlb-vnf",
"is_public": false,
"profile": {
"name": "network-fixed"
},
"route_mode": true,
"subnets": [
{
"id": "0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024"
}
]
}

Save this payload to a JSON file. In the following examples, the file is named create.json.
3. Make the request to create your NLB with the following command. The following properties must be set in the payload:



* route_mode is true
* is_public is false
* Profile name is network_fixed



curl -s -H "Authorization: Bearer $IAM_TOKEN" -X POST -d @create.json "https://us-east.iaas.cloud.ibm.com/v1/load_balancers?version=2021-07-30&generation=2" | jq

Sample output:

{
  "id": "r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"name": "nlb-vnf",
"href": "https://us-east.iaas.cloud.ibm.com/v1/load_balancers/r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"crn": "crn:v1:bluemix:public:is:us-east-2:a/be636a7a6e4d4b6296bedf669ce8f757::load-balancer:r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"is_public": false,
[hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg) and select DevOps.
3. On the DevOps dashboard, on the Toolchains page, click Create a Toolchain.
4. On the Create a Toolchain page, click a toolchain template.
5. Review the diagram of the toolchain that you are about to create. The diagram shows each tool integration in its lifecycle phase in the toolchain.
6. Review the default information for the toolchain settings:



* The toolchain's name identifies it in IBM Cloud. If you want to use a different name, change the toolchain's name.
* The region to create the toolchain in. If you want to use a different region, select it from the list of available regions.
* The resource group to create the toolchain in. If you want to use a different resource group, select it from the list of available resource groups.
* The provider for your source repository, such as GitHub or GitLab. If you want to use a different source provider, select it from the list of available repos.



7. In the Tool Integrations section, select each tool integration that you want to configure for your toolchain. For more information about configuring the tool integrations, see [Configuring tool integrations](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations).
8. Click Create. Several steps run automatically to set up your toolchain. The tool integrations that are set up are different depending on which toolchain template you selected. For example, when you create a Microservices toolchain on IBM Cloud Public, these steps are run:



* The toolchain is created.
* If you configured Delivery Pipeline, the pipelines are created and triggered.