vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Specifying host groups by using key-value pairs in hosts.ini files is not supported.
* You must manually update the hosts.ini file if hostname or IP address of target hosts change.
* All target hosts must be configured with the same public SSH key. When you use the static inventory file in your Schematics action, you can specify one SSH key to authenticate with all target hosts that are included in your resource inventory. The SSH key should contain n at the end of the key details in case of command-line or API calls. For more information about SSH keys, see [Adding an SSH key](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-adding-an-ssh-key).









 Dynamically building resource inventories from Schematics Workspaces 

You can dynamically build your resource inventory from the IBM Cloud resources that you provisioned with Schematics Workspaces.

Dynamic resource inventories references IBM Cloud resources that you provisioned with Schematics Workspaces. To retrieve the IBM Cloud resources from your workspaces, use predefined resource queries. You do not need to keep track of the IP addresses that were assigned to your target resources as Schematics automatically determines the target hosts when you use this inventory in the Schematics action.



1. From the [Schematics inventories dashboard](https://cloud.ibm.com/schematics/inventories), click Create Inventory.
2. Enter a name for your inventory, verify your location, and select your Resource group where you want to create an inventory.
3. Select the Host groups tab.
4. Click Create host group.
5. Enter a name for your host group and select the Schematics Workspaces that provisioned the target hosts that you want to add to your host group.
6. Optional: Click Add query to add another condition to your query and limit the number of target hosts that are added to your host group. You can choose to identify your hosts by using the resource name or a tag.
Administrator View details about projects, configurations, and deployments<br><br>Validate a configuration<br><br>Edit a configuration<br><br>Create a project<br><br>Edit a project<br><br>Delete a project<br><br>Create a configuration<br><br>Discard a draft configuration<br><br>Deploy configuration changes<br><br>Destroy resources.<br><br>Force approve changes that failed validation crn:v1:bluemix:public:iam::::role:Administrator 







 Security and Compliance Center 

You can give users access to create, update, and delete resources for the Security and Compliance Center service in the account that you are assigned access.



Table 18. Roles and example actions for the Security and Compliance Center service

 Roles Actions 

 Viewer View available profiles and attachments<br><br>View created resources such as scopes, credentials, or rules<br><br>View global settings for the service 
 Operator Access the Security and Compliance Center dashboard to view current posture and results<br><br>Create an audit log for monitoring compliance activity 
 Editor Create, update, or delete objects such as scopes, credentials, and collectors<br><br>Update the parameter settings of a goal<br><br>Create, update, or delete rules and templates<br><br>Edit global admin settings for the service 
 Administrator Perform all platform actions based on the resource that this role is being assigned, including assigning access policies to other users. 
 Manager Permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 
 Reader Perform read-only actions within a service such as viewing service-specific resources. 
 Writer Permissions beyond the reader role, including creating and editing service-specific resources. 







 Software instance 

You can give users access to create, delete, or update a software instance. And, you can give users access to view the details page and the logs for the software instance.



Table 19. Roles and example actions for the Software instance service

 Roles Actions 

 Viewer View the software instance details page
Administrator Perform all platform actions based on the resource that this role is being assigned, including assigning access policies to other users. crn:v1:bluemix:public:iam::::role:Administrator 
 Manager Permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. crn:v1:bluemix:public:iam::::serviceRole:Manager 
 Reader Perform read-only actions within a service such as viewing service-specific resources. crn:v1:bluemix:public:iam::::serviceRole:Reader 
 Writer Permissions beyond the reader role, including creating and editing service-specific resources. crn:v1:bluemix:public:iam::::serviceRole:Writer 







 Software instance 

You can give users access to create, delete, or update a software instance. And, you can give users access to view the details page and the logs for the software instance.



Table 19. Roles and example actions for the Software instance service

 Roles Actions role_ID value 

 Viewer View the software instance details page crn:v1:bluemix:public:iam::::role:Viewer 
 Operator Update a software instance<br><br>View the details page for the software instance crn:v1:bluemix:public:iam::::role:Operator 
 Editor Create, delete, update a software instance<br><br>View the details page for the software instance crn:v1:bluemix:public:iam::::role:Editor 
 Administrator Create, delete, update a software instance<br><br>View the details page for the software instance<br><br>View the logs for the software instance<br><br>Assign IAM permissions crn:v1:bluemix:public:iam::::role:Administrator 







 Support center 

You can give users access to manage support cases.



Table 20. Roles and example actions for the Support Center service

 Roles Actions role_ID value
For more information about creating API keys associated with a service ID, see [Managing service ID API keys](https://cloud.ibm.com/docs/account?topic=account-serviceidapikeysserviceidapikeys).

[Classic infrastructure API keys](https://cloud.ibm.com/docs/account?topic=account-classic_keys) are used to call the APIs for classic infrastructure services. You can create only one classic infrastructure API key at a time. You can create a classic infrastructure API key for yourself from the API keys page or the User details page.

IBM Cloud API keys can also be used to access classic infrastructure APIs.

Some services in IBM Cloud might provide an API key when you work with the service that is an auto-generated API key associated with a service ID. For example, if you are viewing the product details of a Watson service by going to the Resource list page, you can create a credential that includes an API key and secret that is specific to that service on the Service credentials page.





 Working with API keys 

To manage the IBM Cloud API keys that are associated with your user identity or the ones that you have access to manage for other users in the account, go to Manage > Access (IAM) > API keys in the IBM Cloud console.

On the IBM Cloud API keys page, you can create, edit, or delete IBM Cloud API keys for yourself, and you can manage all classic infrastructure API keys for users to which you are an ancestor in the user hierarchy. This means you can manage API keys for all users you invited to the account, or your child users invited to the account, and so on. In addition, if you are the account owner or a user with the required access to manage other user's API keys in the account, you can use the View filter to list and manage those API keys.



 Required access for managing API keys 

By default, you always have access to create your own API keys, and then update and delete them as needed. You also can manage your own classic infrastructure API key and any users' classic infrastructure API keys who you are an ancestor of in the classic infrastructure user hierarchy, meaning you invited the user or someone you invited to the account invited the user, and so on.
* CLI
* API







 About targets 

You can manage IBM Cloud® Metrics Routing targets in your account by using the IBM Cloud Metrics Routing CLI, the IBM Cloud Metrics Routing REST API, and Terraform scripts. A target is a resource where you can collect metrics data. The resource can be located in the same IBM Cloud account where metrics are generated or in a different account.



 Understanding how targets work in your account 

Note the following information about targets:



* Targets are regional under an account and can be accessed from any regional IBM Cloud Metrics Routing API endpoint.
* You can define a target in any of the supported locations where IBM Cloud Metrics Routing is available. For more information, see [Locations](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions).
* You can configure up to 16 targets in each account.
* You can configure up to two default targets for each IBM Cloud account.

Default targets collect metrics from locations where you do not specify in the account where to route the metrics that are generated in that location.
* Information about targets is stored as metadata in the primary and backup locations that you set for the IBM Cloud account. The information that is stored include details about the destinatiion resource and credentials to send metrics.

The primary metadata location must be set prior to configuring a target.

If you do not configure a primary metadata location, the location is set to the location where you define your first target in the account. For more information, see [Configuring account settings](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-settings).
* You can use private and public endpoints to manage targets. For more information about the list of endpoints that are available, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).
Managing classic infrastructure API keys 

You can use classic infrastructure API keys to access classic infrastructure APIs. You can have only one classic infrastructure API key per user, and each user can create, delete, and view the details for their API key. If you are an ancestor in the classic infrastructure hierarchy for a user, you can also edit or delete those user's API keys.

IBM Cloud® [API keys](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key-api) can also be used to access classic infrastructure APIs.

To manage classic infrastructure API keys, go to Manage > Access (IAM) > API keys, and select Classic infrastructure API keys in the IBM Cloud console. You can see your classic infrastructure API key and any API keys for users that you are an ancestor for in the user hierarchy, meaning you invited the user or someone you invited to the account invited the user, and so on.



 Creating a classic infrastructure API key 

When you create a classic infrastructure API key, you can use the IP address restrictions feature on the User details page. To create a classic infrastructure API key, complete the following steps:



1. In the IBM Cloud console, go to Manage > Access (IAM) > API keys, and select Classic infrastructure API keys.
2. Click Create a classic infrastructure key.

If you don't see this option, check to see if you already have a classic infrastructure API key that is created because you're only allowed to have one in the account per user.
3. Copy or download the API key, and save it in a safe place. You can retrieve the details of the API key later.



To get the details of a classic infrastructure API key after you create it, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > View details. You can copy the API key value.
If you use CALL iceberg_data_rollback_to_snapshot with a timestamp, you cannot call the stored procedure to move to a later timestamp. Use Spark SQL as an alternative.





 Issue: Only the creator has DROP access on the table in Apache Hive (API) 

Only the creator of a table can drop the table that is created in Apache Hive catalog. Other users cannot drop the table even if they have an explicit DROP access to the table. They will get the Access Denied message.





 Issue: User provided certificates are not supported by watsonx.data 

Currently, user provided certificates are not supported in watsonx.data when adding database connections, object store buckets, or when using ibm-lh utility.





 Issue: CTAS query that uses Parquet format fails 

When you do a CTAS operation to Iceberg tables in Parquet format, you may get the following error:

Size is greater than maximum int value

Workaround: Use the presto-cli to do the CTAS operation and set the following session parameter before the CTAS query:

set session task_writer_count=32

For details about connecting to a Presto server through a CLI, see [Connecting to a Presto Server](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-con-presto-cli).





 Issue: No columns to parse from file error 

When you try to ingest folder from AWS S3 using the ibm-lh tool, the following error may be encountered if there are no empty files in the folder:

No columns to parse from file

Workaround: First list the folders inside the bucket using aws s3 ls command. If no empty files are listed, copy all the files to another folder using aws s3 cp command.
curl -X GET "$vpc_api_endpoint/v1/placement_groups?version=2021-04-20&generation=2" -H "Authorization: $iam_token"





 Listing all placement groups with Terraform 

You can generate a list of placement groups for a region. You can list all the existing placement groups in your IBM Cloud VPC by using Terraform.

The following example lists all the existing placement groups.

data "ibm_is_placement_groups" "is_placement_groups" {
}





 Viewing placement group details with the UI 

You can view details about a placement group, such as the placement group name, assigned resource group, placement group ID, location, date placement group was created, and the specified placement group strategy.

To view details about a placement group, complete the following steps.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Placement Groups.
2. Click the name of the placement group about which you want to view details.







 Viewing placement group details with the CLI 

You can view details about a placement group, such as the placement group name, assigned resource group, placement group ID, location, date placement group was created, and the specified placement group strategy.

You can retrieve the details a placement group in your IBM Cloud VPC by using the command-line interface (CLI).

To retrieve the details of a placement group by using the CLI, use the ibmcloud is placement-group command. Specify the placement group ID.

The following example retrieves the details for a placement group named PLACEMENT_GROUP.

ibmcloud is placement-group PLACEMENT_GROUP --output JSON





 Viewing placement group details with the API
People with the project manager role can perform almost all tasks except creating a workspace. An administrator must create the workspace initially and assign project managers to it.
2. Give the workspace a name. Choose a short name that reflects your domain content or the purpose of the model. If you need to, you can change the workspace name later.
3. Identify the language of the documents in your workspace. The documents that you add to the workspace, and the dictionaries that you create or upload, must be in the language that you specify.
4. Optional: If you want to change the tokenizer that is used by the application from the default machine learning-based tokenizer, then you can expand the Advanced Options section, and choose Dictionary-based tokenizer.

The default tokenizer is more advanced than the dictionary-based tokenizer; it uses machine learning to identify the tokens in the source documents based on the statistical learning it has done in the language of the source documents. It identifies tokens with more precision because it understands the more natural and nuanced patterns of language. The dictionary-based tokenizer identifies tokens based on language rules. See [Tokenizers](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-create-projectwks_tokenizer) for more details.
5. Optional: If you want to add project managers to the workspace, then expand the Advanced Options section, and select the names of people you want to add as project managers from the list. The administrator can add or remove project managers later by editing the workspace.

Only the names of people that you assigned to the project manager role from the User Account Management page for the instance are displayed. See [Assembling a team](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-team) for more information about adding users.

If you have a Lite plan subscription, skip this step. You cannot add other users, so you cannot assign anyone to the project manager role. You do not need a separate project manager.
Managing notification by using the Monitoring API 

You can manage notifications in a IBM Cloud Monitoring instance by using the Monitoring API.

To learn how to use cURL, see [cURL command](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curl).



 Fetch all user notifications 

You can use the following cURL command to get information about all the notification channels:

curl -X GET <REST_API_ENDPOINT>/api/notificationChannels?from=<START_TIMESTAMP>&to=<END_TIMESTAMP> -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "SysdigTeamID: $TEAM_ID" -H "content-type: application/json"

Where



* <REST_API_ENDPOINT>indicates the endpoint targetted by the REST API call. For more information, see [Monitoring REST API endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_rest_api). For example, the public endpoint for an instance that is available in us-south is the following: https://us-south.monitoring.cloud.ibm.com/api
* You can pass multiple headers by using -H.

Authorization and IBMInstanceID are headers that are required for authentication.

SysdigTeamID is optional. When you specify this header, you limit the request to the data and resources available for the team specified.

To get an AUTH_TOKEN and the GUID see, [Headers for IAM Tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curlmon-curl-headers-iam).
* to and from are query parameters that you must define to configure the period of time for which you want information on the notifications.



For more information about the response format, see [notification schema](https://cloud.ibm.com/docs/monitoring?topic=monitoring-notifications_apinotifications-api-parm-req-schema).





 Fetch specific user notification
For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a auditing instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).

KEY_ID
: ID value of the service key for which you want to get details.

KEY_NAME
: Name that you want to give the key. The maximum size of a name is 30 characters.





 Delete a key 

To delete an service key, run the following command.

curl -X DELETE "https://API_ENDPOINT/v1/config/keys/KEY_ID"
-H 'content-type: application/json' -H 'servicekey: SERVICE_KEY'

Where:

API_ENDPOINT
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

KEY_ID
: ID value of the service key to be deleted.

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a auditing instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).





 Rotating the service key by using the API
For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a logging instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).

KEY_ID
: ID value of the ingestion key for which you want to get details.

KEY_NAME
: Name that you want to give the key. The maximum size of a name is 30 characters.





 Delete a key 

To delete an ingestion key, run the following command.

curl -X DELETE "https://API_ENDPOINT/v1/config/keys/KEY_ID"
-H 'content-type: application/json' -H 'servicekey: SERVICE_KEY'

Where:

API_ENDPOINT
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

KEY_ID
: ID value of the ingestion key to be deleted.

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a logging instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).







 Rotating the ingestion key by using the API