Delete tag namespace that contains tags
POST {{baseUrl}}/tagNamespaces/:tagNamespaceId/actions/cascadeDelete
Deletes the specified tag namespace. This operation triggers a process that removes all of the tags defined in the specified tag namespace from all resources in your tenancy and then deletes the tag namespace.
After you start the delete operation:
- New tag key definitions cannot be created under the namespace.
- The state of the tag namespace changes to DELETING.
- Tag removal from the resources begins.
This process can take up to 48 hours depending on the number of tag definitions in the namespace, the number of resources that are tagged, and the locations of the regions in which those resources reside.
After all tags are removed, the state changes to DELETED. You cannot restore a deleted tag namespace. After the deleted tag namespace changes its state to DELETED, you can use the name of the deleted tag namespace again.
After you start this operation, you cannot start either the DeleteTag or the BulkDeleteTags operation until this process completes.
To delete a tag namespace, you must first retire it. Use UpdateTagNamespace to retire a tag namespace.
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
if-match | string | For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match | |
| parameter to the value of the etag from a previous GET or POST response for that resource. The resource | |||
| will be updated or deleted only if the etag you provide matches the resource's current etag value. | |||
opc-request-id | string | Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a | |
| particular request, please provide the request ID. | |||
opc-retry-token | string | A token that uniquely identifies a request so it can be retried in case of a timeout or | |
| server error without risk of executing that same action again. Retry tokens expire after 24 | |||
| hours, but can be invalidated before then due to conflicting operations (e.g., if a resource | |||
| has been deleted and purged from the system, then a retry of the original creation request | |||
| may be rejected). | |||
Date | string | (Required) Current Date | |
Authorization | string | (Required) Signature Authentication on Authorization header | |
x-content-sha256 | string | (Required) Content sha256 for POST, PUT and PATCH operations |