vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Creating key: 'my-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
24203f96-b134-440e-981a-a24f2d432256 my-root-key





 Example 2 

Create a root key and show the JSON output.

 create a root key
$ ibmcloud kp key create my-root-key --output json

{
"id": "24203f96-b134-440e-981a-a24f2d432256",
"name": "my-root-key",
"type": "application/vnd.ibm.kms.key+json",
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:24203f96-b134-440e-981a-a24f2d432256"
}





 Example 3 

Create a root key from a base64-encoded value.

 create a random, base64-encoded, 32-byte key material
$ KEY_MATERIAL=$(openssl rand -base64 32)

 create a root key from a base64-encoded value
$ ibmcloud kp key create my-base64-root-key -k $KEY_MATERIAL

Creating key: 'my-base64-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
Create an instance of IBM Cloud Object Storage for the backing store of your ODF remote configuration. Then, create a set of HMAC credentials and a Kubernetes secret that uses your IBM Cloud Object Storage HMAC credentials.



1. Create an IBM Cloud Object Storage service instance.

ibmcloud resource service-instance-create noobaa-store cloud-object-storage standard global
2. Create HMAC credentials. Make a note of your credentials.

ibmcloud resource service-key-create cos-cred-rw Writer --instance-name noobaa-store --parameters '{"HMAC": true}'



Before you begin, review the [parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-remoteodf-remote-parameter-reference) for the template version that you want to use.







 Creating and assigning a configuration in the console 



1. [From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
7. If the Storage type that you selected requires secrets, enter them on the Secrets tab.
8. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
9. On the Assign to service tab, select the service that you want to assign your configuration to.
10. Click Complete to assign your storage configuration.







 Creating a configuration in the CLI 



1. Log in to the IBM Cloud CLI.

ibmcloud login
2. List your Satellite locations and note the Managed from column.

ibmcloud sat location ls
3. Target the Managed from region of your Satellite location. For example, for wdc target us-east.
"id": "a1fb6c4f-6a63-4d34-8bf6-55fab89e932a"
}
}
],
"name": "share-name1",
"profile": {
"name": "tier-5iops"
},
"user_tags": [],
"zone": {
"name": "us-south-1"
}
}'
Show more

This request creates a file share and mount target, specifying API version 2023-05-30 or later. The mount_targets property is specified in the example.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-05-30&generation=2&maturity=beta" -H "Authorization: Bearer $iam_token" -H 'Content-Type: application/json' -d '{
"size": 300,
"mount_targets": [
{
"name": "mount-target-2",
"vpc": {
"id": "d716af94-b1be-4705-9f70-a6771d622f7d"
}
}
],
"name": "share-name1",
"profile": {
"name": "tier-5iops"
},
"user_tags": [],
"zone": {
"name": "us-south-1"
}
}'
Show more





 Creating a mount target for an existing share 

The following examples compare how to create a mount target for an existing file share before and after the 2023-05-30 versioned change. The path of the API request is different before and after the change.

This request creates a target for an existing file share, specifying API version 2023-05-29 or earlier. The path of the API includes /targets.
ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-trident --template-version 21.04

Example command to create a version 22.04 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-trident --template-version 22.04

Example command to create a version 22.10 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-trident --template-version 22.10
6. Customize the command based on the settings that you want to use.
7. Run the command to create a configuration.
8. Verify your configuration was created.

ibmcloud sat storage config get --config CONFIG







 Creating a configuration in the API 



1. Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 21.04 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "netapp-trident", "storage-template-version": "21.04", "update-assignments": true}

Example request to create a version 22.04 configuration.
Values for creating a mount target.

 Field Value 

 Details 
 Mount target name Specify a mount target name. The name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. You can later edit the name if you want. 
 Zone Zone is inherited from the file share (for example, Dallas 2). 
 VPC Select an available VPC. The list includes only those VPCs with a subnet in the selected zone. 
 Subnet Select a subnet from the list. 
 Reserved IP address Required for the mount target. The IP address cannot be changed afterward. However, you can delete the mount target and create another one with a different IP address. 
 Reserving method You can have the file service select an IP address for you. The reserved IP becomes visible after the mount target is created. Or, specify your own IP. 
 Auto-release Releases the IP address when you delete the mount target. Enabled by default. 
 Security groups The security group for the VPC is selected by default, or select from the list. 
 Encryption in transit Disabled by default, click the toggle to enable. For more information about this feature, see [Encryption in transit - Securing mount connections between file share and host](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit). 



* If the share has VPC as the access mode, provide a name for the mount target and Select a VPC from the list.



5. Click Create.









 Create a file share from the CLI 



 Before you begin 



1. Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).
2. To use the CLI, set the IBMCLOUD_IS_FEATURE_FILESHARE environment variable to true. Copy the following code:
"id": "e6ff7b61-feb4-4c87-94aa-277d6f93e164",
"name": "vpc-name1",
"resource_type": "vpc"
}
}
],
"user_tags": [
"env:test",
"env:prod"
],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}





 Create a file share and mount target by specifying a subnet 

New

The following examople creates and attaches a [virtual network interface](https://cloud.ibm.com/docs/vpc?topic=vpc-vni-about) to your mount target that identifies the file share with a reserved IP address and applies the rules of the selected Security group. To create the mount target with the network interface, make a POST /shares request and specify a subnet. Specifying the subnet property is required when you're not using the [primary_ip property](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-createfs-create-file-share-pni-api) and specifying addressfor a reserved IP.

In this example, the mount target specifies a subnet ID. When the transit_encryption property set to user_managed, encryption in transit with an instance identity certificate is enabled. The default is none, which disables encryption in transit. The default access control mode is security_group, which is shown in the response.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-05-11&generation=2&maturity=beta" 
-H "Authorization: $iam_token" 
-d '{
"size": 10,
"name": "myshare-1",
.resourceGroupId({resource_group_id})
.build();
Response<ToolchainPost> response = toolchainService.createToolchain(createToolchainOptions).execute();
ToolchainPost toolchain = response.getResult();

const CdToolchainV2 = require('@ibm-cloud/continuous-delivery/cd-toolchain/v2');
const toolchainService = CdToolchainV2.newInstance();
...
(async() => {
const toolchainPrototypeModel = {
description: {toolchain_description},
name: {toolchain_name},
resourceGroupId: {resource_group_id}
};
const response = await toolchainService.createToolchain(toolchainPrototypeModel);
})();

from ibm_continuous_delivery.cd_toolchain_v2 import CdToolchainV2
...
toolchain_service = CdToolchainV2.new_instance()
toolchain = toolchain_service.create_toolchain(
description = {toolchain_description},
name = {toolchain_name},
resource_group_id = {resource_group_id}
)

import (
"github.com/IBM/continuous-delivery-go-sdk/cdtoolchainv2"
)
...
toolchainClientOptions := &cdtoolchainv2.CdToolchainV2Options{}
toolchainClient, err := cdtoolchainv2.NewCdToolchainV2UsingExternalConfig(toolchainClientOptions)
createToolchainOptions := toolchainClient.NewCreateToolchainOptions({toolchain_name}, {resource_group_id})
"id": "e6ff7b61-feb4-4c87-94aa-277d6f93e164",
"name": "vpc-name1",
"resource_type": "vpc"
}
}
],
"user_tags": [
"env:test",
"env:prod"
],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}





 Create a file share and mount target by specifying a subnet 

New

The following examople creates and attaches a [virtual network interface](https://cloud.ibm.com/docs/vpc?topic=vpc-vni-about) to your mount target that identifies the file share with a reserved IP address and applies the rules of the selected Security group. To create the mount target with the network interface, make a POST /shares request and specify a subnet. Specifying the subnet property is required when you're not using the [primary_ip property](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=uifs-create-file-share-pni-api) and specifying addressfor a reserved IP.

In this example, the mount target specifies a subnet ID. When the transit_encryption property set to user_managed, encryption in transit with an instance identity certificate is enabled. The default is none, which disables encryption in transit. The default access control mode is security_group, which is shown in the response.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-05-11&generation=2&maturity=beta" 
-H "Authorization: $iam_token" 
-d '{
"size": 10,
"name": "myshare-1",
ibmcloud kp key create new-imported-key --key-material "$ENCRYPTED_KEY" --encrypted-nonce "$ENCRYPTED_NONCE" --iv "$IV" --sha1 -o json > createRootKeyResponse.json

Behind the scenes, Hyper Protect Crypto Services receives your encrypted packet over a TLS 1.2 connection. Within a hardware security module, the system uses the private key to decrypt the symmetric key. Finally, the system uses the symmetric key and the IV to decrypt the nonce and verify the request. Your key is now stored in a tamper-resistant, FIPS 140-2 Level 4 validated hardware security module.



3. View details for the key.

jq '.' createRootKeyResponse.json

The following snippet shows an example output.

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.key+json",
"collectionTotal": 1
},
"resources": [
{
"id": "644cba65-e240-471f-8b84-14115447d2ae",
"type": "application/vnd.ibm.kms.key+json",
"name": "encrypted-root-key",
"state": 1,
"crn": "crn:v1:bluemix:public:hs-crypto:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:346d9f67-4bb2-481e-a3e1-3c2c646aa886:key:644cba65-e240-471f-8b84-14115447d2ae",
"extractable": false,
"imported": true
}
]
}
"mount_targets": [
{
"href": "$vpc_api_endpoint/v1/shares/r134-56f91d4a-2801-470a-b368-176bde64e954/mount_targets/r134-b8573e2c-60ee-4ecc-9eae-c52f890a8195",
"id": "r134-b8573e2c-60ee-4ecc-9eae-c52f890a8195",
"name": "sticky-idealist-spoiled-sloppily",
"resource_type": "share_target"
}
],
"user_tags": [],
"zone": {
"href": "https://us-south-genesis-dal-dev13-etcd.iaasdev.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}
Show more





 Creating a file share and mount target by specifying a primary network interface 

New

Make a POST /shares request and create a mount target with a primary network interface. Specify the primary_ip property and optional address subproperty, which reserves the IP address that you indicate. This address must not already be reserved on the subnet.

If you don't specify an address, an available address on the subnet is automatically selected. The default access control mode is security_group, which is displayed in the response.

By default, auto_delete for the primary IP is set to true. When you create a mount target with this option and later delete the target, the primary IP is also deleted. To release the primary IP when the mount target is deleted, set auto_delete to false. This example releases the primary IP.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-05-11&generation=2&maturity=beta"
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Creating dashboards ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Creating screens !
If MPIO isn't configured correctly, your storage device might disconnect and appear offline when a network outage occurs or when IBM Cloud® teams perform maintenance. MPIO ensures an extra level of connectivity during those events, and keeps an established session to the LUN with active read/write operations.

In the example,36001405b816e24fcab64fb88332a3fc9 is the WWID that is persistent while the volume exists. We recommend that your application uses the WWID. It's also possible to assign more easier-to-read names by using "user_friendly_names" or "alias" keywords in multipath.conf. For more information, see the [multipath.conf man page](https://linux.die.net/man/5/multipath.conf).
3. Check dmesg to make sure that the new disks are detected.

dmesg







 Step 7: Creating a partition and a file system (optional) 

After the volume is mounted and accessible on the host, you can create a file system. Follow these steps to create a file system on the newly mounted volume.



1. Create a partition.

$ sudo fdisk /dev/mapper/mpatha

Welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x92c0322a.

Command (m for help): p
Disk /dev/mapper/mpatha: 1 GiB, 1073741824 bytes, 2097152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x92c0322a

Command (m for help): n
Partition type
"auto_delete": "false"
}
},
"transit_encryption": {
"user_managed"
}
]
}'
Show more





 Create a mount target for an existing file share with the API 

This request creates or adds a mount target to an existing file share. In this example, the vpc property is specified because the file share's access control mode is vpc. Data encryption in transit is not enabled.

Access control modes must match when a mount target is created for an existing share. Both must be either vpc or security_group.

curl -X POST "$vpc_api_endpoint/v1/shares/$share_id/mount_targets?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: Bearer $iam_token" -H 'Content-Type: application/json' -d '{
"name": "mount-target-name1",
"vpc": {
"id": "6e01bc24-4a6e-4a0c-a1bd-4caa0c8159e7"
},
"transit_encryption": "none"
}'

A successful response looks like the following example.

{
"access_control_mode": "vpc",
"created_at": "2023-07-11T23:31:59Z",
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/ff859972-8c39-4528-91df-eb9160eae918/mount_targets/9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"id": "9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"lifecycle_state": "pending",
Enter a Name and Desription for the policy.
3. Click Save.

Your policy is saved in a Draft state and you can configure the policy details.



If you create a new policy by duplicating an existing policy, the new policy is displayed with the requirements and controls that are copied from the duplicated policy. If you create a policy without duplicating an existing policy, the requirements and controls are blank.

Zoom

![Example duplicated policy](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection/images/duplicated-policy.png)

Figure 1. An example of a duplicated policy





 Step 2. Add requirement groups 

Complete the following steps to create a requirement group:



1. Open your policy by [accessing the Posture Policies view](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-posture-policy-create-templateaccess-posture-controls) and clicking the policy that you want to update.
2. Click New Group.
3. Enter the requirement group name and description.
4. Click Save. The new group is displayed.
5. You can optionally create subgroups.



1. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/icons/action-menu-icon.svg) next to the requirement group where you want to create a subgroup.
2. Click New Subgroup.
3. Enter the subgroup name and description.
4. Click Save.









 Step 3. Add a requirement 

Complete the following steps to add a requirement:



1. Click the Actions icon !
"name": "EXAMPLE_VAULT_NAME",
"description": "API Test Vault description update.",
"created_on": "2022-03-07T09:39:17Z",
"updated_on": "2022-03-07T14:31:09Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/d0564770-1422-420c-945f-10803a2e24de"
},
{
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"description": "'Test Vault Name' description.",
"created_at": "2022-03-09T10:57:43Z",
"updated_at": "2022-03-09T10:57:43Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
}
]
}







 hpcs uko vault-create 

Create a vault in the instance with the specified name and description.

ibmcloud hpcs uko vault-create --name NAME [--description DESCRIPTION]



* Command options

--name (string)
: Required. A human-readable name to assign to your vault.
Any lines in the specified file that are empty or begin with are ignored. For this example, use a file that is named secrets_multi.txt, which contains the key-value pairs: sec1=mysec1, sec2=mysec2, and sec3=mysec3.

ibmcloud ce secret create --name mysecretmulti --from-env-file secrets_multi.txt



If you want to create (or update) a generic secret from a file, use the --from-file option with one of the following formats: --from-file FILE or --from-file KEY=FILE In Code Engine, when you use the --from-file option to specify secret values, all the contents within the file is the value for the key-value pair. When you use the option format of --from-file KEY=FILE, the KEY is name of the environment variable that is known to your job or app. When you use the option format of --from-file FILE, FILE is the name of the environment variable that is known to your job or app. If your file contains one or more key-value pairs, use the --from-env-file option to add an environment variable for each key-value pair in the specified file. Any lines in the specified file that are empty or begin with are ignored.

To display the details of the generic secret, myliteralsecret,

ibmcloud ce secret get --name myliteralsecret

Example output

Getting secret 'myliteralsecret'...
OK

Name: myliteralsecret
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Format: generic
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 66s
Created: 2023-03-07 21:06:34 +0000 UTC

Data:
---
TARGET: TXkgbGl0ZXJhbCBzZWNyZXQ=
A number of ways to create a blueprint configuration using the CLI.

For Schematics Blueprints, the [Schematics plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin) version must be greater than the 1.12.5.



1. Using a local file in JSON format.

Example

ibmcloud schematics blueprint create --file payload_complex.json
2. Using command-line arguments.

Example

ibmcloud schematics blueprint create --name bp-useast-basic1 --resource-group Default --bp-git-url https://github.com/Cloud-Schematics/blueprint-basic-example --bp-git-file basic-blueprint.yaml --bp-git-branch main --input-git-url https://github.com/Cloud-Schematics/blueprint-basic-example --input-git-file basic-input.yaml --input-git-branch main --inputs provision_rg=true,resource_group_name=bp-useast-rg1,cos_instance_name=bp-useast-cos1

The --inputs provision_rg=true,resource_group_name=bp-useast-rg1,cos_instance_name=bp-useast-cos1 overrides the values from GitHub config file.



* When you create a blueprint config in the us-south target region, why is the blueprint job ID indicating us-east?

The CLI uses geographic specific API endpoints which direct job requests to the first available region within a geography. us.schematics.cloud.ibm.com is called irrespective of the target us-south or us-east region and similarly, eu.schematics.cloud.ibm.com is called irrespective of the target eu-gb or eu-de region. Schematics dynamically determines which region to send the request based on region availability.