vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-9implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-9scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-9nist-supplemental-guidance)



[SA-10 - Developer Configuration Management](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10sa-10)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10control-requirements)
* [Additional IBM Cloud for Financial Services specifications](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10additional-ibm-cloud-for-financial-services-specifications)
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10nist-supplemental-guidance)
[Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Hybrid Cloud Operations: Update from-the-cloud tunnel endpoint tag ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Localization Resources: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Metadata File Entry: Create/Modify ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) !
* [Accessing the infrastructure portfolio with your IBM Cloud Pay-As-You-Go or Subscription account](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsdefault_account)
* [Accessing a different classic infrastructure account](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credscredentials)
* [Customizing classic infrastructure permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsinfra_access)



* [Assigning infrastructure access through the console](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsinfra_console)
* [Assigning infrastructure access through the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsinfra_cli)





[Controlling user access with IBM Cloud IAM and Kubernetes RBAC](https://cloud.ibm.com/docs/openshift?topic=openshift-usersusers)



* [Example cluster use cases and IAM roles](https://cloud.ibm.com/docs/openshift?topic=openshift-usersexample-iam)
* [Assigning IBM Cloud IAM roles with the console](https://cloud.ibm.com/docs/openshift?topic=openshift-usersadd_users)
* [Assign IBM Cloud IAM roles with the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-usersadd_users_cli)



* [Assigning IBM Cloud IAM platform roles from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-usersadd_users_cli_platform)
This binary is a plugin. These are not meant to be executed directly.
Please execute the program that consumes these plugins, which will load any plugins automatically
6. [Configure the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-reference). To view the list of supported IBM Cloud Provider versions, refer to [IBM Cloud Provider plug-in releases](https://github.com/IBM-Cloud/terraform-provider-ibm/releases).
move2kube collect -a cf

The following is an example of the output from this command:

INFO[0000] Begin collection
INFO[0000] [collector.CfAppsCollector] Begin collection
INFO[0006] Changing metadata name from IBM Cloud to ibm-cloud
INFO[0009] [collector.CfAppsCollector] Done
INFO[0009] [collector.CfServicesCollector] Begin collection
INFO[0013] Changing metadata name from IBM Cloud to ibm-cloud
INFO[0013] [collector.CfServicesCollector] Done
INFO[0013] Collection done
INFO[0013] Collect Output in [/Users/elvinjohngalarza@ibm.com/move2kube-roks-demo/move2kube-demos-clean/m2k_collect]. Copy this directory into the source directory to be used for planning.

Run the following command to look at the collected data. The data is stored in your current working directory by default.

ls m2k_collect/cf

The following is an example of the output from this command:

cfapps-ibm-cloud-39e7da7a9e635f73.yaml
cfservices-ibm-cloud-3873c1404a0c63f9.yaml

In this case the m2k_collect/cf directory contains the runtime information of the application that you are going to transform.





 Create a plan on how to transform your IBM Cloud Foundry application 

The plan phase combines the runtime information with the enterprise-app source artifacts to determine a plan to transform and subsequently deploy the app to the cluster. You give Move2Kube the path to the source directory that contains the source code and the manifest files of the IBM Cloud Foundry application by using the -s flag.

Move the ./m2k_collect_cf directory into the enterprise-app/src directory using the following command:

mv m2k_collect move2kube-demos/samples/enterprise-app/src

Stay in the current working directory (move2kube-demos-<name_of_target>) that you moved m2k_collect from.
Migration Services for IBM Cloud 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use migrationtool-from-wanclds for the service name.

Platform roles

Actions



Table 116. Platform roles - Migration Services for IBM Cloud
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Minio 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use minio for the service name.

Platform roles

Actions



Table 117. Platform roles - Minio
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 IBM Cloud Monitoring Service 

Review the available platform and service roles and the actions mapped to each to help you assign access.
Connecting to your service instance 

You can connect command-line interfaces, IBM® or third-party applications, or apps that you create to your Watson Query instance.

For more information, see [Connecting to your Watson Query service instance](https://dataplatform.cloud.ibm.com/docs/content/dvaas/wq_connecting.html).
[External link icon](https://cloud.ibm.com/docs-content/v1/icons/launch-glyph.svg)](https://docs.internetofthings.ibmcloud.com/apis/swagger/v0002/org-admin.html/Device%20Bulk%20Configuration/get_bulk_devices) to list the devices in your organization: <br>curl -X GET "https://{orgId}.internetofthings.ibmcloud.com/api/v0002/bulk/devices?_limit=25" -u '{username}:{password}' 



†For more information about Watson IoT Platform MQTT messaging support, see [MQTT messaging ![External link icon](https://cloud.ibm.com/docs-content/v1/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/reference/mqtt/index.html).





 API docs 

Use the following URL to view the Watson IoT Platform API docs: [Watson IoT Platform REST APIs ![External link icon](https://cloud.ibm.com/docs-content/v1/icons/launch-glyph.svg)](https://docs.internetofthings.ibmcloud.com/apis/swagger/index.html).

From this landing page, you can access the documentation for the available Watson IoT Platform APIs.





 Interactive API docs 

Use the following URL to view and use the interactive API docs for your Watson IoT Platform organization:

https://{orgId}.internetofthings.ibmcloud.com/docs/index.html

Tip: You can also access the interactive API docs directly from the Watson IoT Platform dashboard by selecting the menu bar help icon in the upper right corner of the window and then clicking API.

From this landing page, you can access the documentation for the available Watson IoT Platform APIs.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/checkmark-icon.svg) 
 IBM Watson® Visual Recognition ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/checkmark-icon.svg) 
 IBM® Voice Agent with Watson ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/checkmark-icon.svg)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/icons/checkmark-icon.svg) 
 IBM Watson® Knowledge Studio 
 IBM Watson® Language Translator ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/icons/checkmark-icon.svg) 
 IBM Watson® Natural Language Understanding ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/icons/checkmark-icon.svg) 
 IBM Watson® Speech to Text ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/icons/checkmark-icon.svg) 
 IBM Watson® Text to Speech ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/icons/checkmark-icon.svg) 



The following table lists Watson services that are deprecated:



Table 3. Watson services that require actions for data events and are deprecated

 Service Name Paid plan required Other configuration required 

 IBM Watson® Compare and Comply ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/icons/checkmark-icon.svg) 
 IBM Watson® Visual Recognition !
dig myapp-abcdefg.ce-abc1abcd23efghijklmn-4o5ddc1a6fde0ec0aebe4cf134f8c000-0000.eu-de.containers.appdomain.cloud A +short

The dig command returns information similar to the following example. Your IP addresses are different, depending on the domain that your app is assigned.

10.0.2.244
10.0.3.19
10.0.1.148



To access your application, the browser or client must to be able to reach these IP addresses. If these IP addresses are private, then the application is accessible only on that private network.
Listing Kafka event subscriptions...
OK

Name Age Ready Destination Type Destination Path Consumer Group Reason
mykafkasubscription 94s true app kafka-receiver-app knative-kafka-source-dc367965-15e4-44f3-bedf-25d453524a68







 ibmcloud ce subscription kafka update 

Update a Kafka event subscription.

ibmcloud ce subscription kafka update --name KAFKA_SOURCE_NAME [--broker BROKER] [--destination DESTINATION] [--destination-type DESTINATION_TYPE] [--extension EXTENSION] [--extension-rm EXTENSION_RM] [--output OUTPUT] [--password PASSWORD] [--path PATH] [--quiet] [--secret SECRET] [--topic TOPIC] [--username USERNAME]



 Command Options 

--name, -n
: The name of the Kafka event subscription. This value is required.

--broker, -b
: Set a broker in the Kafka source. A broker is a Kafka server to which the consumer connects. This option can be specified multiple times. This value is optional.

--destination, -d
: The name of the application or job resource that you want to receive events; for example, myapp. If needed, use the --path option to further qualify an app destination. This value is optional.

--destination-type, --dt
: The type of the destination. Valid values are app and job. This value is optional.

--extension, --ext
: Set CloudEvents extensions to send to the destination. Must be in NAME=VALUE format. This action adds a new CloudEvents extension or overrides an existing CloudEvent attribute. Specify one extension per --extension option; for example, --ext extA=A --ext extB=B. This value is optional.

--extension-rm, --ext-rm
: Remove CloudEvents extensions to send to the destination by specifying the name of the key.
Valid values: ua.
* value: The exact UserAgent string to match with this rule.





* Option fields are paused, description.



* paused: Whether this rule is currently disabled.
* description: Some useful information about this rule to help identify the purpose of it.







Sample JSON data:

{
"mode": "block",
"configuration": {
"target": "ua",
"value": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/603.2.4 (KHTML, like Gecko) Version/10.1.1 Safari/603.2.4"
}
}



* For --type lockdowns: The JSON data describing a lockdown rule as follows.



* Required fields are urls, configurations.



* urls: URLs to be included in this rule definition.



* Wildcards are permitted.
* The URL pattern entered here will be escaped before use.
* This limits the URL to just simple wildcard patterns.



* configurations: List of IP addresses or CIDR ranges to use for this rule.



* This can include any number of ip or ip_range configurations that can access the provided URLs.
* target: The request property to target. Valid values: ip, ip_range.
* value: IP addresses or CIDR. If target is ip, then value should be an IP addresses, otherwise CIDR.





* Option fields are paused, description.



* paused: Whether this rule is currently disabled.
* description: Some useful information about this rule to help identify the purpose of it.







Sample JSON data:

{
"urls": [
"api.mysite.com/some/endpoint"
],
"configurations": [
{
"target": "ip",
"value": "127.0.0.1"
},
{
"target": "ip_range",
"value": " 2.2.2.0/24"
}
]
}
Required.

Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --configuration-prototype=@path/to/file.json.





 Example 

ibmcloud secrets-manager configuration-create --configuration-prototype='{"config_type": "private_cert_configuration_root_ca", "name": "example-root-CA", "max_ttl": "43830h", "crl_expiry": "72h", "crl_disable": false, "crl_distribution_points_encoded": true, "issuing_certificates_urls_encoded": true, "common_name": "example.com", "alt_names": ["alt-name-1","alt-name-2"], "ip_sans": "127.0.0.1", "uri_sans": "https://www.example.com/test", "other_sans": ["1.2.3.5.4.3.201.10.4.3;utf8:test@example.com"], "ttl": "2190h", "format": "pem", "private_key_format": "der", "key_type": "rsa", "key_bits": 4096, "max_path_length": -1, "exclude_cn_from_sans": false, "permitted_dns_domains": ["exampleString"], "ou": ["exampleString"], "organization": ["exampleString"], "country": ["exampleString"], "locality": ["exampleString"], "province": ["exampleString"], "street_address": ["exampleString"], "postal_code": ["exampleString"], "serial_number": "d9:be:fe:35:ba:09:42:b5:35:ba:09:42:b5"}'
"name": "PROFILE NAME",
"version": "PROFILE VERSION"
},
"names":
"CONTROL NAME",
"CONTROL NAME"
]
}
]
},
"iam_permissions":
{
"service_name": "SERVICE PROGRAMMATIC NAME",
"role_crns":
"ROLE",
"ROLE"
],
"resources":
{
"name": "NAME",
"description": "DESCRIPTION",
"role_crns":
"ROLE1",
"ROLE2"
]
}
]
}
],
"architecture":
{
"features":
{
"title": "FEATURE NAME",
"description": "FEATURE DESCRIPTION"
}
],
"diagrams":
{
"diagram": {
"url": "URL",
"api_url": "API URL",
"url_proxy": {
"url": "URL",
"sha": "SHA"
},
"caption": "DIAGRAM LABEL",
"type": "TYPE",
"thumbnail_url": "THUMBNAIL URL"
}
}
],
"description": "DIAGRAM DESCRIPTION"
}
],
"dependencies":
{
"catalog_id": "ID",
"id": "ID",
"name": "PRODUCT PROGRAMMATIC NAME",
"kind": "FORMAT KIND",
"version": "VERSIONS OR RANGE OF VERSIONS",
"flavors": "VARIATION NAME OR NAMES"]
}
],
"release_notes_url": "RELEASE NOTES URL",
"configuration":
{
"key": "KEY",
"type": "TYPE",
[Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Extension Service API Definition: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Extension Service API Definition: View ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Extension Services: View ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Extensions: View ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 External Service: Manage !
<sc:ServiceDefinition xmlns:sc="http://www.platform.com/ego/2005/05/schema/sc" xmlns:ego="http://www.platform.com/ego/2005/05/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:schemaLocation="http://www.platform.com/ego/2005/05/schema/sc ../sc.xsd http://www.platform.com/ego/2005/05/schema ../ego.xsd" ServiceName="SMCP">
<sc:Version>1.2</sc:Version>
<sc:Description>SMC: Proxy</sc:Description>
<sc:MinInstances>1</sc:MinInstances>
<sc:MaxInstances>1</sc:MaxInstances>
<sc:Priority>10</sc:Priority>
<sc:MaxInstancesPerSlot>1</sc:MaxInstancesPerSlot>
<sc:NeedCredential>TRUE</sc:NeedCredential>
<sc:ControlPolicy>
<sc:StartType>AUTOMATIC</sc:StartType>
<sc:MaxRestarts>10</sc:MaxRestarts>
<sc:HostFailoverInterval>PT1S</sc:HostFailoverInterval>
</sc:ControlPolicy>
<sc:AllocationSpecification>
<ego:ConsumerID>/ManagementServices/EGOManagementServices</ego:ConsumerID>
<!--The ResourceType specifies a "compute element" identified by the URI used below-->
<sc:ResourceSpecification ResourceType="http://www.platform.com/ego/2005/05/schema/ce">
<ego:ResourceGroupName>ManagementHosts</ego:ResourceGroupName>
"name": "org1profile",
"description": "Network on IBP v2",
"version": "1.0.0",
"client": {
"organization": "org1"
},
"organizations": {
"org1": {
"mspid": "org1",
"certificateAuthorities": [
"xyz-ca.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud:443"
],
"peers": [
"va0414-ba-peer.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud:443",
"va0414-peer.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud:443"
]
}
},
"peers": {
"xyz-peer.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud:443": {
"url": "grpcs://xyz-peer.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud:443",
"tlsCACerts": {
"pem": "-----BEGIN CERTIFICATE-----nnnnnn-----END CERTIFICATE-----n"
},
"grpcOptions": {
"ssl-target-name-override": "xyz-peer.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud"
}
},
"va0414-peer.openshift-ibpv2-test-1-0001.us-south.containers.appdomain.cloud:443": {
: Name or UUID of service ID.

POLICY_ID (required)
: ID of the service policy.

--output FORMAT
: Specify output format. Only 'JSON' is supported.

-f, --force (optional)
: Display service policy without confirmation.

-q, --quiet
: Suppress verbose output.

--api-version
: Version of the access policy API.





 Examples 

Show policy 140798e2-8ea7db3 of service test:

ibmcloud iam service-policies test 140798e2-8ea7db3

Show policy 140798e2-8ea7db3 of service ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976:

ibmcloud iam service-policies ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976 140798e2-8ea7db3







 ibmcloud iam service-policy-create 

Create an access policy and assign it to a service ID:

ibmcloud iam service-policy-create SERVICE_ID {--file JSON_FILE | -r, --roles ROLE_NAME1,ROLE_NAME2... [--service-name SERVICE_NAME] [--service-instance SERVICE_INSTANCE_GUID] [--region REGION] [--resource-type RESOURCE_TYPE] [--resource RESOURCE] [--resource-group-name RESOURCE_GROUP_NAME] [--resource-group-id RESOURCE_GROUP_ID] [--account-management] [--attributes name=value,name=value...]} [--output FORMAT] [-q, --quiet] [-f, --force] [--api-version v1 | v2]



 Command options 

SERVICE_ID (required)
: Name or UUID of service ID.

--file
: JSON file of policy definition.
<-- </ul> -->

Sample JSON data: {
"targets":
{
"target": "url",
"constraint": {
"operator": "matches",
"value": "example.com/images/"
}
}
],
"actions":
{
"id": "ssl",
"value": "flexible"
},
{
"id": "browser_cache_ttl",
"value": 14400
},
{
"id": "security_level",
"value": "medium"
},
{
"id": "cache_level",
"value": "basic"
},
{
"id": "edge_cache_ttl",
"value": 7200
},
{
"id": "bypass_cache_on_cookie",
"value": "wp-.|wordpress.|comment_."
}
] ! !
}
Show more
-s, --json-str: Deprecated. The JSON data describing a page rule.-j, --json-file: Deprecated. A file contains input JSON data.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-page-rule-create" "> --><-- <section "id="section-command-examples-page-rule-create" "> --> Examples Create a page rule for domain 31984fea73a15b45779fa0df4ef62f9b.