vania-janet/multiturn-rag-retrieval-data huggingface dataset:
--header "Content-Type: application/json"
--data '{
"description": "Extended description for this secret.",
"expiration_date": "2030-01-01T00:00:00Z",
"labels": [
"dev", "us-south"
],
"name": "example-arbitrary-secret",
"payload": "secret-data",
"secret_group_id": "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"secret_type": "arbitrary"
}' 
"{base_url}/api/v2/secrets"
Show more







 Migrating to CLI v2 

You can migrate to the Secrets Manager CLI v2. Review the following steps and examples to complete the process.



1. Review the documentation.
2. Download the latest version of the CLI plug-in.
3. Remove the secret type from the command. In some cases, you might need to add it into the resource.
4. Remove the metadata and resources wrapper from the resource JSON object.
5. If you are using jq or other tools, review the difference in the response structure.





 Comparing v1 and v2 CLI examples 

Compare the following examples to see the changes between the v1 CLI code snippet and how the code must look like in v2.

v1 example

ibmcloud secrets-manager secret-create
--secret-type=arbitrary
--resources='[
{
"name": "example-arbitrary-secret",
"description": "Extended description for this secret.",
"secret_group_id": "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"labels":
"dev","us-south"
],
"custom_metadata": {
Response<Void> response = contextBasedRestrictionsService.deleteRule(deleteRuleOptions).execute();

response = context_based_restrictions_service.delete_rule(
rule_id='testString'
)

deleteRuleOptions := contextBasedRestrictionsService.NewDeleteRuleOptions(
"testString",
)

response, err := contextBasedRestrictionsService.DeleteRule(deleteRuleOptions)
if err != nil {
panic(err)
}
if response.StatusCode != 204 {
fmt.Printf("nUnexpected response status code received from DeleteRule(): %dn", response.StatusCode)
}

const params = {
ruleId: 'testString',
};

contextBasedRestrictionsService.deleteRule(params)
.then(res => {
done();
})
.catch(err => {
console.warn(err)
});







 Removing a network zone 

Removing a network zone removes the set of allowed network locations from which an access request is created. If a network zone is added to a rule, you first have to remove the zone from the rule. See [Updating context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-update) for more information about removing a zone from a rule. Then, complete the following steps:



1. In the IBM Cloud console, go to Manage > Context-based restrictions, and select Network zones.
2. Click the Actions icon !
Deleting a service instance 

The procedure that you follow to delete a service instance differs depending on how the instance was deployed.



 Deleting a managed service instance IBM Cloud 

When you delete a Discovery service instance, the data associated with your service is also removed.

Only the owner or someone with Administrator role-level access to the service instance can delete it.

To delete your Discovery service instance, complete the following steps:



1. From the [IBM Cloud Resource list](https://cloud.ibm.com/resources), expand the AI/Machine Learning section.
2. Find the service instance that you want to delete.
3. Click the Actions menu icon, and then select Delete.



The data that is associated with the service instance is retained for 7 days. After the 7-day retention period, it is deleted. If a service instance is deleted by mistake, you can restore it as long as you do so before the 7-day window closes. For more information, see [Using resource reclamations](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation&interface=cli) in the IBM Cloud documentation.

For more information about how data is handled by IBM Cloud, see the following information:



* [Data Processing and Protection Datasheet](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=A1417A507E8211E6BA51E79BE9476040).
* [IBM Cloud Data security and privacy terms](https://www.ibm.com/support/customer/csol/terms/)



For more information about how to delete a deployment of the service from Cloud Pak for Data as a Service, see [Deleting a deployment](https://dataplatform.cloud.ibm.com/docs/content/wsj/analyze-data/ml-deploy-delete.html?audience=wdp).





 Deleting an installed service instance IBM Cloud Pak for Data
ResourceKeysList resourceKeysList = response.getResult();

System.out.printf("listResourceKeys() response:n%sn", resourceKeysList.toString());

resource_keys_list = resource_controller_service.list_resource_keys(
name=key_name
).get_result()

print('nlist_resource_keys() response:n',
json.dumps(resource_keys_list, indent=2))

listResourceKeysOptions := resourceControllerService.NewListResourceKeysOptions()
listResourceKeysOptions = listResourceKeysOptions.SetName(keyName)

resourceKeysList, response, err := resourceControllerService.ListResourceKeys(listResourceKeysOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(resourceKeysList, "", " ")
fmt.Printf("nListResourceKeys() response:n%sn", string(b))

const params = {
name: keyName,
};

resourceControllerService.listResourceKeys(params)
.then(res => {
console.log('listResourceKeys() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});

Example response:

{
"rows_count": 1,
"next_url": null,
"resources": [
{
Otherwise, Satellite disables the ability to log in to the host via SSH for security purposes. You can [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove) and reload the operating system to restore the ability to SSH into the machine.
2. Ensure that the time that is reported by the host does not differ from the actual time by more than 3 minutes. If the time differs by more than 3 minutes, verify your NTP solution with your infrastructure provider.

date +%s
3. Repeat these steps to identify any hosts that have NTP issues.







 R0047: Location health checking 

Location message
: R0047: IBM Cloud is unable to use the health check endpoint to check the location's health.

Steps to resolve
: See [Why is IBM Cloud unable to check my location's health?](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-location-healthcheck).





 R0048: etcd backup failure 

Location message
: R0048: The etcd backup for a cluster in your location failed to complete within the past day.

Steps to resolve
: The etcd data is backed up every 8 hours from your Satellite location control plane to a bucket in your IBM Cloud Object Storage instance. If this backup consecutively fails 3 times over 24 hours, problems might exist with the Object Storage bucket or service instance, or with your Satellite location's connection to the Object Storage instance.

To determine where your problem exists,



1. Ensure that the hosts that you assigned to the location control plane are able to access the IBM Cloud Object Storage endpoint for the IBM Cloud region that your location is managed from. For example, in your host firewall, you must allow outbound connectivity from your control plane hosts to the following endpoints.



Table 1. Required outbound connectivity for hosts to Object Storage endpoints

 Region Object Storage endpoint 

 wdc s3.us.cloud-object-storage.appdomain.cloud 
 lon s3.eu.cloud-object-storage.appdomain.cloud 



2.
For more information, see the [FAQs](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqsdeleted).

Customers with special requirements for compliance such as NIST 800-88 Guidelines for Media Sanitization can perform the data sanitization procedure before they delete their storage.

To delete a storage LUN, it's necessary to revoke access from any hosts first. Active replicas and dependent duplicates can also block reclamation of the Storage volume. Make sure that the volume is no longer mounted, host authorizations are revoked, replication is canceled, and no dependent duplicates exist before you attempt to cancel the original volume.



1. Click Storage > Block Storage for Classic.
2. Select the volume to be canceled, click Actions, and select Delete Block Storage for Classic.
3. Confirm if want to cancel the volume immediately or on the anniversary date of when the LUN was provisioned.

If you select the option to delete the volume on its anniversary date, you can void the cancellation request before its anniversary date.
4. Click Continue.
5. Click the Acknowledgment checkbox and click Confirm.



You can expect the LUN to remain visible in your Storage list for at least 24 hours (immediate cancellation) or until the anniversary date. Certain features aren't going to be available any longer, but the volume remains visible until it is reclaimed. However, billing is stopped immediately after you cancel.

After the Storage LUN is reclaimed, the disk is wiped, and data can't be restored. When drives are decommissioned, IBM destroys them before they can be disposed of. The drives become unusable. Any data that was written to that drive becomes inaccessible.
[SSP-AM-Remove-User-1](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-1.png)
3. Select your IBMid, or if a Manager the user’s IBMid, from the List View that you want to remove the access from.

![SSP-AM-Remove-User-2](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-2.png)

![SSP-AM-Remove-User-2](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-2.png)
4. Select the user’s Manage Access tab to view their existing accesses.

![SSP-AM-Remove-User-3](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Remove-User-3.png)
5. Select the asset from the Assets table that the access is linked to. This will populate all existing and pending accesses for the asset in the Specific Access in the Environment table below.

!
In the row that contains the image that you want to delete, select the checkbox.
6. Click Delete Image.









 Listing images in the trash 

You can list deleted images that are in the trash and see when they expire.

To find out which images are in the trash, you can use the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command. Images are stored in the trash for 30 days.

To list the images in the trash, complete the following steps:



1. Log in to IBM Cloud by running the ibmcloud login command.
2. List the images in the trash by running the following command:

ibmcloud cr trash-list
3. List only the images in the trash for the namespace that you're interested in by running the following command, where <namespace> is your namespace:

ibmcloud cr trash-list --restrict <namespace>







 Restoring images 

You can restore images from the trash. Deleted images are stored in the trash for 30 days.

You can restore an image from the trash by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command. To find out which images are in the trash, run the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command.

You can restore images by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command. You can use the following options:
Deleting the root key means you cannot recover those resources. This is known as "crypto shredding" and there is no recovery from this action. ibmcloud kp registrations
-i, --instance-id INSTANCE_ID
-c, --crn-query CRN_PATTERN]
-k, --key-id KEY_ID]
-o, --output OUTPUT] !
Registrations<-- <section "id="section-kp-registrations-examples" "> --> Examples These are examples of kp registrations.Registration examples show numerous Cloud Resource Names (CRNs). CRNs follow this format:crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resourceSee Cloud Resource Names]] ! for an in-depth explanation of CRN fields.<-- <section "id="section-kp-registrations-example-1" "> --> Example 1 List all registrations, which may include cloud resources such as databases, storage, compute, containers, or messaging.This example shows the registration between Cloud Object Storage (COS) and Key Protect. view all registrations
$ ibmcloud kp registrations --output json


{
"keyId": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8:bucket:my-cos-kms-bucket",
In the OpenID Connect panel, click DELETE.







 Related links 



* [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
* [Ordering virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering)
* [VMware Cloud Director](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-74C9E10D-9197-43B0-B469-126FFBCB5121.html)
For detailed information about the API, see [Resource Manager API](https://cloud.ibm.com/apidocs/resource-controller/resource-managerdelete-resource-group).



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE https://resource-controller.cloud.ibm.com/v2/resource_groups/09f8c1c0742c493f80baaf7835212345 -H 'Authorization: Bearer <IAM_TOKEN>'
-H 'Content-Type: application/json'

String id = '09f8c1c0742c493f80baaf7835212345';
DeleteResourceGroupOptions options = new DeleteResourceGroupOptions.Builder().id(id).build();
Response<Void> response = service.deleteResourceGroup(options).execute();
System.out.println(response):

delete_resource_group(self,
id: str,
kwargs
) -> DetailedResponse

ID := "09f8c1c0742c493f80baaf7835212345"
deleteResourceGroupOptionsModel := service.NewDeleteResourceGroupOptions(ID)
detailedResponse, err := service.DeleteResourceGroup(deleteResourceGroupOptionsModel)

const params = {
id: '09f8c1c0742c493f80baaf7835212345'
};
service.deleteResourceGroup(params).then(response => {
console.log(response)
}).catch(err => {});





 Deleting a resource group by using Terraform 

Before you can delete a resource group by using Terraform, make sure that you have completed the following:



* Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform.
Deleting services from Cyber Recovery instances 

You can delete the services that were provisioned for your Cyber Recovery instances when you no longer need these services.



 Before you delete services from Cyber Recovery instances 

You are billed until the end of the IBM Cloud® infrastructure billing cycle for the deleted services.





 Procedure to delete services from Cyber Recovery instances 



1. From the IBM Cloud for VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click the instance for which you want to delete services.
3. Click the Services tab.
4. Locate the service instance that you want to delete, click the vertical overflow menu next to the Status column, and then click Delete service.
5. In the Remove service window, review the considerations or warnings if there are any and select I Understand. Click Delete.







 Results after you delete services from Cyber Recovery instances 

After your request to delete a service is accepted, the service status is changed to Removing.

When the service deletion is completed successfully, you are notified by email, and the service is deleted from the Services page of the instance.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted services.





 Manually removing the DNS entries for specific services 

After you delete the service, unused DNS entries remain in Active Directory™. These entries do not cause any problems. However, in the future, they might create conflicts with reverse lookups. It is recommended that you remove the entries as soon as possible.

The following table shows the services that are affected and the pattern for hostnames for these services. The hostname might differ from the exact pattern displayed. Use the pattern to locate all the registered DNS hostnames associated with a service. Services might have more than one registered hostname.



Table 1. Hostname patterns and examples for affected services

 Service Hostname Pattern Example 

 Caveonix RiskForesight™ riskforesight riskforesight <br>inst01-riskforesight
From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance for which you want to delete services.
3. Click the Services tab and locate the service instance that you want to delete and click the Delete icon.
4. In the Delete service window, review the considerations or warnings if there are any. Select I understand and click Delete.





 Results after you delete a service 

After your request to delete a service is accepted, the service status is changed to Removing.

When the service deletion is completed successfully, you are notified by email, and the service is deleted from the Services page of the instance.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted services.







 Related links 



* [FAQ](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
The status of the instance is changed to Deleting. When the instance is deleted successfully, the components of the instance are released, and the status of the instance is changed to Deleted.
4. If you want to delete the instance record from the IBM Cloud for VMware Solutions console, complete the following steps:



1. Click Actions again and then click Delete from the console.
2. In the Delete instance window, click Delete.









 Related links 



* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Viewing vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewinginstances)
* [Expanding and contracting capacity for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)
* [Managing virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-servers)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
--address or -adr Required Enter the address of the resource to mark as taint. 



Example

ibmcloud schematics workspace taint --id myworkspace-lalalalalalala-11 --address null_resource.sleep





 ibmcloud schematics workspace untaint 

Manually marks an instance or resources as untainted, by forcing the resources to be restored on the next apply. When you perform next plan the changes will show as restored and in the next apply the change is implemented.

You can execute [ibmcloud schematics state list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencestate-list) command to view the tainted status of your resources. Taint Status returns tainted for (true) or blank for (false).

Syntax

ibmcloud schematics workspace untaint --id WORKSPACE_ID [--options OPTIONS] [--address PARAMETER]

Command options



 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace for which you want to re-create the instance or resource. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --options or -o Optional Enter the option flag that you want to show. 
 --address or -adr Optional Enter the address of the resource to mark as untaint. 
 {: caption="Schematics Workspaces untaint flags" caption-side="top"} 



Example

ibmcloud schematics workspace untaint --id myworkspace-asdff1a1a-42145-11 --address null_resource.sleep





 ibmcloud schematics workspace update 

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).
$ ibmcloud kp key delete $MY_COS_KEY_ID --output json

FAILED
kp.Error:
correlation_id='fffdd8a9-405a-4a91-a5a7-52c30d11424d',
msg='Conflict: Key could not be deleted. Please see "reasons" for more details.',
reasons='PROTECTED_RESOURCE_ERR: Key is protecting one or more cloud resources -
FOR_MORE_INFO_REFER: https://cloud.ibm.com/docs/key-protect?topic=key-protect-troubleshootingunable-to-delete-keys] ! ! ! ! ! ! ! ! ! !
Why can't I delete my secret group? 

You try to use IBM Cloud® Secrets Manager to delete a secret group, but you're unable to complete the action.

  What’s happening 

You have a secret group that you no longer need. When you try to delete it in the Secrets Manager UI, you get the following error:

Delete group failed
An error occurred and the secret group couldn't be deleted.

  Why it’s happening 

Secret groups are a way to organize and assign access policies to your secrets. By deleting a secret group, you render all the secrets in that group useless. For that reason, you cannot delete a secret group that contains secrets.

  How to fix it 

To delete a secret group, delete all the secrets that are associated with it and then delete the group itself.

To learn more about secret groups, check out [Organizing your secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-secret-groups).
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Key could not be deleted. Please 'reasons' for more details.",
"reasons":
{
"code": "AUTHORIZATIONS_NOT_MET",
"message": "The key cannot be deleted because it failed the dual authorization request.",
"status": 409,
"moreInfo":"https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}
Show more





 Example Response 2 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Key could not be deleted. Please 'reasons' for more details.",
"reasons":
{
"code": "PROTECTED_RESOURCE_ERR",
"message": "The key cannot be deleted because the key has one or more associated resources.",
"status": 409,
"moreInfo":"https://cloud.ibm.com/apidocs/key-protect"
}
]
}
]
}
Show more





 Example Response 3 

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.error+json",
"collectionTotal": 1
},
"resources": [
{
"errorMsg": "Key could not be deleted. Please 'reasons' for more details.",
"reasons":
{
"code": "PREV_KEY_DEL_ERR",
* [ibmcloud schematics policy delete](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-policy-delete)



* [Enable BYOK or KYOK commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencekms-commands)



* [Prerequisites](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencekey-prerequisites)
* [ibmcloud schematics kms instance ls](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-kms-list)
* [ibmcloud schematics kms enable](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-kms-enable)
* [ibmcloud schematics kms info](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-kms-info)



* [General commands](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-general-commands)



* [ibmcloud schematics help](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-help-cmd)
* [ibmcloud schematics version](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-version)