vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"warnings": null,
"auth": null
}

A request to retrieve the metadata of a kv secret returns the following response:

{
"request_id": "0a0000e-0a0f-edfh-000a-ec2000ab00",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-9ca00000-f00d-000e-8b02-ed6b000pl",
"creation_date": "2022-01-25T19:22:04Z",
"crn": "crn:v1:bluemix:public:secrets-manager:eu-gb:a/4000000bbea00000000647f000001f5:5f000004-5f00-40000-8bfc-5mnh0a200000:secret:00000ea8e-7d00-00ce-c00poa-0a00000f0000e",
"description": "Extended description for my secret.",
"downloaded": true,
"id": "0a0000e-0a0f-edfh-000a-ec2000ab00",
"labels": [],
"last_update_date": "2022-01-25T19:22:04Z",
"name": "test-kv-secret",
"secret_type": "kv",
"state": 1,
"state_description": "Active",
"versions_total": 1
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to retrieve the metadata of a kv secret in an existing secret group returns the following response:

{
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:d7a2b83f-997c-4914-857a-86bfcdbf0873",
"description": "Extended description for my secret.",
"id": "d7a2b83f-997c-4914-857a-86bfcdbf0873",
"labels": [
"dev",
"us-south"
],
"last_update_date": "2020-12-16T22:05:16Z",
"name": "test-iam-credentials",
"secret_type": "iam_credentials",
"service_id": "ServiceId-43c79ec9-7f02-481d-92f1-e60363483298",
"state": 1,
"state_description": "Active",
"ttl": 1800
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to generate IAM credentials in an existing secret group returns the following response:

{
"request_id": "201eaa80-d5f1-2697-66dd-481d94a52685",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"access_groups": [
"AccessGroupId-0529f490-129c-4877-a2a0-b57f50d3e53b"
],
In this case, it's possible that an unauthenticated user might have a more powerful role than the authenticated alexone user.

It's important to understand that the nobody username is not a way of supplying a default set of permissions. Instead, the nobody username is used to determine permissions for unauthenticated users.



 Determining the role to assign 

First, determine the role or roles to assign to a user account or API key. It's best to assign a role with the least permissions necessary to do the tasks for that account or API key.

If the tasks are for a specific aspect, such as working with design documents or security settings, then assign a focused role, such as _design or _security.







 API keys 

The following section applies only to legacy credentials. For more information about using API keys with IAM credentials, see [IAM API keys](https://cloud.ibm.com/docs/account?topic=account-manapikey).

Use API keys to enable database access for a person or application, but without creating a new IBM Cloudant account for that person or application. An API key is a randomly generated username and password. The key is given the wanted access permissions for a database.

When a key is generated, and granted the required access permissions, the API key can be used in the same way as a normal user account.

However, API keys aren't the same as normal user accounts. An API key doesn't have access to the dashboard.

An API key is primarily used to enable applications to access a database, with a determined level of access control.

All IBM Cloudant instances that are deployed from the IBM Cloud® Public Germany region are deployed in EU-managed environments. Any IBM Cloudant account or API key that is generated outside an EU-managed environment can't be granted access to an EU-managed IBM Cloudant instance. For more information about IBM Cloudant in an EU-managed environment, see [Locations and tenancy](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publiclocations-and-tenancy).



 Creating API keys
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:34:53Z",
"id": "a7f55e6f-b068-977b-062e-4de644633982"
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to generate IAM credentials returns the following response:

{
"request_id": "c9716624-669f-2ef4-5560-a5d4e6618826",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"access_groups": [
"AccessGroupId-0529f490-129c-4877-a2a0-b57f50d3e53b"
],
"api_key": "U40hERZ0h-0C0cnka2bEuL2y...(redacted)",
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T21:55:31Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:d7a2b83f-997c-4914-857a-86bfcdbf0873",
"name": "test-kv-secret",
"secret_type": "kv",
"state": 1,
"state_description": "Active",
"versions_total": 1
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to retrieve the metadata of a kv secret in an existing secret group returns the following response:

{
"request_id": "0a0000e-0a0f-edfh-000a-ec2000ab00",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "id-0000000YC6X",
"creation_date": "2022-01-26T20:11:29Z",
"crn": "crn:v1:bluemix:public:secrets-manager:eu-gb:a/4000000bbea00000000647f000001f5:5f000004-5f00-40000-8bfc-5mnh0a200000:secret:00000ea8e-7d00-00ce-c00poa-0a00000f0000e",
"description": "Test secret in test secret group.",
"downloaded": true,
"id": "0a0000e-0a0f-edfh-000a-ec2000ab00",
"labels": [],
"last_update_date": "2022-01-26T20:11:29Z",
"name": "test-kv-secret-from-group",
"secret_group_id": "aded0a0000e-0a0f-edfh-000a-ec2000ab00",
"secret_type": "kv",
"state": 1,
"id": "2302-3744f199-6ccc-4698-8772-bb3937348c96",
"name": "zipfile-delude-slang-knoll",
"resource_type": "bare_metal_server_disk"
},
"cpu": {
"architecture": "amd64",
"core_count": 96,
"socket_count": 4,
"threads_per_core": 2
},
"created_at": "2021-03-12T09:29:17.000Z",
"crn": "crn:[...]",
"disks": [
{
"created_at": "2021-03-12T09:29:17.000Z",
"href": "https://us-south.iaas.cloud.ibm.com/v1/bare_metal_servers/2302-5e095b83-ceb4-49b5-9699-0aa5a2c996a4/disks/2302-3744f199-6ccc-4698-8772-bb3937348c96",
"id": "2302-3744f199-6ccc-4698-8772-bb3937348c96",
"interface_type": "sata",
"name": "zipfile-delude-slang-knoll",
"resource_type": "bare_metal_server_disk",
"size": 960
},
{
"created_at": "2021-03-12T09:29:17.000Z",
ibmcloud secrets-manager secret-metadata-update --id ID [--name NAME] [--description DESCRIPTION] [--labels LABELS] [--custom-metadata CUSTOM-METADATA] [--expiration-date EXPIRATION-DATE] [--ttl TTL] [--rotation ROTATION]



 Command options 

--id (string)
: The ID of the secret. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/.

--secret-metadata-patch (generic map)
: JSON Merge-Patch content for update_secret_metadata.

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

--name (string)
: A human-readable name to assign to your secret.

To protect your privacy, do not use personal data, such as your name or location, as a name for your secret.

The maximum length is 256 characters. The minimum length is 2 characters. The value must match regular expression /^[A-Za-z0-9](?:_-\.[A-Za-z0-9]+)$/.

--description (string)
: An extended description of your secret.

To protect your privacy, do not use personal data, such as your name or location, as a description for your secret group.

The maximum length is 1024 characters. The minimum length is 0 characters. The value must match regular expression /(.?)/.

--labels ([]string)
: Labels that you can use to search secrets in your instance. Only 30 labels can be created.

Label can be between 2-30 characters, including spaces.
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets/0cf4addb-7a90-410b-a3a7-a15bbe2b7909/versions/7bf3814d-58f8-4df8-9cbd-f6860e4ca973/locks?offset=50&limit=50"
},
"last" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets/0cf4addb-7a90-410b-a3a7-a15bbe2b7909/versions/7bf3814d-58f8-4df8-9cbd-f6860e4ca973/locks?offset=200&limit=50"
},
"limit" : 50,
"locks" : [ {
"attributes" : {
"key" : "value"
},
"created_at" : "2022-06-27T11:58:15Z",
"created_by" : "iam-ServiceId-e4a2f0a4-3c76-4bef-b1f2-fbeae11c0f21",
"description" : "lock for consumer 1.",
"name" : "lock-example-1",
"secret_group_id" : "d8371728-95c8-4c12-b2af-1af98adb9e41",
"secret_id" : "0cf4addb-7a90-410b-a3a7-a15bbe2b7909",
"secret_version_alias" : "current",
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets/0cf4addb-7a90-410b-a3a7-a15bbe2b7909/locks?offset=50&limit=50"
},
"limit" : 50,
"last" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets/0cf4addb-7a90-410b-a3a7-a15bbe2b7909/locks?offset=200&limit=50"
},
"locks" : [ {
"attributes" : {
"key" : "value"
},
"created_at" : "2022-06-27T11:58:15Z",
"created_by" : "iam-ServiceId-e4a2f0a4-3c76-4bef-b1f2-fbeae11c0f21",
"description" : "Lock for consumer 1.",
"name" : "lock-example-1",
"secret_group_id" : "d8371728-95c8-4c12-b2af-1af98adb9e41",
"secret_id" : "0cf4addb-7a90-410b-a3a7-a15bbe2b7909",
"secret_version_id" : "7bf3814d-58f8-4df8-9cbd-f6860e4ca973",
"secret_version_alias" : "current",
"updated_at" : "2022-10-05T21:33:11Z"
} ],
"secret_group_id": "9ab2250f-a369-4e07-ade7-d417d63ad587",
"secret_type": "IAM_CREDENTIALS",
"state": 1,
"state_description": "Active",
"ttl": 3600
},
{
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
"creation_date": "2020-10-09T17:05:21Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/791f5fb10986423e97aa8512f18b7e65:e415e570-f073-423a-abdc-55de9b58f54e:secret:a810998d-2912-4865-b4da-8dcc7465d784",
"description": "My test IAM credential.",
"id": "a810998d-2912-4865-b4da-8dcc7465d784",
"labels":
"test",
"us-south"
],
"last_update_date": "2020-10-09T17:05:21Z",
"name": "test-iam-credentials",
"secret_type": "IAM_CREDENTIALS",
"state": 1,
"state_description": "Active",
"ttl": 3600
}
],
"roles_total": 2
},
"warnings": null
}

If the role belongs to a secret group, the roles.data.secret_group_id value is included in the response to identify the secret group assignment.







 Read the metadata of a role
"description": "Reboot / Remote Console"
}
},
{
"id": 273,
"item": {
"description": "100 Mbps Public & Private Network Uplinks"
}
},
{
"id": 50367,
"item": {
"description": "250 GB Bandwidth"
}
},
{
"id": 21,
"item": {
"description": "1 IP Address"
}
},
{
"id": 55,
"item": {
"description": "Host Ping"
}
},
{
"id": 57,
"item": {
"description": "Email and Ticket"
}
},
{
"id": 58,
"item": {
"description": "Automated Notification"
}
},
{
"id": 420,
"item": {
"description": "Unlimited SSL VPN Users & 1 PPTP VPN User per account"
}
}
],
"quantity": 1,
"useHourlyPricing": false,
"virtualGuests":
{
"domain": "softlayer.local",
"hostname": "public-01-mex01"
}
],
"complexType": "SoftLayer_Container_Product_Order_Virtual_Guest"
}
]
}
Show more







 Upgrading public virtual servers 

Upgrading a public virtual server is done by using the SoftLayer_Product_Order/placeOrder API service.

Not applicable for transient virtual servers.
DevOps processes often require various types of credentials (such as usernames and passwords, API keys, service keys, and SSH keys) to interact with other systems to build, test, and deploy applications. You are responsible for ensuring that these credentials aren't inadvertently shared outside of their intended audience. Access to these credentials by malicious actors might disrupt your IT operations, cause unexpected costs, or use your resources to start attacks. IBM is not responsible for protecting and maintaining the security of your credentials.

To keep your credentials secure, make sure that you follow this guidance:



* Do not store credentials in Git repos. Depending on the repo settings, files within a repo might be visible to other members of your organization, other IBM Cloud users, or the public internet.
* Do not include user credentials in Delivery Pipeline definitions because they might be visible to other users. Specifically, do not place user credentials within Delivery Pipeline Classic job definition scripts, Delivery Pipeline Tekton yaml files, or scripts that are started by delivery pipelines.
* Do not publish user credentials in log files that are created when a pipeline runs because these files might be shared.
* Do not specify credentials in plain text in calls to Continuous Delivery APIs, such as when you configure [tool integrations](https://cloud.ibm.com/apidocs/toolchaincreate-tool), [Tekton pipeline environment properties](https://cloud.ibm.com/apidocs/tekton-pipelinecreate-tekton-pipeline-properties), or [Tekton pipeline trigger properties](https://cloud.ibm.com/apidocs/tekton-pipelinecreate-tekton-pipeline-trigger-properties).
* Do not specify credentials in plain text in Terraform configuration files, such as when you define tool integration resources, Tekton pipeline environment property resources, or Tekton pipeline trigger property resources. Instead, manage credentials in a secrets storage service and specify them by reference in API calls and Terraform configurations.
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y

Error from server (InternalError): Internal error occurred: unexpected response: 500

 Why it’s happening 

Some recent changes to the IAM user role have not yet been synchronized to the Red Hat OpenShift cluster.

 How to fix it 

Synchronize the IAM user information to the Red Hat OpenShift cluster. After the initial user synchronization is performed, further RBAC synchronization should occur automatically.

Before you begin:

[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).

To synchronize the IAM information for the user, you have 2 options:



* Log in to your cluster from the Red Hat OpenShift [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift).
* Set your command line context for the cluster by running the ibmcloud oc cluster config --cluster CLUSTER command.



If you use an API key for a functional ID or another user, make sure to log in as the correct user.

After the impacted user completes the IAM synchronization, the cluster administrator can verify the user exists in the cluster by listing users with the oc get users command.





 Missing projects or oc and kubectl commands fail 

Virtual Private Cloud

Classic infrastructure

 What’s happening 

You don't see all the projects that you have access to. When you try to run oc or kubectl commands, you see an error similar to the following.

No resources found.
Error from server (Forbidden): <resource> is forbidden: User "IAMuser@email.com" can't list <resources> at the cluster scope: no RBAC policy matched

 Why it’s happening 

You need to download the admin configuration files for your cluster to run commands that require the cluster-admin cluster role.

 How to fix it
"id": "363f6d70-0000-0001-0000-00000013b96c"
}
],
"name": "my-instance",
"placement_target": {
"id": "0787-8c2a09be-ee18-4af2-8ef4-6a6060732221"
},
"primary_network_interface": {
"name": "my-network-interface",
"subnet": {
"id": "bea6a632-5e13-42a4-b4b8-31dc877abfe4"
}
},
"profile": {
"name": "bx2-2x8"
},
"volume_attachments": [
{
"volume": {
"capacity": 1000,
"encryption_key": {
"crn": "crn:...]"
},
"name": "my-data-volume",
"profile": {
"name": "5iops-tier"
},
"user_tags": {
"env:test",
"env:prod"
}
}
}
],
"vpc": {
"id": "f0aae929-7047-46d1-92e1-9102b07a7f6f"
},
"zone": {
"name": "us-south-1"
}
}'

A successful response looks like this:

{
"bandwidth": 4000,
"boot_volume_attachment": {
"device": {
"id": "a8a15363-a6f7-4f01-af60-715e85b28141"
},
"id": "b7246cdf-892a-4a6c-8fa9-491a5f585bd0",
"created_on": "2019-09-11 13:46:51.68793557 +0000 UTC",
"modified_on": "2019-09-11 13:46:51.68793557 +0000 UTC",
"permitted_network": {
"vpc_crn": "crn:v1:staging:public:is:us-east:a/0821fa9f9ebcc7b7c9a0d6e9bf9442a4::vpc:b7246cdf-892a-4a6c-8fa9-491a5f585bd0"
},
"type": "vpc",
"state": "ACTIVE"
}







 Listing permitted networks 

List all permitted networks for your DNS zone.



 Request list permitted networks 

curl -X GET $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID/permitted_networks -H "Authorization: $TOKEN"





 Response list permitted networks 

{
"permitted_networks": [
{
"id": "b7246cdf-892a-4a6c-8fa9-491a5f585bd0",
"created_on": "2019-09-11 13:46:51.68793557 +0000 UTC",
"modified_on": "2019-09-11 13:46:51.68793557 +0000 UTC",
"permitted_network": {
"request_id": "201eaa80-d5f1-2697-66dd-481d94a52685",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"access_groups": [
"AccessGroupId-0529f490-129c-4877-a2a0-b57f50d3e53b"
],
"api_key": "CFQY6wWPI3C3wKx6XLC9p0c3e...(redacted)",
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T21:57:13Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:99425779-0707-4877-81CB-ca11e28b6ef1",
"description": "Extended description for my secret.",
"id": "99425779-0707-4877-81CB-ca11e28b6ef1",
"labels": [
"dev",
"us-south"
],
"last_update_date": "2020-12-16T22:07:20Z",
"name": "test-iam-credentials-in-group",
"secret_group_id": "714e070d-8122-6270-198c-fef9166729e3",
"secret_type": "iam_credentials",
{
"id": "fecd0173-3919-456b-b202-3029dfa1b0f7",
"created_on": "2019-01-01T05:20:00.12345Z",
"modified_on": "2019-01-01T05:20:00.12345Z",
"permitted_network": {
"vpc_crn": "crn:v1:bluemix:public:is:us-south:a/a8c46c094344a98ec1d8ef6ea19da410::vpc:r134-02681b2e-3c65-42c0-8ce4-b31da3fafcb"
},
"type": "vpc",
"state": "ACTIVE"
}
(https://cloud.ibm.com/docs/openshift?topic=openshift-access-credswhat-perms-api-key)
* [How do I limit which commands a user can run?](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credslimit-apikey-scopes)
* [What if I don't want to assign the API key owner or credentials owner the Super User infrastructure role?](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsnon-superuser)
* [What happens if the user who set up the API key for a region and resource group leaves the company?](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsapikey-user-leaves)
* [How can I lock down my cluster if my API key becomes compromised?](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsapikey-lockdown)



* [Ensuring that the API key or infrastructure credentials owner has the correct permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsowner_permissions)
* [Understanding access to the infrastructure portfolio](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsunderstand_infra)
* [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)
Private IPs 10.241.64.16, 10.241.64.17
Provision status active
Operating status online
Is public false
Listeners
Pools ID Name

Resource group ID Name
42c4f51adc3147b4b4049ad9826c30a1 Default

Created 2021-09-14T17:54:24.584-05:00
Security groups supported false

Take note of the first IP address listed in Private IPs. You require this when defining the custom routes.
5. Add a pool.

ibmcloud is load-balancer-pool-create example-pool r014-c7cadd8e-9e8b-4965-bee3-5d9ff95b3512 round_robin tcp 20 2 5 tcp  

Sample output:

Creating pool example-pool of load balancer r014-c7cadd8e-9e8b-4965-bee3-5d9ff95b3512 under account CNS Development Account - netsvs as user ibm@us.ibm.com

ID r014-474dca7d-aece-48a3-a636-fe8c3e654a3b
Name example-pool
Protocol tcp
Algorithm round_robin
Instance group ID Name
- -

Proxy protocol disabled
Health monitor Type Port Health monitor URL Delay Retries Timeout
tcp - 20 2 5

Session persistence Type Cookie name
- -

Members
Provision status active
Created 2021-09-14T18:03:56.274-05:00
6. Add a member.

ibmcloud is load-balancer-pool-member-create r014-c7cadd8e-9e8b-4965-bee3-5d9ff95b3512 r014-474dca7d-aece-48a3-a636-fe8c3e654a3b 200 0767_5545cfb3-febc-4f09-b9ea-0aeb66074edf
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/791f5fb10986423e97aa8512f18b7e65:e415e570-f073-423a-abdc-55de9b58f54e:secret:a6067f1c-98cf-9379-6188-a94a58222f5d",
"expiration_date": "2020-12-31T23:59:59Z",
"id": "a6067f1c-98cf-9379-6188-a94a58222f5d",
"labels": [
"label-1",
"label-2"
],
"last_update_date": "2020-10-05T21:52:29Z",
"name": "my-test-user-credential",
"secret_data": {
"password": "window-steel-dogs-coffee",
"username": "user123"
},
"secret_type": "USERNAME_PASSWORD",
"state": 1,
"state_description": "Active",
"versions": [
{
"auto_rotated": false,
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
"creation_date": "2020-10-05T21:52:29Z",
"id": "f53b8061-359e-3236-5bcc-fb120e170c87"
}
]
},
"warnings": null
}

The command to create an arbitrary secret returns the following output:

{
"crn": "crn:v1:bluemix:public:secrets-manager:eu-gb:a/4b85000004a6be3700000f5:5f1000-5f00-4000-8bfc-5e0000f66:secret:0000ea8e-7d00-69ce-c000a-0a00000b3ee",
"description": "Extended description for my secret.",
"downloaded": true,
"id": "00002ea8e-7lk90-00ce-c200a-00004b3ee",
"labels": [],
"last_update_date": "2022-01-25T19:22:04Z",
"name": "test-kv-secret",
"secret_data": {
"payload": {
"key1": "value1"
}
},
"secret_type": "kv",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-000000-f000d-479e-8b02-ed600000",
"creation_date": "2022-01-25T19:22:04Z",
"downloaded": true,
"id": "bf00007-800dc-0006-14d9-a7c720000bh",
"payload_available": true
}
],
"versions_total": 1
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to retrieve a key-value secret in an existing secret group returns the following response:

{
"request_id": "a0000c-e00-000ef-d000e8-a68e60000",
"lease_id": "",
"public_key": "ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQB/nAmOjTmezNUDKYvEeIRf2YnwM9/uUG1d0BYsc8/tRtx+RGi7N2lUbp728MXGwdnL9od4cItzky/zVdLZE2cycOa18xBK9cOWmcKS0A8FYBxEQWJ/q9YVUgZbFKfYGaGQxsER+A0w/fX8ALuk78ktP31K69LcQgxIsl7rNzxsoOQKJ/CIxOGMMxczYTiEoLvQhapFQMs3FL96didKr/QbrfB1WT6s3838SEaXfgZvLef1YB2xmfhbT9OXFE3FXvh2UPBfN+ffE7iiayQf/2XR+8j4N4bW30DiPtOQLGUrH1y5X/rpNZNlWW2+jGIxqZtgWg7lTy3mXy5x836Sj/6L"
}'

Save the ID of the SSH key in a variable, for example:

key="0738-35fb0489-7105-41b9-8764-033fae723006"





 Select a profile for your instance 

Call the API to list all profiles. The following command lists the profiles available.

curl -X GET "$vpc_api_endpoint/v1/instance/profiles?version=$api_version&generation=2" -H "Authorization:$iam_token"

Save the name of the profile in a variable, which will be used later to provision an instance. For example:

profile_name="b2-2x8"





 Select an image for your instance 

You can create an instance using a stock image, a custom image from your account, or an image that was shared with your account from a private catalog. Run one of the following API calls based on the image you plan to use.