vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Activity Tracker hosted event search CLI 

The IBM Cloud® command-line interface (CLI) provides extra capabilities for service offerings. This information describes how you can use the CLI to list and export information for IBM Cloud Activity Tracker service instances for an account.

This information applies only if you use an IBM Cloud® Activity Tracker [hosted event search offering](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started-search).



 Prerequisites 



* Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
* Install the CLI by running the following command:

ibmcloud plugin install logging



You're notified on the command line when updates to the IBM Cloud CLI and plug-ins are available. Be sure to keep your CLI up to date so that you can use the latest commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.





 ibmcloud auditing service-instances 

Use this command to list the service instances for IBM Cloud Activity Tracker.

ibmcloud logging service-instances [OPTIONS]



 Command options 

--service-name <NAME> | --sn <NAME>
: Name of the service.

--region <NAME> | -r <NAME>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into or targeted will be used.

--all-regions
: Services hosted across all regions.

-g <GROUP>
: Resource Group associated with the hosted service.

--all-resource-groups
: Services hosted across all resource groups.

--quiet | -q
: Supresses verbose output.

--output <TYPE>
: A comma-separated list of output preferences enclosed in double-quotes ("). If only a single preference is specified, the double-quotes can be omitted. Supported options are WIDE and JSON.

If JSON is specified, output will be returned in JSON format.
ibmcloud sat subscription identity set --subscription SUBSCRIPTION [-f] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Subscription resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--subscription SUBSCRIPTION
: Required. The name or ID of your subscription. To list subscriptions in your IBM Cloud account, run ibmcloud sat subscription ls.

-f
: Optional. Force the command to run with no user prompts.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat subscription identity set --subscription my_subscription







 ibmcloud sat subscription ls 

List the subscriptions to Satellite configurations in your IBM Cloud account.

ibmcloud sat subscription ls [--cluster CLUSTER] [--output JSON] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Subscription resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--cluster, -c CLUSTER
: Optional. The name or ID of the cluster that you want to list subscriptions from. To list registered clusters, run ibmcloud sat cluster ls.

--output JSON
: Optional. Displays the command output in JSON format.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat subscription ls







 ibmcloud sat subscription rm 

Remove a subscription.

The Kubernetes resources for the subscription, such as pods and services, are deleted from all your subscribed clusters that are registered in Satellite. Before you remove a subscription, make sure that you do not need these resources.
If you select Specific resources, you can establish trust with one or more existing compute resource instances directly without conditions. For example, a Kubernetes cluster.



5. Click Continue.
6. (Optional) [Assign access to the trusted profile](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profiletp-access).
7. Or, click Create without assigning any access.



For more information about the fields that are used to create conditions for trusted profiles, see [IAM condition properties](https://cloud.ibm.com/docs/account?topic=account-iam-condition-properties).





 Establishing trust with IBM Cloud services in the console 

An IBM Cloud service in your account or another account might need a token to run an operation in your account.

For example, a Project service instance can assume a trusted profile to securely deploy an architecture in your account or another account without the need for key rotation. For more information, see [Using trusted profiles to authorize a project to deploy an architecture](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-tp-project).

Complete the following steps to define how an IBM Cloud service can access specific resources in your account:



1. Ask the administrator of the service for the Cloud Resource Name (CRN) that uniquely identifies the service instance. The CRN is used to authorize operations.



* The service administrator can find the CRN by going to the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/icon_hamburger.svg) > Resource list and clicking the name of the service that you're targeting. In the Details section, copy the CRN.



2. In the IBM Cloud console, click Manage > Access (IAM), and select Trusted profiles.
3. Click Create profile.
4. Define your profile by providing a name and a description, and click Continue.
Create the service key that connects to the instance [ibmcloud resource service-key-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_key_create)

ibmcloud resource service-key-create NAME ROLE_NAME --instance-name SERVICE_INSTANCE_NAME

Where

NAME is the name of your new service key

ROLE_NAME is either Administrator, Manager, Writer, or Reader

SERVICE_INSTANCE_NAME is the name of the instance you created

This will gain you access to the instance's access key.
You can generate a new set of credentials for cases where you want to manually [connect an app](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-ibmcloud-app) or [external consumer](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-external-app) to an IBM Cloud service. [Learn more](https://cloud.ibm.com/docs/account?topic=account-service_credentials).





 Connections 

Shows connected resources. You can use the Create connection button to bind this service to another resource.





 View docs 

The View docs link from the Actions drop list opens the main documentation page for Databases for PostgreSQL in a new tab.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 IBM Cloud® CLI ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/checkmark-icon.svg) 
 API call 







 Next steps 

For more information about using IAM access tokens, see the following topics:



* [Invoking IBM Cloud service APIs](https://cloud.ibm.com/docs/account?topic=account-iamapikeysforservices)
* [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey)
Searching and managing the IBM Cloud catalog (ibmcloud catalog) 

Use the following commands from the IBM Cloud® Command Line Interface to manage the IBM Cloud catalog entries, query templates, runtimes, and geolocations of data centers.

There are extra CLI commands and capabilities for catalogs. You can use the Catalogs management CLI plug-in to manage your private catalogs and onboard new private software. For more information, see [Catalogs management CLI plug-in](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugin).



 ibmcloud catalog entry 

Get a catalog entry:

ibmcloud catalog entry ID [--children] [--global]



 Command options 

--children
: Get all children for the catalog entry

--global
: Operate in global scope





 Examples 

Get entry with ID a0ef1-d3b4j0:

ibmcloud catalog entry 'a0ef1-d3b4j0'







 ibmcloud catalog entry-create 

Create a catalog entry (catalog admin of an account only):

ibmcloud catalog entry-create [-c PARAMETERS_AS_JSON] [-p, --parent PARENT] [--global]



 Command options 

-p, --parent
: Parent ID of the object

-c
: Valid JSON object that contains catalog-specific configuration parameters, provided either inline or in a file. For a list of supported configuration parameters, see documentation for the particular catalog entry.

--global
: Operate in global scope





 Examples 

Create resource from JSON file with parent ID a0ef1-d3b4j0:

ibmcloud catalog entry-create -c @entry.json -p 'a0ef1-d3b4j0'







 ibmcloud catalog entry-update 

Update an existing catalog entry (catalog admin or editor of an account only):

ibmcloud catalog entry-update ID [-c PARAMETERS_AS_JSON] [--global]



 Command options 

-c
ibmcloud iam trusted-profile-create my-profile -d "sample trusted profile"

For more information, see the [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_trusted_profile_create).
3. To create conditions for your trusted profile, run the ibmcloud iam trusted-profile-rule-create command:

ibmcloud iam trusted-profile-rule-create my-profile --name my-rule --type Profile-SAML --conditions claim:cn,operator:EQUALS,value:my_user --realm-name https://w3id.sso.ibm.com/auth/sps/samlidp2/saml20 --expiration 1200

For more information, see the [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_trusted_profile_rule_create).
4. Create an access policy with the Viewer role for all resources in the account by running the following command:

ibmcloud iam trusted-profile-policy-create --roles Viewer

For more information, see the [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_trusted_profile_policy_create).







 Establishing trust with compute resources by using the CLI 

Complete the following steps to set up better control over granting access to compute resources.

IBM Cloud Kubernetes Service supports only trusted profiles for versions 1.21 and newer. Free IBM Cloud Kubernetes Service clusters create only earlier versions. You have the choice to create clusters with an earlier version with the standard plan, so be sure to select version 1.21 or newer.



1. Create a trusted profile by running the following command:

ibmcloud iam trusted-profile-create sample-compute-profile -d "sample trusted profile for compute resources"
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --default-trusted-profile Profile-c9fe8182-870a-49df-8308-c8bb7394c4c3 --default-trusted-profile-auto-link true Create instance with default trusted profile
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --host-failure-policy restart Create instance with availability policy on host failure
* ibmcloud is instance-create my-instance-name my-vpc us-south-1 bx2-2x8 my-subnet --image ibm-ubuntu-20-04-2-minimal-amd64-1 --volume-attach '[{"volume": {"name":"my-vol-1"}}]' Create instance with existing volume in volume attachment by using resource name.
* ibmcloud is instance-create my-instance-name my-vpc us-south-1 mx2-2x16 my-subnet --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --dedicated-host my-dedicated-host Create instance to be placed in the wanted dedicated host by using resource name.
If you use a federated ID, you can choose one of the following options for creating an IAM token:



* Generate an IBM Cloud API key: IBM Cloud API keys are dependent on the IBM Cloud account they are generated for. You cannot combine your IBM Cloud API key with a different account ID in the same IAM token. To access clusters that were created with an account other than the one your IBM Cloud API key is based on, you must log in to the account to generate a new API key.
* Use a one-time passcode: If you authenticate with IBM Cloud by using a one-time passcode, you cannot fully automate the creation of your IAM token because the retrieval of your one-time passcode requires a manual interaction with your web browser. To fully automate the creation of your IAM token, you must create an IBM Cloud API key instead.



When you create your access token, the body information that is included in your request varies based on the IBM Cloud authentication method that you use. Replace the following values:



* <my_username> = Your IBM Cloud user name.
* <my_password> = Your IBM Cloud password.
* <my_api_key> = Your IBM Cloud API key.
* <my_passcode> = Your IBM Cloud one-time passcode. Run bx login --sso and follow the instructions in your CLI output to retrieve your one-time passcode by using your web browser.



Example: POST https://iam.<region>.cloud.ibm.com/identity/token

To specify an IBM Cloud region, review the region abbreviations that are used in the API endpoints. See [IBM Cloud region API endpoints ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://cloud.ibm.com/docs/containers/cs_regions.htmlbluemix_regions) for more information.



 Input parameter Values
Follow these steps to prepare for running the command.

Gather the following required instance template details.



Table 1. Required instance template details

 Instance template details Listing command 

 VPC ibmcloud is vpcs 
 Zone ibmcloud is zones 
 Profile ibmcloud is instance-profiles 
 Subnet ibmcloud is subnets 
 Image ibmcloud is images 



Use the following commands to determine the required information for creating a new instance template.



1. List the IBM Cloud VPCs that are associated with your account.

ibmcloud is vpcs

For this example, you see a response similar to the following output:

ID Name Default Status Tags
0738-xxx1xx23-4xx5-6789-12x3-456xx7xx123x my-vpc yes available -
0738-xxxx1234-5678-9x12-x34x-567x8912x3xx my-other-vpc no available -

If you don't have one available, you can create an IBM Cloud VPC by using the ibmcloud is vpc-create command. For more information about creating an IBM Cloud VPC, see [IBM Cloud VPC CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencevpcs).
2. List the regions that are associated with your account.

ibmcloud is regions

For this example, you see a response similar to the following output:

Name Endpoint Status
us-south /v1/regions/us-south available
3. List the zones associated with the region.

ibmcloud is zones us-south

For this example, you see a response similar to the following output:

Name Region Status
us-south-1 us-south available
us-south-3 us-south available
4. List the available profiles for creating your instance template.

ibmcloud is instance-profiles

For this example, you see a response similar to the following output:
ibmcloud tg connection-create|cc GATEWAY_ID --name NAME --network-type [vpc | directlink | classic] --network-id NETWORK_ID --network-account-id NETWORK-ACCOUNT-ID [--output json] [-h, --help]

Where:



* GATEWAY_ID: ID of the gateway that the new connection will be on.
* --name: Name for the new connection.
* --network-type: Network type of the connection. Values are vpc, directlink, or classic.
* --network-id: ID of the network connection. For classic, do not set a value. For vpc and directlink, use the CRN. To find the CRN of a VPC:

ibmcloud is vpc VPC_ID --json
* --network-account-id: ID of the IBM Cloud account to use for creating a classic connection. Only used with 'classic' type, when the account of connection is different than the gateway's account.
* --output json: Optional: Specify if you want the output to display in JSON format.
* --help | -h: Optional: Get help on this command.





 Examples 

This example illustrates creating a VPC connection named vpc-connection using vpcCRN="crn:v1:bluemix:public:is:us-south:a/3aa0a9999a1a46258064d84f7f447920::vpc:r134-f87014d5-87d2-46d1-9999-24683082f6bc":

ibmcloud tg cc $gateway --name vpc-connection --network-id $vpcCRN --network-type vpc

Create Classic connection named classic-conn.

ibmcloud tg cc $gateway --name classic-conn --network-type classic









 Adding a connection with the API 

To add a connection with the API, follow these steps:



1.
curl -X POST 'https://iam.cloud.ibm.com/v1/profiles/PROFILE_ID/rules' -H 'Authorization: Bearer TOKEN' -H 'Content-Type: application/json' -H 'Accept: application/json' -d '{
"type": "Profile-CR",
"conditions": [
{
"claim": "namespace",
"operator": "EQUALS",
"value": ""default123""
}
]
}'

There is a limit of 20 claim rules per trusted profile.

Create a direct link
: You can establish a direct link with specific, existing resources.

curl -X POST 'https://iam.cloud.ibm.com/v1/profiles/PROFILE_ID/links' -H 'Authorization: Bearer TOKEN' -H 'Content-Type: application/json' -H 'Accept: application/json' -d '{
"name": "my link",
"cr_type": "VSI",
"link": {
"crn": "crn:v1:bluemix:public:iam-identity::a/18e3020749ce4744b0b472466d61fdb4::computeresource:Fake-Compute-Resource",
"namespace": "default",
"name": "my compute resource name"
}
}'
3. Create an access policy. For more information, see [IAM Policy Management API?](https://cloud.ibm.com/apidocs/iam-policy-management).

curl -X POST 'https://iam.cloud.ibm.com/v1/policies' -H 'Authorization: Bearer $TOKEN' -H 'Content-Type: application/json' -d '{
"type": "access",
"description": "Editor role for SERVICE_NAME's RESOURCE_NAME",
"subjects": [
{
"attributes":
{
* [Setting up user access](https://cloud.ibm.com/docs/account?topic=account-access-getstarted)
* [Inviting users to an account](https://cloud.ibm.com/docs/account?topic=account-iamuserinv)
* [Locating an IAM account administrator](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iam_verify_permissions)
* [Managing IAM access for VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iam)
ibmcloud resource service-key crn:v1:bluemix:public:cloudantnosqldb:us-south:a/537860630a5ba7115be954e8d5aa5689:cc2a6d6c-8f5e-4038-b975-b09b51d1d8dc:resource-key:9057f12e-fbf5-421d-8865-764422217a79







 ibmcloud resource service-key-create 

Create a service key.

ibmcloud resource service-key-create NAME [ROLE_NAME] ( --instance-id SERVICE_INSTANCE_ID | --instance-name SERVICE_INSTANCE_NAME | --alias-id SERVICE_ALIAS_ID | --alias-name SERVICE_ALIAS_NAME) [--service-id SERVICE_ID] [-p, --parameters @JSON_FILE | JSON_TEXT] [-g RESOURCE_GROUP] [--service-endpoint SERVICE_ENDPOINT_TYPE] [-f, --force] [-f, --force] [-q, --quiet]



 Command options 

NAME (required)
: Name of the key.

ROLE_NAME (optional)
: Name of the IAM service role. The specified role cannot be one of the default platform roles. You can verify eligibility of any role for use with this option by running ibmcloud iam roles --service <your-service> and checking that serviceRole appears in the role's CRN.

--instance-id SERVICE_INSTANCE_ID
: Service instance ID.

--instance-name SERVICE_INSTANCE_NAME
: Service instance name.

--alias-id SERVICE_ALIAS_ID
: Service alias ID.

--alias-name SERVICE_ALIAS_NAME
: Service alias name.

--service-id SERVICE_ID
: Name or UUID of the service ID, which the role belongs to.

-p, --parameters @JSON_FILE | JSON_TEXT
: Parameters JSON file or JSON string.

-g RESOURCE_GROUP
For more information, see [IAM Policy Management API?](https://cloud.ibm.com/apidocs/iam-policy-management).

curl -X POST 'https://iam.cloud.ibm.com/v1/policies' -H 'Authorization: Bearer $TOKEN' -H 'Content-Type: application/json' -d '{
"type": "access",
"description": "Editor role for SERVICE_NAME's RESOURCE_NAME",
"subjects": [
{
"attributes":
{
"name": "iam_id",
"value": "IBMid-123453user"
}
]
}'
],
"roles":[
{
"role_id": "crn:v1:bluemix:public:iam::::role:Editor"
}
],
"resources":[
{
"attributes":
{
"name": "accountId",
"value": "$ACCOUNT_ID"
},
{
"name": "serviceName",
"value": "$SERVICE_NAME"
},
{
"name": "resource",
"value": "$RESOURCE_NAME",
"operator": "stringEquals"
}
]
}
]
}'







 Establishing trust with compute resources with the API 

Complete the following steps to set up better control over granting access to compute resources.

IBM Cloud Kubernetes Service supports only trusted profiles for versions 1.21 and newer. Free IBM Cloud Kubernetes Service clusters create only earlier versions. You have the choice to create clusters with an earlier version with the standard plan, so be sure to select version 1.21 or newer.



1. Create a trusted profile by specifying your account ID.
Navigating to devices 

Use the [IBM Cloud console](https://cloud.ibm.com/docs/email-delivery?topic=virtual-servers-navigating-devicesusing-console) to locate your existing IBM Cloud® devices or provision new ones.



  Using the IBM Cloud console to go to your devices 

The following steps use the IBM Cloud console to go to your devices. For more information about working with the console, see [Navigating the IBM Cloud console](https://cloud.ibm.com/docs/overview?topic=overview-uiui).



1.  Log in to the [IBM Cloud console](https://cloud.ibm.com/) by using your unique credentials.
2.  From the Dashboard, click the menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Classic Infrastructure > Devices.







  Next steps 

Select the applicable management tasks to work with your virtual server instances.
curl http://$appname-orders.mybluemix.net/orders

{"content":[{"id":1,"customerUID":1,"date":"30-05-2018","items":{"id":1,"productUID":4,"quantity":1,"price":30.00},{"id":2,"productUID":3,"quantity":1,"price":50.00},{"id":3,"productUID":5,"quantity":1,"price":200.00},{"id":4,"productUID":1,"quantity":4,"price":5.00},{"id":5,"productUID":2,"quantity":1,"price":60.00},{"id":6,"productUID":6,"quantity":1,"price":20.00}]},{"id":2,"customerUID":2,"date":"12-04-2018","items":{"id":7,"productUID":3,"quantity":1,"price":45.00},{"id":8,"productUID":6,"quantity"
<br><br> * rate_limit_mb_per_member - Auto scaling rate limit in megabytes per member.-> [Scale up by rate_increase_percent<br><br><br> 
 <br><br> * rate_period_seconds - Auto scaling rate period in seconds. -> [Scale up by rate_increase_percent every rate_period_seconds]<br><br><br> 
 <br><br> * rate_units - Auto scaling rate in units<br><br><br> 
 Nested scheme for memory: 
 <br><br> * io_above_percent - Auto scaling scalar I/O utilization above percent. -> [Average IO utilization]<br><br><br> 
 <br><br> * io_enabled- Auto scaling scalar I/O utilization enabled.<br><br><br> 
 <br><br> * io_over_period - Auto scaling scalar I/O utilization over period. ->[Average IO utilization for this period]<br><br><br> 
 <br><br> * rate_increase_percent - Auto scaling rate in increase percent. -> [Scale up by rate_increase_percent]<br><br><br> 
 <br><br> * rate_limit_mb_per_member - Auto scaling rate limit in megabytes per member. [Scale up by rate_increase_percent every rate_period_seconds up to rate_limit_mb_per_member]<br><br><br> 
 <br><br> * rate_period_seconds - Auto scaling rate period in seconds. -> [Scale up by rate_increase_percent every<br><br><br> 
 <br><br> * rate_units - Auto scaling rate in units.<br><br><br> 
 tags A list of tags that you want to add to your instance. 
 whitelist A list of allowed IP addresses for the database. Multiple blocks are allowed.Nested scheme for whitelist: