vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If the service credential used to generate the HMAC credentials (used as the Access Key ID and Secret Access Key configuration above) is deleted, the access for the pre-signed URL will fail.

It is also possible to set an expiration time for the URL in seconds (default is 3600):

$ aws --endpoint-url=https://{endpoint} s3 presign s3://bucket-1/new-file --expires-in 600

It is also possible to construct them programmatically. Here are examples for basic GET operations written in Python. For more information about endpoints, see [Endpoints and storage locations](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints).

Unlike AWS S3, IBM Cloud Object Storage does not enforce a maximum expiration time of 7 days (604800 seconds). While it is possible to create a presigned URL with a long expiration value, most use cases that require extended public access would be better served by [implementing a public access policy](https://cloud.ibm.com/docs/cloud-object-storage/info?topic=cloud-object-storage-iam-public-access) on a bucket instead.



 Create a presigned URL to download an object 



 Python Example 

import ibm_boto3
import os

bucket_name = '<bucekt name>'
key_name = '<object key name>'
http_method = 'get_object'
expiration = 600 time in seconds, default:600

access_key = os.environ.get('COS_HMAC_ACCESS_KEY_ID')
secret_key = os.environ.get('COS_HMAC_SECRET_ACCESS_KEY')
 Current list avaiable at https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints
cos_service_endpoint = 'https://s3.<region>.cloud-object-storage.appdomain.cloud'
│ "no-cache, no-store, must-revalidate"
│ ],
│ "Content-Language": [
│ "en-US"
│ ],
│ "Content-Length": [
│ "534"
│ ],
│ "Content-Type": [
│ "application/json"
│ ],
│ "Date": [
│ "Tue, 12 Jul 2022 14:47:03 GMT"
│ ],
│ "Expires": [
│ "0"
│ ],
│ "Pragma": [
│ "no-cache"
│ ],
│ "Strict-Transport-Security": [
│ "max-age=31536000; includeSubDomains"
│ ],
│ "Transaction-Id": [
│ "aDJwNTQ-fec49a18af674b77a356764b2c633520"
│ ],
│ "X-Content-Type-Options": [
│ "nosniff"
│ ],
│ "X-Correlation-Id": [
│ "aDJwNTQ-fec49a18af674b77a356764b2c633520"
│ ],
│ "X-Proxy-Upstream-Service-Time": [
│ "78"
│ ],
│ "X-Request-Id": [
│ "e74ad79c-e934-40b7-9ced-d7b4b2507f42"
│ ]
│ },
│ "Result": null,
│ "RawResult": "eyJlcnJvckNvZGUiOiJCWE5JTTA0MTVFIiwiZXJyb3JNZXNzYWdlIjoiUHJvdmlkZWQgQVBJIGtleSBjb3VsZCBub3QgYmUgZm91bmQiLCJjb250ZXh0Ijp7InJlcXVlc3RJZCI6ImFESndOVFEtZmVjNDlhMThhZjY3NGI3N2EzNTY3NjRiMmM2MzM1MjAiLCJyZXF1ZXN0VHlwZSI6ImluY29taW5nLklkZW50aXR5X1Rva2VuIiwidXNlckFnZW50IjoiR28taHR0cC1jbGllbnQvMS4xIiwidXJsIjoiaHR0cHM6Ly9pYW0uY2xvdWQuaWJtLmNvbSIsImluc3RhbmNlSWQiOiJpYW1pZC03LjctMTM5NzQtZTYxMmIxYy04NDc0OTU2OWYtaDJwNTQiLCJ0aHJlYWRJZCI6IjM3YWRiIiwiaG9zdCI6ImlhbWlkLTcuNy0xMzk3NC1lNjEyYjFjLTg0NzQ5NTY5Zi1oMnA1NCIsInN0YXJ0VGltZSI6IjEyLjA3LjIwMjIgMTQ6NDc6MDM6NjI5IFVUQyIsImVuZFRpbWUiOiIxMi4wNy4yMDIyIDE0OjQ3OjAzOjY5OSBVVEMiLCJlbGFwc2VkVGltZSI6IjcwIiwibG9jYWxlIjoiZW5fVVMiLCJjbHVzdGVyTmFtZSI6ImlhbS1pZC1wcm9kLWV1LWdiLWxvbjA1In19"
│ }
│
│
│ with data.ibm_is_ssh_key.ssh_key_id[0],
│ on main.tf line 54, in data "ibm_is_ssh_key" "ssh_key_id":
This option supports referencing an entire IAM API key JSON file and you can use the apikey field in the file as the registry password.<br> * Added references to logs and events commands to the outputs for app get, jobrun get, and buildrun get commands.<br><br><br> 
 1.18.0 09 September 2021 <br><br> * Added a prompt to confirm deletion to the reclamation delete command. Also added the --force option to the reclamation delete command to force the deletion without confirmation.<br> * Added the --all-resource-groups option to the project list and reclamation list commands to display projects from all resource groups instead of just the currently targeted resource group.<br> * Updated the output of the project get command to display the resource quota for all projects, not just the currently selected project.<br> * Updated the output of the reclamation get and reclamation list commands to display information about time to hard deletion.<br> * Updated the output for the application get command to display the Cluster Local URL information.<br> * Updated the output for all commands with the --output json option to display JSON in pretty-printed format.<br> * Updated the --wait-timeout option for the project create command to increase the default value to 600 seconds (10 minutes).<br><br><br> 
 1.17.0 31 August 2021 <br><br> * Added the reclamation delete, reclamation get, reclamation list, and reclamation restore commands for managing project reclamations.<br><br><br> 
 1.16.1 24 August 2021 <br><br> * Fixed various bugs.<br><br><br> 
 1.16.0 17 August 2021 <br><br> * Added --wait, --no-wait, and --wait-timeout options to the project create command.<br> * Updated the default timeout value for the project create command from 3 minutes (180 seconds) to 5 minutes (300 seconds).<br> * Updated the project get command output to change the format of the memory and ephemeral storage values to display in gigabytes.<br> * Updated translations for the CLI.<br><br><br>
2. When the instance migration is completed, the instance is displayed on the Resources > vCenter Server page under the account to which it was migrated. The migrated instance is no longer displayed in the original account from which it was migrated.







 Related links 



* [Managing user access with IAM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iamiam)
* [Inviting users to access services and resources](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-useraccountuseraccount-iamuserinv)
* [How IBM Cloud IAM works](https://cloud.ibm.com/docs/account?topic=account-iamoverview)
$template->data = '127.0.0.1';
$template->host = 'server01';
 
$result = $client->editObject($template);
print_r($result);

It is also necessary to populate the init params with the resource record ID property. A Boolean is returned by SoftLayer_Dns_Domain_ResourceRecord::editObject





 Delete records 

Removal of a record is accomplished with SoftLayer_Dns_Domain_ResourceRecord::deleteObject. This method requires only an init parameter to be provided.

$recordId = 1545925;
 
$client = SoftLayer_SoapClient::getClient('SoftLayer_Dns_Domain_ResourceRecord', $recordId, $apiUser, $apiKey);
 
$result = $client->deleteObject();
print_r($result);

SoftLayer_Dns_Domain_ResourceRecord::deleteObject Returns a Boolean value: true for successful, false for failed.
Cleans up a namespace by retaining a specified number of images for each repository within a namespace in IBM Cloud Container Registry. All other images in the namespace are deleted.

You can choose whether to exclude all untagged images from the total number of images that you decide to retain.

Where an image, within a repository, is referenced by multiple tags, that image is counted only once. Newest images are retained. Age is determined by when the image was created, not when it was pushed to the registry.

If you want to restore a deleted image, you can list the contents of the trash by running the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command and restore a selected image by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command.

If an image that you're expecting to see doesn't show in the list that is produced, see [Why doesn't the retention command show all the images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-list-retention) for assistance.

ibmcloud cr retention-run [--force | -f --json]] [--retain-untagged] --images IMAGECOUNT NAMESPACE



 Prerequisites 

To find out about the required permissions, see [Access roles for using Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_using).





 Command options 

NAMESPACE
: The namespace that you want to clean up.

--force, -f
: (Optional) Force the command to run with no user prompts.

--json
: (Optional) Outputs JSON that contains the results of cleaning your namespace. This option must be used with --force.

--retain-untagged
: (Optional) Retain all untagged images when the retention policy is being processed.
You can, however, create instances of other paid plan types (for example, Standard), independent of any free trials you might have created.
* Can I downgrade from Standard to the Free Trial?

No. Downgrading from Standard to a Free Trial plan is not allowed.
* My Free Trial has expired. What are my options?

To avoid any data loss you must upgrade from Free Trial to Standard prior to the expiration date. After that, we only support upgrading the Plan or Deleting the CIS instance. If the instance is not deleted or upgraded after 45 days (from the initiation of the instance) the configuration domain, global load balancers, pools, and health checks are deleted automatically.
* What happened to Enterprise Package plans?

Starting on 21 June 2023, you can no longer configure the Enterprise package plan. The functionality of this plan was split across various tiers and are now available in Enterprise Essential, Enterprise Advanced, and Enterprise Premier plans. See [Transition to Enterprise](https://cloud.ibm.com/docs/cis?topic=cis-transitioning-next-plan).
* How do I delete my CIS instance?

To delete a CIS instance, you must first delete all global load balancers, pools, and health checks. Then delete the associated domain (zone). Go to the Overview page and click the trash can icon next to the domain name located in the Service Details section to start the deletion process.

If you are moving your domain to a different provider, be sure to migrate your DNS records and other configuration information to the new provider before activating the domain there. Activating the domain before migrating from CIS can cause your domain to changed to a [Moved state](https://cloud.ibm.com/docs/cis?topic=cis-domain-moved-status).
* I added a user to my account and gave that user permission to manage Internet Services instance(s). Why is that user facing authentication issues?

It's possible that you did not assign "service access roles" to the user. Note that there are two separate sets of roles:



* Platform access
* Service access
Why can't I delete an initialized service instance? 

You get an error when you delete an initialized service instance.

  What’s happening 

You might receive an error similar to the following one:

> FAILED Error Code: RC-ServiceBrokerErrorResponse Message: Service Broker returned error status code 409

  Why it’s happening 

You haven't cleared (zeroized) the initialized service instance before you delete the instance.

  How to fix it 

The procedure varies depending on the method that you use to initialize the service instance.



*  If you've initialized your service instance through IBM Cloud Trusted Key Entry (TKE) command-line interface (CLI) plug-in, run the following command before you delete the instance:

ibmcloud tke cryptounit-zeroize
*  If you've initialized your service instance through the TKE application, in the user interface of the application, select Imprint mode > Zeroize crypto unit.



After you zeroize the crypto unit, the administrator signature keys and the master key are cleared from the crypto unit, which means you are not able to access any root keys or standard keys that are protected by the master key. Any resources that are associated with the root keys, such as the [Immutable Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable), cannot be accessed.
Note that all resources that are already removed are not re-created. If a resource is currently deleting, Schematics waits for the deletion to complete, and then stops the creation, update, or deletion of any other resources in your Terraform template.
10. Review the log files to ensure that no errors occurred during the deletion process.
11. From the navigation, select Resources and verify that your resources are removed.
12. Optional: After you removed all your resources, remove your workspace.



1. Open the [workspace dashboard](https://cloud.ibm.com/schematics/workspaces) and find the workspace that you want to remove.
2. From the Actions menu, click Delete.
3. Select Delete workspace.
4. Confirm the deletion of your workspace by clicking Delete.





To remove your resources from the Schematics console:



1. From the [workspace dashboard](https://cloud.ibm.com/schematics/workspaces), find the workspace that includes the resources that you want to delete.
2. From the action menu, click Delete.
3. Select Delete workspace and Delete all associated resources to delete the resources and your workspace.
4. Confirm the deletion of your workspace by clicking Delete.
5. From the navigation, select Activity to review the logs for your resource deletion. Ensure that no errors occurred during the deletion process.
6. From the navigation, select Resources and verify that your resources are removed.



After the deletion of your resources is complete, the Schematics Workspaces is removed.
const resourceModel = {
resource_id: serviceidCrn,
};

const params = {
resources: [resourceModel],
tagNames: ["tag_test_1", "tag_test_2"],
tagType: 'user',
};

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



When you tag a service ID, all policies that have resources that are scoped to your access management tag include access to this service ID.





 Detaching tags on a service ID in the console 

To detach a tag from a service ID, complete the following steps:



1. Go to Manage > Access (IAM) > Service IDs.
2. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg) in the Tags column.
3. Click the Remove icon ![Remove icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/delete.svg) on the tag that you want to detach from the service ID..
4. Click Save.



When you detach an access management tag from a service ID, any policies that are scoped that that tag no longer includes access the service ID.





 Detaching tags on a service ID by using the CLI 

To detach a tag on your service ID, use the tag-detach command.
When you enter this input, only enter the domain name of the URL, for example https://<company>.<domain>.com/. If you enter a URL that extends beyond the domain name, or .com/, the input is invalid. Replace <company> and <domain> with the corresponding parts of the organization URL that you want to crawl.
* site_collection_path Optional: - The site_collection_path to the source that you want to crawl. For example, if your organization URL is https://<company>.<domain>.com/sites/test, the /sites/test segment is the input to enter in this field. You cannot enter the full organization URL in this field, and you cannot specify any input that has the extension .aspx, such as URLs to document libaries, lists, and subsites. For example, the following URL to a list is invalid input: https://..com/Lists//AllItems.aspx. If unspecified, the default is /, and the root site collection is crawled.



Note the following items when you crawl Microsoft SharePoint Online:



* To crawl SharePoint, the username account does not need SiteCollection Administrator permissions.
* When you crawl SharePoint, you must have the list of SharePoint site collection paths that you want to crawl. Discovery does not support folder paths as input.
* You might want to use the default Azure AD authentication.
* Because the SharePoint API does not return a unique ID for ListItems, ListItem documents in Discovery are overridden when the IDs of different ListItems are the same. To ensure that your ListItems are not overridden and that each has a unique ID, recrawl your collection, or change the configuration settings for your data source so that your ListItems are assigned a unique ID.
* SharePoint Online cannot crawl Personal SiteCollections.



To successfully crawl Microsoft SharePoint Online, you must enable legacy authentication and Contribute level permissions. To enable legacy authentication, visit the [Azure portal](https://portal.azure.com/), or contact your SharePoint administrator.
[List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI 

By using the CLI, you can delete your existing IBM Cloud® Databases instance with the [ibmcloud resource service-instance-delete](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_delete) command:

ibmcloud resource service-instance-delete my-service-instance

Using the command ibmcloud resource reclamation-delete deletes a reclaimed resource so that the resource can no longer be restored.





 Deleting your database by using DROP DATABASE Statement 

[DROP DATABASE](https://dev.mysql.com/doc/refman/5.7/en/drop-database.html) drops all tables in the database and deletes the database.

DROP {DATABASE | SCHEMA} [IF EXISTS] db_name





 Deleting your database by using mysqladmin 

You can also drop databases with [mysqladmin, a MySQL Server Administration Program](https://dev.mysql.com/doc/refman/5.7/en/mysqladmin.html). Launch mysqladmin like this:

mysqladmin [options] command [command-arg] [command command-arg]] ...





 Cryptoshredding keys 

Key Protect provides for a [force delete](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keys) of a key that is in use by IBM Cloud® services, including your Cloud Databases deployments.
Return only managed keys whose deactivation date is at or before the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, expiration_date_min, and expiration_date_max query parameters. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--expiration-date (string)
: Optional. Return only managed keys whose deactivation date matches the parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--expiration-date-min (string)
: Optional. Return only managed keys whose deactivation date is at or after the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, deactivation_date_min, and deactivation_date_max query parameters. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--expiration-date-max (string)
: Optional. Return only managed keys whose deactivation date is at or before the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, deactivation_date_min, and deactivation_date_max query parameters. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--created-at (string)
: Optional. Return only managed keys whose creation time matches the parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--created-at-min (string)
: Optional. Return only managed keys whose creation time is at or after the parameter value.
After the billing cycle ends, the status of the device changes from ACTIVE to RECLAIM until the reclaim process completes which can take days or weeks into the following month.

After the ESXi server reclaim process completes, the subnets and VLANs are deleted and the instance deletion is completed.

You can review the next account invoice to confirm that you are no longer billed for this instance. From the IBM Cloud console, click Manage > Billing and usage, then click Invoices.



 Procedure to delete vCenter Server instances from the Resources page 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, find the instance to delete.
3. Click the vertical overflow menu next to the Status column, and then click Delete instance. 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 the vertical overflow menu next to the Status column, and then click Delete from the console.
2. In the Delete instance window, click Delete.









 Procedure to delete vCenter Server instances from the instance details page 



1. 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 to delete.
3. Click Actions next to vCenter console, and then click Delete instance. 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
-f, --force
: Force update without confirmation





 Examples 

Rename resource group example-group to trial-group:

ibmcloud resource group-update example-group -n trial-group







 ibmcloud resource group-delete 

Delete an existing resource group

ibmcloud resource group-delete NAME [-f, --force]



 Command options 

NAME (required)
: Name of the target resource group

-f, --force
: Force deletion without confirmation





 Examples 

Delete resource group example-group:

ibmcloud resource group-delete example-group -f







 ibmcloud resource quotas 

List all quota definitions.

ibmcloud resource quotas



 Examples 

List all quota definitions:

ibmcloud resource quotas







 ibmcloud resource quota 

Show details of a quota definition.

ibmcloud resource quota NAME



 Command options 

NAME (required)
: Name of the quota





 Examples 

Show details of quota free:

ibmcloud resource quota free







 ibmcloud resource service-instances 

List service instances.

ibmcloud resource service-instances [--service-name SERVICE_NAME] [--location LOCATION] [--type INSTANCE_TYPE] [-g RESOURCE_GROUP | --all-resource-groups] [--long]



 Command options 

--service-name SERVICE_NAME
: Name of belonging service

--location LOCATION
: Filter by location

--type INSTANCE_TYPE
: Type of instances. service_instance type is used if not specified, use all to list all types of instances.

-g RESOURCE_GROUP
: Resource group name

--all-resource-groups
: Query all resource groups

--long
: Show more fields in output.





 Examples 

List service instances of service test-service:

ibmcloud resource service-instances --service-name test-service







 ibmcloud resource service-instance 

Show details of a service instance.

ibmcloud resource service-instance (NAME|ID) [--location LOCATION] [--id]



 Command options
You can retain an Analytics Engine instance as long as you want and submit your Spark applications against the same instance on an as-needed basis.

If you want to delete an Analytics Engine instance:

Action
: Enter:

ibmcloud resource service-instance-delete NAME|ID [-g RESOURCE_GROUP] -f

Parameter values:



* NAME|ID: The value of Name or GUID from the response of the Analytics Engine instance creation call
* RESOURCE_GROUP: Optional parameter. The name of resource group in which the serverless instance is resides



Example
: Enter:

ibmcloud resource service-instance-delete MyServiceInstance -g default -f





 Learn more 

See the [IBM Analytics Engine serverless CLI reference](https://cloud.ibm.com/docs/AnalyticsEngine?topic=analytics-engine-cli-plugin-CLI_analytics_engine).