vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Show more





 JSON response 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Bad Request: The key expired on 2020-08-14 19:33:47 +0000 UTC: Key could not be restored. Please see reasons for more details.",
"reasons":
{
"code": "KEY_EXPIRED_ERR",
"message": "The action could not be performed on the key because the key is expired.",
"status": 400,
"moreInfo": "https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}











 22 - The encrypted nonce given does not match... 



 Message 

The encrypted nonce given does not match existing record: Please ensure the correct nonce was given in the request

Reason code: INCORRECT_NONCE_ERR





 HTTP status code 

400 - Bad Request

The HTTP 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

The client should not repeat this request without modification.





 Context 

This error message is applicable to the restore and rotate key interfaces.

This example is based on the restore key command and it uses the [CLI](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-protect-cli-reference) because the output is easier to follow than the [API](https://cloud.ibm.com/apidocs/key-protect).

Step 1 - setup the problem by creating a root key using an import token and then delete the key

 create an import token that expires in 15 minutes (900 seconds) and allows 10 retrievals
Step 4: Remove resources 



1. Change to the terraform/roles/development directory
2. Destroy the access groups and access policies

terraform destroy -var-file=../../credentials.tfvars -var-file=development.tfvars
3. Change to the terraform/per-environment folder of the checkout
4. Activate the development workspace

terraform workspace select development
5. Destroy the resource group, spaces, services, clusters

terraform destroy -var-file=../credentials.tfvars -var-file=development.tfvars

terraform destroy only removes the terraform state information related to a resource group as a resource group cannot be deleted by a user.
6. Repeat the steps for the testing and production workspaces
7. If you created it, destroy the organization. Change to the terraform/global directory.

terraform destroy -var-file=../credentials.tfvars



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content 



* [Tutorial with Terraform: PHP web application on a LAMP Stack in VPC](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-lamp-stack-on-vpc)
* [Getting started with Terraform on IBM Cloud](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started)
* [Examples using IBM Cloud Provider for Terraform](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples)
"activity_tracking": ],
"archive_rule": ],
"expire_rule": ],
"metrics_monitoring": ],
"retention_rule": ]
}
}
],
"address": "module.instance_config"
}
]
}
},
"resource_changes": [
{
"address": "module.instance.ibm_resource_instance.cos_instance",
"module_address": "module.instance",
"mode": "managed",
"type": "ibm_resource_instance",
"name": "cos_instance",
"provider_name": "registry.terraform.io/ibm-cloud/ibm",
"change": {
"actions":
"create"
],
"before": null,
"after": {
"location": "global",
"parameters": null,
"plan": "lite",
"service": "cloud-object-storage",
"timeouts": null
},
"after_unknown": {
"account_id": true,
"allow_cleanup": true,
"created_at": true,
"created_by": true,
"crn": true,
"dashboard_url": true,
"deleted_at": true,
"deleted_by": true,
"extensions": true,
"guid": true,
"id": true,
"last_operation": true,
"locked": true,
"name": true,
"plan_history": true,
"resource_aliases_url": true,
"resource_bindings_url": true,
"resource_controller_url": true,
"resource_crn": true,
"resource_group_crn": true,
It is also possible to manage resources using the [IBM Cloud® Platform CLI](https://cloud.ibm.com/docs/account?topic=account-manage_resource):

ibmcloud resource service-instance-create <instance-name> cloud-object-storage <plan> global





 Deleting a service instance 

When a service instance is deleted, the data is not deleted immediately. Instead, it is scheduled for reclamation (by default this is set to take 7 days), after which the data is irreversibly destroyed, and the bucket names will be made available for reuse. It is also possible to [restore a deleted resource](https://cloud.ibm.com/docs/account?topic=account-resource-reclamationrestore-resource) that has not yet been reclaimed.

It is possible to check the status of a reclamation, as well as force or cancel a scheduled reclamation using the [the IBM Cloud® Platform CLI](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_reclamations).

It is not possible to delete a Service Instance if there is a bucket with an active Immutable Object Storage policy or legal hold on any objects. The policy will need to expire before the data can be deleted. It isn't possible to delete a Service Instance if there is a permanent retention policy in place.

Currently, the reclamation can be scheduled for IBM Cloud Object Storage standard plan instances only.
"role_id": "crn:v1:bluemix:public:iam::::role:Operator"
}
]
}
},
"resource": {
"attributes": [
{
"operator": "stringEquals",
"value": "d4b763ad0cbd4dca8dd1edb427d7a77e",
"key": "accountId"
},
{
"value": "platform_service",
"operator": "stringEquals",
"key": "serviceType"
}
]
},
"pattern": "time-based-conditions:once",
"rule": {
"operator": "and",
"conditions": [
{
"key": "{{environment.attributes.current_date_time}}",
"operator": "dateTimeGreaterThanOrEquals",
"value": "2022-12-23T00:00:00+00:00"
},
{
"key": "{{environment.attributes.current_date_time}}",
"operator": "dateTimeLessThanOrEquals",
"value": "2022-12-23T23:59:59+00:00"
}
]
},
"subject": {
"attributes": [
{
"key": "iam_id",
"operator": "stringEquals",
"value": "IBMid-550000HFVV"
}
]
}
}



Temporary policies, which use the pattern time-based-conditions:once, aren't automatically removed when they expire. To avoid reaching the policy limit in the account, administrators can remove the policy manually after it expires.
curl -X DELETE https://resource-controller.cloud.ibm.com/v2/resource_aliases/267bf377-7fa2-43f6-94ec-09103a8e89d4 -H 'Authorization: Bearer <IAM_TOKEN>'

DeleteResourceAliasOptions deleteResourceAliasOptions = new DeleteResourceAliasOptions.Builder()
.id(aliasGuid)
.build();

Response<Void> response = service.deleteResourceAlias(deleteResourceAliasOptions).execute();

System.out.printf("deleteResourceAlias() response status code: %dn", response.getStatusCode());

response = resource_controller_service.delete_resource_alias(
id=alias_guid
)
print('ndelete_resource_alias() response status code: ',
response.get_status_code())

deleteResourceAliasOptions := resourceControllerService.NewDeleteResourceAliasOptions(
aliasGUID,
)

response, err := resourceControllerService.DeleteResourceAlias(deleteResourceAliasOptions)
if err != nil {
panic(err)
}
fmt.Printf("nDeleteResourceAlias() response status code: %dn", response.StatusCode)

const params = {
id: aliasGuid,
};

resourceControllerService.deleteResourceAlias(params)
.then(res => {
console.log('deleteResourceAlias() response status code: ' + res.status);
})
.catch(err => {
console.warn(err)
});
Why do I still see results if I've deleted a resource? 

Results for a resource that you no longer have are still available in the Security and Compliance Center UI.

  What’s happening 

You've deleted a resource from your account, but you are still able to view the results for it from previous evaluations.

  Why it’s happening 

Results are a point in time statement of your compliance with a specific group of controls. Results are not overwritten. As new evaluations are conducted, new results are provided. In your historical results, the deleted resource continues to display.

  How to fix it 

If you don't want to view results for a specific resource, you can remove the scans from your storage.
For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Managing Entrust DataControl](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managing-entrust-dc)
* [Contacting IBM® Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
* [FAQ](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
* [Entrust website](https://www.entrust.com/)
Because of this fact, it is recommended to poll the resources you're deleting, to check for deletion before proceeding.

It can take several minutes for resources to be deleted from the system, due to these asynchronous operations. To facilitate deletion, the best practice is to do things in this order:



1. Delete your instances
2. Delete your public gateways
3. Delete your subnets
4. Delete your VPCs



For more information, see [Deleting a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-deleting).





 Trace ID is blank 

Usually, when the Trace ID is blank, it is because the JSON returned doesn't match what is expected from the API. Try running the command RIAAS_DEBUG=yes ibmcloud is server-rm 3fb7c1eb-45fd-4c85-962e-617f216e7393 (substitute your correct server ID token) and check the output.





 VPC public gateway drops connection 

 What’s happening 

The TCP connection between the IKS cluster and back-end database is dropped by the VPC public gateway during the TCP idle time (for example, 5 minutes).

 Why it’s happening 

The VPC public gateway has a fixed 4-minute timeout for TCP connections, and it is not configurable. This problem occurs because the Linux default timeout for idle time is 2 hours (only if connection is idle for 2 hours, TCP keep-alive packets are being sent).

 How to fix it 

Set the idle time to less than 4 minutes (for example, 180 seconds).
Can I move service instances between resource groups? 

You can't move service instances between resource groups. If you assign a service instance incorrectly, you must delete and recreate the instance to assign it to another resource group.





 How do I delete a service from my account? 

You can delete a service instance by using the following steps:



1. From your dashboard in the IBM Cloud console, click View resources within the Resources summary widget.
2. Expand the sections to locate the service instance that you want to delete.
3. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Delete for the row.







 Can I view usage per resource group? 

Yes, you can. To access your usage dashboard, go to Manage > Billing and usage in the IBM Cloud console. Select Usage to view a summary of the usage by resource group for the account.





 Who can attach tags to a resource? 

Any user assigned the correct access for the specific type of resource can attach tags. When a resource is tagged, it is visible to all users who have read access to the resource. However, to attach or detach a tag on a resource, certain access roles or permissions are required depending on the resource type and the tag type. For example, to attach user tags to any of the resources that are managed by using IAM, you must be assigned the Editor or Administrator role on the resource.

You can attach access management tags to IAM-enabled resources only.

For more information about the required access for other resources types, see [Tagging permissions](https://cloud.ibm.com/docs/account?topic=account-accesstagging-permissions).





 Where can I find my resources in the IBM Cloud console? 

To view all of your resources, select from the following options:



* Click the Navigation menu icon !
description='This is an updated description'
).get_result()

print(json.dumps(service_id, indent=2))

updateServiceIDOptions := iamIdentityService.NewUpdateServiceIDOptions(svcID, svcIDEtag)
updateServiceIDOptions.SetDescription("This is an updated description")

serviceID, response, err := iamIdentityService.UpdateServiceID(updateServiceIDOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(serviceID, "", " ")
fmt.Println(string(b))

const params = {
id: svcId,
ifMatch: svcIdEtag,
description: 'This is an updated description',
};

iamIdentityService.updateServiceId(params)
.then(res => {
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err);
});

For more information, see the [IAM Identity Services API](https://cloud.ibm.com/apidocs/iam-identity-token-apiupdate-service-id).





 Deleting a service ID in the console 

To delete a service ID, complete the following steps:



1. In the IBM Cloud console, go to Manage > Access (IAM), and select Service IDs.
2. Identify the row of the service ID that you want to remove, and click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Remove.
3.
If you want to delete service instances or check the billing information, you must go back to the Resource list page in the user interface to manage the service instances.





 Connect a service to an external app by using the API 



1. Create an instance of the service by calling [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controller?code=gocreate-resource-instance) as shown in the following example request:



* Curl
* Java
* Python
* Go
* Node



curl -X POST https://resource-controller.cloud.ibm.com/v2/resource_instances -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{
"name": "my-instance",
"target": "bluemix-global",
"resource_group": "5g9f447903254bb58972a2f3f5a4c711",
"resource_plan_id": "0be5ad401ae913d8ff665d92680664ed",
"tags": [
"my-tag"
]
}'

CreateResourceInstanceOptions createResourceInstanceOptions = new CreateResourceInstanceOptions.Builder()
.name(resourceInstanceName)
.target(targetRegion)
.resourceGroup(resourceGroup)
.resourcePlanId(resourcePlanId)
.build();

Response<ResourceInstance> response = service.createResourceInstance(createResourceInstanceOptions).execute();
ResourceInstance resourceInstance = response.getResult();

System.out.printf("createResourceInstance() response:n%sn", resourceInstance.toString());

resource_instance = resource_controller_service.create_resource_instance(
name=resource_instance_name,
target=target_region,
resource_group=resource_group,
You might want to remove inactive identities if they are no longer needed. For more information, see [Identifying inactive identities](https://cloud.ibm.com/docs/account?topic=account-id-inactive-identities).
* Why am I required to migrate my resources?

To continue bringing you the best service, hardware, and connectivity, data centers are continually evaluated to ensure that they meet networking, electrical, and other infrastructure standards. The [closing data centers](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure) no longer meet the ongoing standards.
* Do I need to be fully migrated on the date my data center is closed?

Yes. To ensure that you have no interruption in service, we try to allow as much lead time as possible to make the transition easier.
* Will I need to migrate my resources in the future?

We constantly evaluate the quality of our sites to bring you the best and most dependable service. It's possible that we might have other moves as we continue to evaluate some of the older sites.
* How do I select which data center to deploy to?

The following factors might influence which data center you select:



* Proximity to the users of the systems
* Proximity to any other systems that this server needs to communicate with
* Any data policies or regulations that require data to be stored in a specific location



For the list of available data centers, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).
* What data centers can I use during the transition period?

You can use any worldwide IBM Cloud data center during your transition period, which lasts up to 60 days. See [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations) for more information.
* Are the two free months of transition period resources in addition to my existing server time?

Yes. You can [contact an appropriate support representative](https://www.ibm.com/cloud/data-centers?contactmodule=undefined) to help you through the process of acquiring your transition period servers.
Why is my software instance not usable? 

When a software product is removed or temporarily suspended from the IBM Cloud® catalog, any related software instances are not usable.

  What’s happening 

When you access your software instance from your resource list, the following error message is displayed:

> The instance is not usable.

  Why it’s happening 

This problem happens if the software product that is used to create the instance is removed or suspended from the IBM Cloud catalog. Suspension is a temporary state while removal is permanent. In both states, the software instance cannot retrieve necessary information from the product, including updates for new features and fixes for vulnerabilities.

  How to fix it 

In the case of the software being removed from the catalog, you should delete your instance. If necessary, you can create a new instance from a different software product in the catalog.
Finally, click the red Delete button to initiate the request.
* How do I delete a single virtual server instance?

There are two methods to delete a virtual server instance. Both deletion methods are manual processes. There is no way to delete all VSIs without deleting the workspace or deleting a subset of the virtual server instance.



* Delete a single virtual server instance from the Virtual server instances page. Click on the overflow menu (icon with 3 vertical dots) on the far right of each virtual server instance entry on the table. From the pull-down menu, click Delete to open the delete confirmation modal. Click Delete instance to initiate the deletion request. This action cannot be undone.
* Delete a single virtual server instance from the its details page. Navigate to the virtual server instance's details page by clicking on the virtual server instance name on the table on the Virtual server instances page. Find and click on the trash icon on the top right of the screen. Confirm the request by clicking Delete instance. This action cannot be undone.



* How do I open a support ticket for the Power Systems Virtual Server workspace?

To open a support ticket, see [Getting help and support](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-help-and-support).
* What are the supported databases that I can run for SAP on Power Systems Virtual Server?

On an AIX VM, the following databases are supported:



* IBM Db2 for LUW (Linux, UNIX, and Windows) version 10.5, or later
* Oracle Database version 12.1.0.2, or later
* SAP Adaptive Server Enterprise version 16.0 SP03, or later



On a Linux VM, the following database is supported:



* SAP HANA Platform 2.0 SPS 04, or later



You can find an up-to-date list at [SAP Apps on IBM Power Systems Virtual Server](https://launchpad.support.sap.com//notes/2855850).
If you remove the workspace and keep the resources, you need to manage the resources with the resource list or CLI.



delete workspace and associated resource

 Action Delete workspace Delete all associated resources 

 Delete workspace True False 
 Delete only resources False True 
 Delete workspace and the resources provisioned by workspace True True 
 Resources destroyed using command-line or resource list, and want to delete workspace True False 



Syntax

ibmcloud schematics workspace delete --id WORKSPACE_ID [--force]

Command options



Schematics Workspaces delete flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace that you want to remove. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --force or -f Optional Force the deletion of your workspace without command-line prompts. 



Example

ibmcloud schematics workspace delete --id myworkspace-a1aa1a1a-a11a-11





 ibmcloud schematics workspace get 

Retrieve the details of an existing workspace, including the values of all input variables.

Syntax

ibmcloud schematics workspace get --id WORKSPACE_ID [--output OUTPUT]

Command options



Schematics Workspaces get flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace, for which you want to retrieve the details. To find the Resource ID of a workspace, run ibmcloud schematics workspace list command to view the of list service instances. From your resource group get an Resource ID for the --id flag. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 
 --json or -j Deprecated Prints the output in the JSON format. 



Example

ibmcloud schematics workspace get --id myworkspace-a1aa1a1a-a11a-11 --json





 ibmcloud schematics workspace import
"type": "application/vnd.ibm.kms.key+json",
"name": "Root-key-1",
"description": "example-key",
"expirationDate": "'$EXPIRE'",
"extractable": false
}
]
}'
Show more



 JSON response 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.key+json",
"collectionTotal": 1
},
"resources": [
{
"type": "application/vnd.ibm.kms.key+json",
"id": "88d649f8-41b8-4426-b52b-45c88953d5b8",
"name": "Root-key-1",
"description": "example-key",
"state": 1,
"expirationDate": "2020-08-12T23:38:09Z",
"extractable": false,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:key:88d649f8-41b8-4426-b52b-45c88953d5b8",
"imported": false,
"deleted": false
}
]
}

 capture the key id
$ KEY_ID=88d649f8-41b8-4426-b52b-45c88953d5b8

 step 2 - allow the expiration date to pass by sleeping for 1 (one) minute
$ sleep 60

 step 3 - fails because you cannot enable a key after the expiration date