vania-janet/multiturn-rag-retrieval-data huggingface dataset:
resource "ibm_cm_offering_instance" "cm_offering_instance" {
catalog_id = "catalog_id"
label = "label"
kind_format = "operator"
version = "version"
cluster_id = "cluster_id"
cluster_region = "cluster_region"
cluster_namespaces = [ "cluster_namespaces", "cluster_namespaces"]
cluster_all_namespaces = false
}

You can specify a delete timeout for the ibm_cm_offering_instance resource. For more information, see the timeout reference details on the [Terraform Catalog Management](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cm_offering_instancetimeouts) page.
2. Initialize the Terraform CLI.

terraform init
3. Run terraform plan to generate a Terraform execution plan to preview the proposed actions. The Terraform execution plan summarizes all the actions that need to be run to delete the software instance.

terraform plan
4. Delete the software instance.

terraform apply
<br> <br>For example, if you have multiple registrations in your instance, and you want to list only registrations where preventKeyDeletion is true, use ../registrations?preventKeyDeletion=true. <br> <br>You can also pair preventKeyDeletion with offest, limit, and urlEncodedResourceCRNQuery to search through your available resources. 
 urlEncodedResourceCRNQuery The resource CRN that you want to filter registrations by. <br> <br>For example, if you have multiple registrations in your instance, and you want to only view registrations that are associated with a specific Cloud Resource Name (CRN), use ../registrations?urlEncodedResourceCRNQuery="url_encoded_CRN". <br> <br>For more information, see [CRN query examples](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resourcescrn-query-examples). <br> <br>You can also pair urlEncodedResourceCRNQuery with offest, limit, and preventKeyDeletion to search through your available resources. 



You can also filter for a subset of registrations by specifying the limit and offset parameters at query time.

You can use the following example request to retrieve a different set of registrations.

$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys/registrations?offset=<offset>&limit=<limit>" -H "accept: application/vnd.ibm.collection+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the limit and offset variables in your request according to the following table.



Table 8. Describes the limit and offset variables.

 Variable Description 

 offset The number of registrations to skip.
"creationDate": "2010-01-12T05:23:19+0000",
"updatedBy": "string",
"lastUpdated": "2010-01-12T05:23:19+0000",
"description": "string",
"preventKeyDeletion": true,
"keyVersion": {
"id": "string",
"creationDate": "2010-01-12T05:23:19+0000"
}
},
{
"keyId": "string",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/<account-id>:<service-instance>:bucket:<other-bucket-name>",
"createdBy": "string",
"creationDate": "2010-01-12T05:23:19+0000",
"updatedBy": "string",
"lastUpdated": "2010-01-12T05:23:19+0000",
"description": "string",
"preventKeyDeletion": true,
"keyVersion": {
"id": "string",
"creationDate": "2010-01-12T05:23:19+0000"
}
}
]
}

The resourceCrn value represents the unique identifier of the cloud resource that is encrypted by keyId. The metadata that is associated with the registration, such as the creation date, is also returned in the response body.

By default, GET api/v2/keys/registrations returns the first 200 registrations, but you can adjust this limit by using the limit parameter at query time.







 Listing registrations for any root keys with the API 

You can also retrieve a list of registrations that are associated with any cloud resource by making a GET call to the following endpoint.
Depending on the size of the image, it might take a while for the image to be removed and for the storage to be available.



1. Find the names of the images that you want to remove.



* To list only tagged images, run the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) command. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag. If the listing images command times out, see [Why is it timing out when I list images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-timeout) for assistance.

ibmcloud cr image-list
* To list both tagged and untagged images, you must list the images by [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) in all your namespaces of your IBM Cloud account. To list the images by digest, run the [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) command. Combine the content of the Repository column (repository) and the Digest column (digest) separated by an at (@) symbol to create the image name in the format repository@digest.

ibmcloud cr image-digests



2. You can remove images individually, collectively, or by using retention policies.



* To remove images individually from your namespace, use the [ibmcloud cr image-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_rm) command. Replace <image_name> with the name of the image that you want to remove. The name must be in the format repository@digest or repository:tag. If a tag is not specified in the image name, the image that is tagged latest is deleted by default.
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/cli?topic=cli-containerregclibx_cr_trash_list) command and restore a selected image by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/cli?topic=cli-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. Only tagged images are analyzed and, if the images don't meet the criteria, they are deleted. If the option isn't specified, all tagged and untagged images are analyzed and, if the images don't meet the criteria, they are deleted.

--images
: Determines how many images to keep within each repository in the specified namespace. The newest images are retained. The age of images is determined by their build date.
You can explicitly specify [http://example.com](http://example.com) or better yet ensure that HTTPS was selected when creating the CDN and https:// URL references to the CDN content were pasted into the index.html file in the previous step.







 Step 5: Remove resources 

To clean up resource, perform the following steps:



* Delete the [IBM® Content Delivery Network service](https://cloud.ibm.com/cdn).
* Delete the [IBM Cloud Object Storage bucket and / or service](https://cloud.ibm.com/resources).



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 



* [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage)
* [Manage Access to IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam)
* [Getting Started with CDN](https://cloud.ibm.com/docs/CDN?topic=CDN-getting-startedgetting-started)
-ir, --is-reclaimed
: Search for account resources that have been reclaimed. By default the search returns only active resources, however you can set is-reclaimed to any to search for resources whether they have been reclaimed or not. Set this option to true to apply the search criteria only to reclaimed resources. Set this option to false to search only for active resources. false is the default behavior.

-o, -offset
: Starting resource position number

-l, -limit
: Number of resources to return, up to a maximum of 10000.

-s, --sort-by
: Property to sort by. Accepted values are name, family, region, type, crn.

-p, --provider
: Display classic infrastructure resources. The only supported value is classic-infrastructure.





 Searchable attributes 

You can search for the following attributes:

name
: The user-defined name of the resource.

region
: The geographical location where the resource is provisioned. For example: us-south, us-east, au-syd, eu-gb, eu-de, and jp-tok.

service_name
: The name of the service as it appears in the Name column of the output of 'ibmcloud catalog service-marketplace'.

family
: The cloud component to which your resource belongs. The allowed values are containers, resource_controller, vmware, or ims.

doc.resource_group_id
: The ID of the resource group.

type
: The resource type. The allowed values are k8-cluster, resource-instance, resource-alias, resource-binding, resource-group, vmware-solutions, cloud-objects-storage-infrastructure, block-storage, file-storage, cloud-backup.

creation_date
: The date on which the resource is created.

modification_date
: The last modification date of the resource. It is in the format yyyy-mm-ddThh:mm:ssZ

_objectType
: The type of the classic infrastructure resource.
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/action-menu-icon.svg) for the instance you want to delete and select Delete.



Next, remove permissions that are granted to users to work with the instance that you deleted.





 Removing an instance through the CLI 

To remove an instance of IBM Cloud Activity Tracker through the command line, complete the following steps:



1. [Pre-requisite] Install the IBM Cloud CLI.

For more information, see [Installing the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2. Log in to IBM Cloud. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)
3. Get information about the instance that you plan to delete.

ibmcloud resource service-instance INSTANCE-NAME --output JSON
4. Remove any service key associated with the instance.

Find the service keys that are associated with an instance:

ibmcloud resource service-keys --instance-id INSTANCE-GUID

Run the following command to delete 1 service key. You must delete all.

ibmcloud resource service-key-delete SERVICE-KEY-NAME
5. Remove the instance. Run 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 NAME

Where NAME is the name of the instance.

For example, to remove an instance, run the following command:

ibmcloud resource service-instance-delete logging-instance-01
If the name is not set, the context instance specified by ibmcloud dns instance-target is used.

-f, --force
: Delete resource record without prompting for confirmation.







 ibmcloud dns resource-records 

List all resource records for a DNS zone.

ibmcloud dns resource-records ZONE_ID [-i, --instance INSTANCE] [--output FORMAT]



 Command options 

ZONE_ID
: The ID of the DNS zone.

--page
: Page number of paginated results. (default 1)

--per-page
: Number of resource records per page. Min: 50. Max: 1000. (default 200)

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Command example 

List resource records with pagination:

ibmcloud dns resource-records ZONE_ID --per-page 1000 --page 1





 Example command to list resource records with pagination 

ibmcloud dns resource-records ZONE_ID --per-page 1000 --page 1







 ibmcloud dns resource-records-import 

Import resource records from BIND zone file.

ibmcloud dns resource-records-import DNS_ZONE_ID (--file FILE) [-i, --instance INSTANCE_NAME | INSTANCE_ID] [--output FORMAT]



 Command options 

DNS_ZONE_ID
: The ID of DNS zone.

--file
: BIND zone file to import. Support type: A, AAAA, CNAME, MX, PTR, SRV, TXT.

-i, --instance
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Examples
-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat subscription ls







 ibmcloud sat subscription rm 

Remove a subscription.

The Kubernetes resources for the subscription, such as pods and services, are deleted from all your subscribed clusters that are registered in Satellite. Before you remove a subscription, make sure that you do not need these resources. The Satellite configuration remains, so if you want to restore the resources, you can create another subscription.

ibmcloud sat subscription rm --subscription SUBSCRIPTION [-f] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Subscription resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--subscription SUBSCRIPTION
: Required. The name or ID of your subscription. To list subscriptions in your IBM Cloud account, run ibmcloud sat subscription ls.

-f
: Optional. Force the command to run with no user prompts.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat subscription rm --subscription myapp_prod_subscription







 ibmcloud sat subscription update 

Update a subscription, such as to change the subscription name, the configuration version, or the subscribed cluster group. After you update the subscription, the configuration version is automatically deployed to all subscribed clusters.

ibmcloud sat subscription update --subscription SUBSCRIPTION [--name NAME] [--group GROUP] [--version VERSION] [-f] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Subscription resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--subscription SUBSCRIPTION
: Required.
ibm_compute_vm_instance.vm1: Refreshing state... (ID: 60948867)
An execution plan has been generated and is shown here.
Resource actions are indicated with the following symbols:
- destroy

Terraform on IBM Cloud performs the following actions:

- ibm_compute_vm_instance.vm1

Plan: 0 to add, 0 to change, 1 to destroy.

Do you really want to destroy?
Terraform on IBM Cloud destroys all your managed infrastructure, as shown above.
There is no undo. Only 'yes' is accepted to confirm.

Enter a value: yes

ibm_compute_vm_instance.vm1: Destroying... (ID: 60948867)
ibm_compute_vm_instance.vm1: Still destroying... (ID: 60948867, 10s elapsed)
ibm_compute_vm_instance.vm1: Destruction complete after 14s
Destroy complete! Resources: 1 destroyed.
4. Verify that your IBM Cloud resources are removed.

terraform show
[ibmcloud is key-delete](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-reference&interface=clikey-delete) After you remove an SSH key, it can no longer be used when you provision an instance or when you perform an OS reload on an existing instance. However, the key is still available on any instances that you previously provisioned with it, and you can use it to log in. 







 Managing SSH keys by using the API 

You can also manage your SSH keys by using the API. For more information about the $vpc_api_endpoint and $iam_token variables in the following examples, see the Authentication and Endpoint URLs sections in [Virtual Private Cloud API Introduction](https://cloud.ibm.com/apidocs/vpcabout-vpc-api).





 Listing all your SSH keys by using the UI 

To list all your SSH keys, complete the following steps.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > SSH keys.
2. Any existing SSH keys are displayed.







 Listing all your SSH keys by using the CLI 

To view all of your existing SSH keys, use the ibmcloud is keys command.

Use the --all-resource-groups option to list the SSH keys for all available resource groups. Optionally, you can filter the list to include only SSH keys for a specific resource group. Specify the resource group by using the RESOURCE_GROUP_ID or RESOURCE_GROUP_NAME variable. For more information, see [ibmcloud is keys](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencekeys-list).
"expired_issues": 134, 132, 342], // link(s) to the issues for which the grace period expired
"required": "yes"|"no"]// yes: this is an auditable step; no: this is a non auditable step
// there could be other artifacts that serve as build input
}, {
// build output: images or config files, calico policies...
// Partial: CM-5(3) ACCESS RESTRICTIONS FOR CHANGE | SIGNED COMPONENTS
// The information system prevents the installation of Assignment: organization-defined software and firmware components]
// without verification that the component has been digitally signed using a certificate that is recognized and approved by
// the organization.
// Partial: SI-7(6) SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITY | CRYPTOGRAPHIC PROTECTION
// The information system implements cryptographic mechanisms to detect unauthorized changes to software, firmware, and information.
// Partial: SI-7(15) SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITY | CODE AUTHENTICATION
// The information system implements cryptographic mechanisms to authenticate Assignment: organization-defined software or firmware components] prior to installation.
// Control passed if:
// 1- the script is one of the blessed ones AND
// 2- the signature is verified OR
// 3- the signatures are not verified AND issues have been opened AND prod CR approved manually
"evidence_type_id": "com.ibm.images_signature",
"version": "1.0.0",
"date": "2020-05-06T12:00:00Z", // date of task run
"origin": {
"url":"https://us-south.git.cloud.ibm.com/open-toolchain/compliance-pipelines/-/blob/master/definitions/mytask.yaml", // where the task is taken from
"version": "423792" // commit id representing the task version used to produce the evidence
}
"id": "12e8c9c2-a162-472d-b7d6-8b9a86b815a6",
"creationDate": "2010-01-12T05:23:19+0000"
}
},
{
"keyId": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/<account-id>:<service-instance>:bucket:<other-bucket-name>",
"createdBy": "IBMid-25555555",
"creationDate": "2010-01-12T05:23:19+0000",
"updatedBy": "IBMid-25555555",
"lastUpdated": "2010-01-12T05:23:19+0000",
"description": "A description of the registration",
"preventKeyDeletion": true,
"keyVersion": {
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"creationDate": "2010-01-12T05:23:19+0000"
}
}
]
}

The resourceCrn value represents the unique identifier of the cloud resource that is encrypted by keyId. The metadata that is associated with the registration, such as its creation date, is also returned in the response body.

By default, GET api/v2/keys/registrations returns the first 200 registrations, but you can adjust this limit by using the limit parameter at query time.



 Filter registrations for a specific root key 

You can filter for a set of registrations that are associated with a root key by specifying the preventKeyDeletion and urlEncodedResourceCRNQuery parameters at query time.
Why does the Ingress status show an ESSEF error? 

Virtual Private Cloud

Classic infrastructure

Satellite

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The Opaque secret field expired or will expire soon (ESSEF).

  Why it’s happening 

You have secrets in your cluster that have fields which are either expired or are about to expire in the next 5 days.

  How to fix it 

Review the secrets in your cluster and update or remove them.



1.  List your secrets.

ibmcloud ks ingress secret ls
2.  Complete the steps depending on whether the secret fields are still needed or not. If the expiring secret field in the secret is still needed, ensure the corresponding secret in the IBM Cloud Secrets Manager instance has been updated and has a new expiry date. Then, update the secret field with the new values from IBM Cloud Secrets Manager by running the following command.

To view all the secrets in your IBM Cloud Secrets Manager instance, see [Accessing Secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-access-secrets&interface=uiget-secret-value-ui).

ibmcloud ks ingress secret update
3.  If the secret in the secret field is expiring because it is no longer needed, run the ibmcloud ks ingress secret field rm command to remove it.
4.  If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
For more information, see [Manually removing the DNS entries](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingservicesvc_deletingservices-DNS-entries).







 Related links 



* [Ordering F5 BIG-IP](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-f5_ordering)
* [Managing F5 BIG-IP](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managing_f5)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
* [FAQ](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
* [F5 website](https://www.f5.com/)
"service": "cloud-object-storage",
"timeouts": null
},
"sensitive_values": {
"extensions": {},
"last_operation": {},
"plan_history": ],
"tags": ]
}
}
],
"address": "module.instance"
},
{
"resources":
{
"address": "module.instance_config.ibm_cos_bucket.bad_resource_cos_bucket_missing_all_configuration0]",
"mode": "managed",
"type": "ibm_cos_bucket",
"name": "bad_resource_cos_bucket_missing_all_configuration",
"index": 0,
"provider_name": "registry.terraform.io/ibm-cloud/ibm",
"schema_version": 0,
"values": {
"activity_tracking": ],
"allowed_ip": null,
"archive_rule": ],
"cross_region_location": null,
"endpoint_type": "public",
"expire_rule": ],
"force_delete": true,
"key_protect": null,
"metrics_monitoring": ],
"region_location": "us-south",
"retention_rule": ],
"single_site_location": null,
"storage_class": "standard",
"timeouts": null
},
"sensitive_values": {
"activity_tracking": ],
"archive_rule": ],
"expire_rule": ],
"metrics_monitoring": ],
"retention_rule": ]
}
},
{