vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics_router?topic=metrics_router-endpointsendpoints_api).







 Getting settings using the API 

You can use the following cURL command to get existing settings information:

curl -X GET ENDPOINT/api/v3/settings -H "Authorization: $ACCESS_TOKEN"

Where:

ENDPOINT
: Is the API endpoint in the region where you plan to configure or manage a target. For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics_router?topic=metrics_router-endpointsendpoints_api).

For example, you can use the following cURL request to get the account settings information:

curl -X GET https://private.us-south.metrics_router.cloud.ibm.com/api/v2/settings -H "Authorization: $ACCESS_TOKEN"

A response similar to the following is returned:

{
"default_targets": [
{
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"crn": "crn:v1:bluemix:public:metrics-router:us-south:a/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::target:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"name": "default-us-south-target",
"target_type": "sysdig_monitor"
},
{
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"crn": "crn:v1:bluemix:public:metrics-router:au-syd:a/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa::target:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
If you are using the expression editor, click Apply to save your changes and close the editor window.



You can also use an expression to assign an initial value to a session variable. In the Session variable window, go to the Initial value field and click Use expression.

You can also write an expression directly without first picking a variable:



1. From within a step, click Set variable values.
2. Click Set new value.
3. From the drop-down list, select Expression.
4. Type the expression you want to use.
5. If you are using the expression editor, click Apply to save your changes and close the editor window.







 Expression syntax 

The Watson Assistant expression language is based on the Spring Expression Language (SpEL), but with some important differences in syntax. For detailed background information about SpEL, see [Spring Expression Language (SpEL)](https://docs.spring.io/spring-framework/docs/5.2.13.RELEASE/spring-framework-reference/core.htmlexpressions).



 Variables 

To reference a variable in an expression, type type a dollar sign ($) and then select a variable from the list. The reference is inserted into your expression in the correct notation, referencing the variable using its variable ID rather than its display name (for example, ${step_773} or ${customer_id}). Do not edit this reference unless you want to refer to a different variable and you are sure of its variable ID.





 Standard math 

For numeric values, you can use expressions to perform mathematical calculations. For basic arithmetic, you can use standard operators (+, -, , /).

You can also use methods to perform additional mathematical operations. For more information, see [Expression language methods for actions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-expression-methods-actionsexpression-methods-actions-numbers).





 Arrays 

To define an array value, type the value using square brackets, with commas separating the items (for example, [ "one", "two", "three" ]).
Select the Format of the string flag type from the list. Supported format is Text, JSON, and YAML. When JSON or YAML format is selected, provide the Enabled value and Disabled value in the selected format.
2. Specify the Enabled value. This value is returned by default when toggle switch is set to ON for the feature flag. This value can be overridden when targeting to a segment.
3. Specify the Disabled value. This value is returned by default when toggle switch is set to OFF for the feature flag.







 Numeric 

When you select the Flag type as Numeric, the Default value details are displayed:

Zoom

![Feature flag type - Numeric](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-feature-flag-numeric.png)

Figure 5. Feature flag type - Numeric



1. Select the Enabled value from the list. Only integer values are supported. This value is returned by default when toggle switch is set to ON for the feature flag. This value can be overridden when targeting to a segment.
2. Select the Disabled value from the list. Only integer values are supported. This value is returned by default when toggle switch is set to OFF for the feature flag.









 Target collections to feature flags 

Optionally, select a collection for applying a feature flag now. Otherwise, you need to add a collection before you toggle a feature flag.

You can add feature flags to one or more collections either during creation of feature flag or during editing feature flag details.

For adding collections to the feature flag, for the Flag availability across collections field, select the collection from the list.

If you try to target a feature flag that is not linked to a collection, a window is displayed to add a feature flag to a collection.





 Configure feature rollout percentage
You create this image stream in the default project, which is also the project where the image stream is created if you don't specify a project. The values for <image>:<tag> typically match the values that you previously retrieved.
* --reference-policy=local: Set this value to local so that a copy of the image from IBM Cloud Container Registry is imported into the local cache of the internal registry and made available to the cluster's projects as an image stream. If you don't include this value, the image stream refers back to IBM Cloud Container Registry when you use it in your deployments and therefore requires credentials in the project.
* --scheduled: Set this optional option to set up periodic importing of the image from IBM Cloud Container Registry into the internal registry. The default frequency is 15 minutes. For more information, see the [Red Hat OpenShift documentation](https://docs.openshift.com/container-platform/4.11/openshift_images/image-streams-manage.htmlimages-imagestreams-import_image-streams-managing).



5. Verify that your image stream is created.

oc get imagestreams
6. Verify that the image stream successfully pulled the image from IBM Cloud Container Registry. In the output, check that the latest tagged from image matches your <region>.icr.io/<namespace>/<image>@<digest> image.

oc describe is/<imagestream>

Example output

NAME: <imagestream>
Namespace: default
Created: 2 days ago
Labels: <none>
Annotations: openshift.io/image.dockerRepositoryCheck=2020-03-31T09:41:36Z
Image Repository: image-registry.openshift-image-registry.svc:5000/default/ant1
Image Lookup: local=false
Unique Images: 1
Tags: 1

latest
tagged from <region>.icr.io/<namespace>/<image>:<tag>

* <region>.icr.io/<namespace>/<image>@<digest>
2 days ago
If you set your application for visibility = private, then you can only test your application through the [virtual private endpoint from within your Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/codeengine?topic=codeengine-vpe).

By changing the visibility of your app, the change is effective immediately. It is important to consider the impact of the change for your active users or integrations as well as any security implications. You can change the visibility setting as needed.





 Updating your app with the CLI 

To update your app with the CLI, use the app update command. This command requires the name of the app that you want to update and also allows other optional arguments. For a complete listing of options, see the [ibmcloud ce app update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-update) command.

Update the application that you created in [Deploying an application with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-cli) to add an environment variable.

The sample icr.io/codeengine/hello image reads the environment variable TARGET, and prints Hello ${TARGET}. If this environment variable is empty, Hello World is returned. The following example updates the app to modify the value of the TARGET environment variable to Stranger. For more information about the code that is used for this example, see [hello](https://github.com/IBM/CodeEngine/tree/main/hello).



1. Run the application update command. For example,

ibmcloud ce application update -n myapp --env TARGET=Stranger

Example output

Updating application 'myapp' to latest revision.
[...]
Run 'ibmcloud ce application get -n myapp' to check the application status.
OK

https://myapp.4svg40kna19.us-south.codeengine.appdomain.cloud
2.
7. Navigate to When to run tab and select the Update checkbox.

Zoom

![ServiceNow - When to run tab](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-sn-17.png)

Figure 12. ServiceNow - When to run tab
8. Click Submit to save the details.







 How to add IBM IAM token or App Configuration service credentials' API key for the webhook script? 

Webhook script needs IBM IAM token for the webhook calls or App Configuration service credentials' API key, where you can store the API key to generate the token.

Follow these steps:



1. Login to your ServiceNow instance as an administrator.
2. Click the All tab and search for sys_properties.LIST and press Enter. Alternately, you can go to https://{{instanceid}}.service-now.com/sys_properties_list.do, where instanceid is your ServiceNow instance ID.

Zoom

![ServiceNow All tab](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-sn-04.png)

Figure 13. ServiceNow - All tab
3. The System properties details gets displayed.

Zoom

![System properties](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-sn-05.png)

Figure 14. ServiceNow - System properties
4. Click New to create a new system property.

Zoom

!
After you change the storage section in the ConfigMap to use a different solution such as the emptyDir, you must update the management state to Managed. Then, the operator creates the internal registry pod. Use the following command: oc patch configs.imageregistry.operator.openshift.io/cluster --type merge -p '{"spec":{"managementState":"Managed"}}'



 Setting up the internal container image registry with IBM Cloud Object Storage 

You can configure the internal image registry in your Satellite cluster with IBM Cloud Object Storage as the backing storage.



1. Determine if you have an IBM Cloud Object Storage instance that meets the requirements.



1. In the IBM Cloud console, navigate to the Resources menu and list your storage instances.
2. Identify your Object Storage instances and find the Location column. If an instance was created in IBM Cloud, its location is listed as Global.
3. If you do not have an instance that meets the requirements, follow the steps to create one.



1. From the IBM Cloud Object Storage, click Create Instance.
2. Under Choose an Infrastructure, select the IBM Cloud option.
3. Select a pricing plan and a service name.
4. Choose the resource group where your Satellite components are stored.
5. Click create. Note that it might take several minutes for your instance to provision.





2. Create a bucket to use when you set up your image registry. Your bucket must be configured with regional resiliency. For more information on creating bucket, see [Setting up IBM Cloud Object Storage](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-understand).



1. Click on your Object Storage instance.
2. Click Create a bucket.
3. Select the option to Customize your bucket.
4. Under Resiliency, select Regional.
5. From the Location drop down menu, choose the region that is closest to where your location is managed from.
https://<region>.kms.cloud.ibm.com/api/v2/instance/policies?policy=allowedNetwork



1. [Retrieve your authentication credentials to work with the API](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-up-api).

To change a network access policy, you must be assigned a Manager access policy for your Key Protect instance. To learn how IAM (identity and access management) roles map to Key Protect service actions, check out [Service access roles](https://cloud.ibm.com/docs/key-protect?topic=key-protect-manage-accessmanage-access-roles).
2. Enable a network access policy for your Key Protect instance by running the following curl command.

$ curl -X PUT "https://<region>.kms.cloud.ibm.com/api/v2/instance/policies?policy=allowedNetwork" -H "accept: application/vnd.ibm.kms.policy+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>" -H "content-type: application/vnd.ibm.kms.policy+json" -d '{
"metadata": {
"collectionType": "application/vnd.ibm.kms.policy+json",
"collectionTotal": 1
},
"resources": [
{
"policy_type": "allowedNetwork",
"policy_data": {
"enabled": <enabled>,
"attributes": {
"allowed_network": "<access_type>"
}
}
}
]
}'
Show more



Replace the variables in the example request according to the following table.



Table 1. Describes the variables that are needed to set a network access policy at the instance level.

 Variable Description 

 region Required. The region abbreviation, such as us-south or eu-gb, that represents the geographic area where your Key Protect instance resides.
If set to root-key, root keys will be retrieved.









 kp region-set 

Target a different Key Protect regional endpoint.

ibmcloud kp region-set REGION
-i, --instance-id INSTANCE_ID
[-u, --unset]



 Examples 

These are examples of kp region-set.



 Example 1 

If the REGION parameter is not specified, you are prompted to select a region.

 set the region endpoint
$ ibmcloud kp region-set

Select a Region:
1. au-syd
2. ca-tor
3. eu-de
4. eu-fr2 (available by request)
5. eu-gb
6. jp-osa
7. jp-tok
8. us-east
9. us-south
10. br-sao
11. staging (us-south)
Enter a number:
5
OK





 Example 2 

Set the region explicitly.

 set the region endpoint to "us-south"
$ ibmcloud kp region-set us-south

OK

The REGION must be a valid regional endpoint.

 this should fail (not a valid regional endpoint)
$ ibmcloud kp region-set not-a-region

FAILED





 Example 3 

Unset (remove) the regional endpoint.

 remove the regional endpoint
$ ibmcloud kp region-set -u

OK







 Required parameters 



* -i, --instance-id

The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.







 Optional parameters 



* REGION

Specify a regional endpoint. This parameter is optional and if not specified, you are prompted to select a regional endpoint from a list.
* -u, --unset

Unset (remove) the regional endpoiont.









 kp registrations
"session_affinity": "ip_cookie",
"session_affinity_attributes": {
"samesite": "None",
"secure": "Always",
"drain_duration": 100
}
}'
Show more





 Setting session affinity using the API 

When you create a global load balancer using the API, take the following steps to set the session affinity:



1. Set up your API environment with the correct variables.
2. Store the following values in variables to be used in the API command:



* session_affinity, which specifies the type of session affinity the load balancer uses, unless specified as "none" or "default". Valid values are none, cookie, ip_cookie.
* session_affinity_ttl, which is the time-to-live of the session affinity.
* session_affinity_attributes which include:



* samesite configures the SameSite attribute on the affinity cookie. Valid values are Auto, Lax, None, Strict; default Auto
* secure configures the Secure attribute on the session affinity cookie. Valid values are Auto, Always, Never ; default Auto
* drain_duration is the value of the drain duration, in seconds.





3. When all variables are initiated, create the global load balancer with session affinity:



curl -X POST https://api.cis.cloud.ibm.com/v1/:crn/zones/:zone_id/load_balancers -H 'content-type: application/json' -H 'x-auth-user-token: Bearer xxxxxx' -d '{
"description": "",
"proxied": true,
"enabled": true,
"name": "www.example.com",
"session_affinity": "none",
"session_affinity_ttl": 5000,
"steering_policy": "geo",
"fallback_pool": "4112ba6c2974ec43886f90736968e838",
"default_pools": [
Required if the user doesn't have permissions on the default key ring.
* -s, --starting-offset

Retrieves keys starting at the offset specified. The offset is zero-based, meaning offset 0 (zero) is the first key.
* -t, --key-type

The type of keys to be retrieved. If set to standard-key, standard keys will be retrieved. If set to root-key, root keys will be retrieved.









 kp region-set 

Target a different Key Protect regional endpoint.

ibmcloud kp region-set REGION
-i, --instance-id INSTANCE_ID
[-u, --unset]



 Examples 

These are examples of kp region-set.



 Example 1 

If the REGION parameter is not specified, you are prompted to select a region.

 set the region endpoint
$ ibmcloud kp region-set

Select a Region:
1. au-syd
2. ca-tor
3. eu-de
4. eu-gb
5. jp-osa
6. jp-tok
7. us-east
8. us-south
9. br-sao
10. staging (us-south)
Enter a number:
5
OK





 Example 2 

Set the region explicitly.

 set the region endpoint to "us-south"
$ ibmcloud kp region-set us-south

OK

The REGION must be a valid regional endpoint.

 this should fail (not a valid regional endpoint)
$ ibmcloud kp region-set not-a-region

FAILED





 Example 3 

Unset (remove) the regional endpoint.

 remove the regional endpoint
$ ibmcloud kp region-set -u

OK







 Required parameters 



* -i, --instance-id

The IBM Cloud instance ID that identifies your Key Protect instance.
The default setting is unencrypted http.

ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET ... [--metadata-service-protocol http | https] ...

--metadata-service-protocol value : The communication protocol to use for the metadata service
endpoint. Applies only when the metadata service is enabled. One of: http, https. (default: "http")

To enable secure access on an existing instance, specify a value for the protocol sub-property of the metadata service when you use the instance-update command.







 Set the metadata hop limit by using the CLI 

You can set a hop limit for IP response packets from the metadata service by specifying a hop limit value between 1 (default) and 64 for the Response hop limit sub-property of the Metadata service property for your instance.



 Set the metadata hop limit when you provision an instance 

To set the metadata hop limit when you provision an instance, specify a hop limit value between 1 (default) and 64 for the --metadata-service-response-hop-limit option when you use the instance-create command.

ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET ... [--metadata-service-response-hop-limit METADATA-SERVICE-RESPONSE-HOP-LIMIT] ...

--metadata-service-response-hop-limit value : The hop limit (IP time to live) for IP response packets
from the metadata service. (default: 1)









 Configure metadata settings by using the API 

You can enable and disable features of the metadata service by using the API.



 Disable auto link by using the API 

You can disable auto link for the instance metadata service when provisioning an instance. Auto link is enabled automatically when a trusted profile is selected. When autolink is enabled, the specified trusted profile is automatically linked to the virtual server instance when the instance is provisioned. The trusted profile that is associated with an instance that is provisioned with auto link is available to the instance immediately at startup.
* UI
* CLI
* API







 Setting the Databases for EnterpriseDB Admin Password 

The Databases for EnterpriseDB service is provisioned with an admin user. You must set the admin password before you can use it to connect.



 Setting the Databases for EnterpriseDB admin password in the UI 

To set the password through the IBM Cloud dashboard, select Manage from the service dashboard to open the management pane for your service. Open the Settings tab, and use the Change Database Admin Password pane to set a new admin password.

Zoom

![The Admin Password pane in Settings](https://cloud.ibm.com/docs-content/v1/content/e2b18e1112dc55facb736744a935365dce13849a/databases-for-enterprisedb/images/settings-admin-password.png)

Figure 1. The Admin Password pane in Settings





 Setting the Databases for EnterpriseDB admin password with the CLI 

Use the cdb user-password command from the [Databases for EnterpriseDB CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference) to set the admin password with the command line.

For example, to set the admin password for a deployment named "example-deployment", use the following command.

ibmcloud cdb user-password example-deployment admin <newpassword>





 Setting the Databases for EnterpriseDB admin password through the API 

The Foundation Endpoint that is shown on the Overview pane of your service provides the base URL to access this deployment through the API. Use it with the /deployments/{id}/users/{username} endpoint to set the admin password.

curl -X PATCH https://api.
[Set up BGP Message Digest 5 (MD5) authentication keys](https://cloud.ibm.com/docs/dl?topic=dl-dl-md5).
2. Log in to the [Direct Link console](https://cloud.ibm.com/interconnectivity/direct-link), then click the Direct Link name in the table to show its details.
3. Click the BGP tab, then click the MD5 authentication Deactivated switch to open the MD5 authentication window.
4. Complete the following information:



* For the keystore, select either Hyper Protect Crypto Services or Key Protect.
* Select an authentication keystore instance.
* Select an authentication key.



5. Click Activate. The information is added to the details page and the switch shows Activated.



If you later want to edit BGP values, click Edit in the upper right of the BGP section.





 Deactivating BGP MD5 authentication 

To deactivate BGP MD5 authentication, follow these steps:



1. Log in to the [Direct Link console](https://cloud.ibm.com/interconnectivity/direct-link), then click the Direct Link name in the table to show its details.
2. On the BGP tab, click the MD5 authentication Activated switch to show the Deactivate BGP MD5 authentication window.
3. Enter the name of the key to confirm, then click Deactivate. Your key is removed in the process.

The Details page is updated with your change.
ibmcloud resource service-instances
5. Get the plan ID of the instance.

Run the following command. Look for the entry for the monitoring instance. Then, copy the value of the field resource_plan_id. This value is needed to update the instance.

ibmcloud resource service-instances --long --output JSON
6. Set on the default_receiver property. Run the following command:

ibmcloud resource service-instance-update InstanceName --service-plan-id PlanID -p '{"default_receiver": true}'

Where PlanID is the resource plan ID of your monitoring instance.