vania-janet/multiturn-rag-retrieval-data huggingface dataset:
<-- </section "id="section-kp-keys-required" "> --><-- <section "id="section-kp-keys-optional" "> --> Optional parameters -c, --crn: Include the cloud resource name (CRN) in the output.<-- </section "id="section-kp-keys-optional" "> --><-- </section "id="section-kp-keys" "> --><-- <section "id="section-kp-region-set" "> --> kp region-set Target a different Key Protect regional endpoint. ibmcloud kp region-set REGION
-i, --instance-id INSTANCE_ID
-u, --unset] ! ! ! ! ! ! ! ! ! ! ! ! ! !
<-- <section "id="section-kp-region-set-examples" "> --> Examples These are examples of kp region-set.<-- <section "id="section-kp-region-set-example-1" "> --> 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. jp-tok
3. eu-de
4. eu-gb
5. us-south
6. us-east
7. staging (us-south)
Enter a number:
5
OK
<-- </section "id="section-kp-region-set-example-1" "> --><-- <section "id="section-kp-region-set-example-2" "> --> Example 2 Set the region explicitly. set the region endpoint to "us-south"
$ ibmcloud kp region-set us-south

OK
PUT /v1/{crn}/zones/{domain_id}/setting/max_upload internet-svcs.performance.update internet-svcs.max-upload-setting.update 
 Get TLS client authentication settings. GET /v1/{crn}/zones/{domain_id}/setting/tls_client_auth internet-svcs.security.read internet-svcs.tls-client-auth-setting.read 
 Update TLS client authentication settings. PUT /v1/{crn}/zones/{domain_id}/setting/tls_client_auth internet-svcs.security.update internet-svcs.tls-client-auth-setting.update 
 Get pseudo IPv4 settings. GET /v1/{crn}/zones/{domain_id}/setting/pseudo_ipv4 internet-svcs.zones.read internet-svcs.pseudo-ipv4-setting.read 
 Update pseudo IPv4 settings. PUT /v1/{crn}/zones/{domain_id}/setting/pseudo_ipv4 internet-svcs.zones.update internet-svcs.pseudo-ipv4-setting.update 
 Get origin error page passthrough settings. GET /v1/{crn}/zones/{domain_id}/setting/origin_error_page_pass_thru internet-svcs.zones.read internet-svcs.origin-error-page-pass-thru-setting.read 
 Update origin error page passthrough settings. GET /v1/{crn}/zones/{domain_id}/setting/origin_error_page_pass_thru internet-svcs.zones.update internet-svcs.origin-error-page-pass-thru-setting.update 
 Get brotli compression settings. GET /v1/{crn}/zones/{domain_id}/setting/brotli internet-svcs.performance.read internet-svcs.brotli-setting.read 
 Update brotli compression settings.
The CIDR is the IP address and the subnet mask for that subnet.
7. Enter your gateway for Gateway.
8. Add DNS server information. For example, for this Bare Metal Server, these values are 8.8.8.8 and 4.4.4.4 for public interfaces; and 10.0.80.11 and 10.0.80.12 for private interfaces.
9. Repeat these steps for each of the wired connections that you want to activate.
10. When you are finished, select OK, Quit.
11. Test that you have connectivity by pinging your server network. For example, to test the public network for this specific Bare Metal Server, ping 8.8.8.8.







 Step 3: Configuring your ignition file 

Complete the following steps to configure your ignition file. The ignition file is used to attach your bare metal server as a host in your Satellite location.

You must configure a separate ignition file for each bare metal host that you are attaching to the location.



1. [Download the host attach script for your location](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hostshost-attach-download). Make sure to specify RHCOS for the host operating system.
2. Get the host name for your bare metal system; for example, mybaremetalserver.
3. Convert your host name to base64 by running the following command, substituting <hostname> with your bare metal server host name:

echo <hostname> | base64
4. Open your ignition file and add the host name information to the "storage":{"files":[ section. Replace <hostname> with the base64 encoded output from the previous step.
{"overwrite": true,"path": "/etc/hostname","mode": 600,"contents": {"source": "data:text/plain;base64,<hostname>"},},],}
If you try to target a property that is not linked to a collection, a window is displayed to add a property to a collection.





 Targeting a segment with properties 

You can roll out property to one or more target segments. You can set different property values for different segments, if needed.



1. From the App Configuration console, go to Properties to display the list of properties available in the current environment of the App Configuration service instance.
2. Click Add targeting in the required property row to display the Target property to segments side panel.

Zoom

![Target property to segments](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-property-to-segments.png)

Figure 7. Target property to segments
3. Select Segments from the list. If no segments are available to target, click Create segment. For more information about creating a segment, see [Create a segment](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-segmentsac-create-segment).
4. Select the Property value (Inherited from property or Override).
5. Click Save rule to save the changes to the rules.
6. Click Add targeting.



If you try to target a property that is not linked to a collection, a window is displayed to add a property to a collection.
To resume pagination, provide the NextToken value in the starting-token argument of a subsequent command. (default: 0)



* Flag: --max-items NUMBER



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Set bucket CORS 



* Action: Sets the CORS configuration for a bucket in the user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos bucket-cors-put --bucket BUCKET_NAME [--cors-configuration STRUCTURE] [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* Optional: A STRUCTURE using JSON syntax in a file.



* Flag: --cors-configuration STRUCTURE
* JSON Syntax: --cors-configuration file://<filename.json> ======= The --cors-configuration command takes a JSON structure that describes the CORS configuration. In this example, the file:// prefix is used to load the JSON structure from the specified file.





{
"CORSRules": [
{
"AllowedHeaders": "string", ...],
"AllowedMethods": "string", ...],
"AllowedOrigins": "string", ...],
"ExposeHeaders": "string", ...],
"MaxAgeSeconds": integer
}
...
]
}



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Put object
{"configuration":{"maxmemory-policy":"allkeys-lru"}}

to either the CLI or to the API.



 Using the CLI 

View the configuration schema of possible settings through the Cloud Databases cli-plugin with the cdb deployment-configuration-schema command.

ibmcloud cdb deployment-configuration-schema <deployment name or CRN>

To change your configuration, use the cdb deployment-configuration command.

ibmcloud cdb deployment-configuration <deployment name or CRN> [@JSON_FILE | JSON_STRING]

The command reads the changes that you would like to make from the JSON object or a file. For more information, see the [reference page](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-configuration).





 Using the API 

There are two deployment-configuration endpoints, one for viewing the configuration schema and one for changing the configuration. To view the configuration schema, send a GET request to /deployments/{id}/configuration/schema.

To change the configuration, send the settings that you would like to change as a JSON object in the request body of a PATCH request to /deployments/{id}/configuration.

For more information, see the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-apichange-your-database-configuration).



 Available Configuration settings 

To check the current value of a setting, use [CONFIG GET](https://redis.io/commands/config-get) from a [CLI client](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-connecting-cli-client). You can check all of the settings by using CONFIG GET .

Many of the settings are used to configure Redis as a cache.
[Property type - String](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-property-string.png)

Figure 4. Property type - String



1. Specify the Default value. This value is returned by default and be overridden while targeting to a segment.



* Format: select the format of the string type from the list. Options are: Text, JSON, and YAML.
* Property value: specify the property value based on the format selected.









 Numeric 

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

Zoom

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

Figure 5. Property type - Numeric



1. Specify the Property value. This value is returned by default and can be overridden while targeting to a segment.







 Secret reference 

When you select the Property type as Secret reference, the Secrets Manager instance, and Default value details are displayed:

Zoom

![Property type - Secret reference](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-property-secret-reference.png)

Figure 6. Property type - Secret reference



1. Specify the Secrets Manager instance information from where the values need to be pulled.



* Resource group: select the resource group from where the Secrets Manager instance to be used.
* Secrets Manager instance: select the Secrets Manager instance to be used for the specified property.



2. Specify the Default value.
ID Name Destination Type Address
cavvku1p1h1gcfgk1kn1_uwokw satellite-cosRegional-cavvku1p1h1gcfgk1kn1 cloud TLS i11aa11a1a1a11a11-1a11a1aaa1a1a1a1a-c000.us-east.satellite.appdomian.cloud:11111
2. Open the file editor in the CLI.

oc edit configs.imageregistry.operator.openshift.io/cluster
3. Find the following section to edit.

storage:
emptyDir: {}
managementState: Managed
storageManaged: true
4. Replace emptyDir: {} with your bucket information and location endpoints.

s3:
bucket: <bucket_name>
region: <bucket_region>
regionEndpoint: <location_link_endpoint>
virtualHostedStyle: false

Example section after adding the bucket and location information.

storage:
managementState: Managed
s3:
bucket: my_bucket
region: us-east
regionEndpoint: https://i11aa11a1a1a11a11-1a11a1aaa1a1a1a1a-c000.us-east.satellite.appdomian.cloud:11111
virtualHostedStyle: false
storageManaged: true
5. Save and apply the changes.



7. Verify that the image registry was configured by checking for a pod that begins with image-registry- in the openshift-image-registry namespace.

oc get pod -n openshift-image-registry

Example output.

NAME READY STATUS RESTARTS AGE
image-registry-63p54b8add-vkjju 1/1 Running 0 16m









 Exposing apps 

Several options exist to securely expose apps to traffic requests from the public network, from resources that are connected to your hosts' private network, or from resources in IBM Cloud.
* [list_artifacts](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectllist_artifacts)
* [load_artifact](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectlload_artifact)
* [put_data](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectlput_data)
* [get_data](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectlget_data)
* [serialize](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectlserialize)
* [deserialize](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectldeserialize)





 set_env 

 <key>: The name of the environment variable e.g. pipeline-namespace, app-name
 <value>: Value of the key
set_env <key> reads <value> from stdin
set_env <key> <value>

If the <value> argument is missing, set_env reads it from the standard input. Saves an arbitrary string that can be retrieved later on with [get_env](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectlget_env).

Example:

 set value provided as argument
set_env app-name "my-app-name"

 set value provided via stdin
echo "my-app-name" | set_env app-name
set_env my-api-key < /config/my-api-key





 get_env
* [Creating Satellite configurations from the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-gitopscreate-satconfig-cli-gitops)



* [Updating your Satellite configuration](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-gitopssatcon-manage-update-gitops)



* [Updating your subscription from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-gitopssatcon-manage-update-console-gitops)
* [Updating your Satellite Config with the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-gitopssatcon-manage-update-cli-gitops)





[Managing Direct Upload configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-uploadsatcon-manage-direct-upload)



* [Creating Satellite configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-uploadsatcon-create)



* [Creating Satellite configurations from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-uploadcreate-satconfig-ui)
* [Creating Satellite configurations from the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-uploadcreate-satconfig-cli)



* [Updating your Satellite Config configuration](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-uploadsatcon-manage-update)



* [Updating your Satellite Config from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-manage-direct-uploadsatcon-manage-update-console)
See [Host header support](https://cloud.ibm.com/docs/CDN?topic=CDN-about-content-delivery-networks-cdn-host-header-support) for more information.
* Provide an optional Path where content can be retrieved from on the origin. See [Path-based CDN mappings](https://cloud.ibm.com/docs/CDN?topic=CDN-about-content-delivery-networks-cdn-path-based-cdn-mappings) to understand the implications of adding a path at this time.

For Server:



* Enter the Origin server address (hostname or IPv4 address of the origin server). If HTTPS port is also selected, the Origin server address must be the hostname, not the IP address.



For Object Storage:



* Enter the required S3 Endpoint ([S3 format public endpoint](https://cloud.ibm.com/docs/cloud-object-storage/info?topic=cloud-object-storage-advanced-endpointsadvanced-endpoint-reference)) from which to fetch the object.
* Enter the name of the Bucket in which your content is stored.



You must set the Access Control List (ACL) for each Object in your Bucket to "public-read" with your Cloud Object Storage provider. For more information, see [Allowing public access](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-public-access).
* Provide an HTTP port, an HTTPS port, or both. These fields indicate which protocol and port number can be used to contact the origin server. For non-default port numbers, refer to [FAQs](https://cloud.ibm.com/docs/CDN?topic=CDN-faqsare-there-any-restrictions-on-what-port-numbers-are-allowed) for a list of allowed port numbers.

An SSL certificate option appears if you select HTTPS port. You can choose Wildcard or DV SAN certificate as your SSL certificate option. Both offer the enhanced security provided by HTTPS.
: The wsk API version. This flag is optional.

--authKEY, -uKEY
: The wsk authorization KEY. This flag is optional.

--certSTRING
: The wsk client certificate. This flag is optional.

--cliversion
: The wsk CLI version. This flag is optional.

--keySTRING
: The wsk client KEY. This flag is optional.

--namespaceNAMESPACE
: An IAM namespace name or ID. This flag cannot be set for Cloud Foundry namespaces. This flag is optional.





 Example 

ibmcloud fn property get --auth







 ibmcloud fn property set 

Set a property. At least one flag is required. After a property is set, it is retained on your workstation at <home_dir>/.bluemix/plugins/cloud-functions/config.json. To remove a property, run [ibmcloud fn property unset --<property>](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_prop_set).

ibmcloud fn property set [--auth KEY] [--cert STRING] [--key STRING] [--namespace NAMESPACE]



 Command options 

--authKEY, -u
: The wsk authorization KEY. This flag is optional.

--certSTRING
: The wskclient certificate. This flag is optional.

--keySTRING
: The wsk client KEY. This flag is optional.

--namespaceNAMESPACE
: An IAM namespace name or ID. This flag cannot be set for Cloud Foundry namespaces. This flag is optional.





 Example 

ibmcloud fn property set --namespace myNamespace

Output

ok: whisk namespace set to myNamespace







 ibmcloud fn property unset
Complete all of the required fields, and click Next.
7. Click Create Rule.
8. Complete all of the required fields.
9. Optional. Select the Regression Check box to opt out of test case regression. This option is available only for data sets, Unit Tests, Code Coverage, and Functional Verification Tests.
10. Click Save.



If you want to add another rule, repeat from step 3.

For more information about data sets, see [Managing data sets](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-adding-data-sets).





 Adding a rule to an already established policy 

You can add rules to policies that are already defined.



1. From the Policies page, select the policy to add the rule.
2. Click Create Rule.
3. Complete all required fields, then click Save.







 Editing rules 

You can edit the rules that you established with your policies. You can change the rule description, the results file format, and the minimum code coverage required.

To edit rules, complete the following steps:



1. From the Policies page, select the policy that has the rule you want to edit.
2. Click the Edit icon ![write icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_write.svg) for the rule.
3. Complete all required fields, and click Save.
Each of the Flag type is having a default value.



* When you set the toggle switch to ON, the value for the Enabled value is required, which can be overridden when targeting to a segment.
* When you set the toggle switch to OFF, the value for the Disabled value is required, which can be overridden when targeting to a segment.





 Boolean 

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

Zoom

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

Figure 3. Feature flag type - Boolean



1. Select the Enabled value from the list. This value is returned by default when the 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. This value is returned by default when toggle switch is set to OFF for the feature flag.







 String 

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

Zoom

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

Figure 4. Feature flag type - String



1. 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.
*  CLI







  Enforcing target locations 

To enforce target locations in your IBM Cloud account, you must configure IBM Cloud Metrics Routing account settings to limit the locations.



  Prereqs 



1.  [Install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2.  [Install the IBM Cloud Metrics Routing CLI](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-metrics-router-cli-config).
3.  Ensure you have the [correct IAM permissions to configure IBM Cloud Metrics Routing settings.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-iam)
4.  Log in to IBM Cloud by running the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)







  Step 1. Get details of your current account settings 

Get details of your current account settings. Run the following command:

ibmcloud metrics-router setting get

The setting Permitted target regions list all the locations where you allowed administrators to configure targets in the account.





  Step 2. 

To manage the list of permitted regions, run the following command:

ibmcloud metrics-router setting update --permitted-target-regions REGIONS

Where REGIONS define a comma-separated list of regions.

For example, you can run the following command to set 3 regions only:

ibmcloud metrics-router setting update --permitted-target-regions "us-south","us-east","eu-de"
Configuring the input variables 

Input variables are parameters that users specify when they install your product. You can review and modify the input variables that were imported from your catalog manifest or add new input variables to your deployable architecture. When you configure your input variables, you can update the requirements, visibility, and format of the input variables.



1. To add new input variables, click Add input variables.
2. Select the parameters that you want to include, or select Parameters to select all options, and click Add.
3. From the input variables table, select a parameter, and click Edit.
4. Select the applicable options to require or hide the value.

Required
: Users are required to specify the parameter during installation.

Hidden
: The parameter is included in the configuration but is not shown to users and is not configurable.
5. You can choose a value type, default value, and description for each input variable to customize how the value appears to users.

Unless they are hidden, input variables display for your users, and can be configured during the deployment process. Ensure that your input variable descriptions are clear and concise for your users.
6. Click Save > Next.







 Updating output values 

You can update the descriptions of any output values that you included. The output values are shown to users when they deploy your product.

If you didn't include output values, you can't update the descriptions.



1. From the Configure the deployment details section, go to the Output values section, and find the value that you want to update.
2. Enter a value description that helps the user understand its purpose.
3. Click Next.









 Configuring the input variables by using the CLI 

After you review the version details, you're ready to configure the input variables by updating your offering.



1. Run the [ibmcloud catalog offering get](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-pluginget-offering) command: