Delete Locks

Delete locks prevent accidental deletion of instances and volumes. When you set a delete lock on a resource, any attempt to delete it returns an error until you remove it.

Delete locks apply to:

• Instances
• Instance templates
• Volumes
• Volume templates

Enabling a delete lock

You can set a delete lock on a resource via a PATCH operation. Set UKC_TOKEN and UKC_METRO for the API calls:

Locking an instance
curl -X PATCH \
    -H "Authorization: Bearer $UKC_TOKEN" \
    -H "Content-Type: application/json" \
    "https://api.$UKC_METRO.unikraft.cloud/v1/instances" \
    -d "[{
        'name': '<instance-name>',
        'prop': 'delete_lock',
        'op': 'set',
        'value': true 
    }]"

Removing a delete lock

Before you can delete a resource, you need to remove the delete lock by setting its value to false:

Unlocking an instance
curl -X PATCH \
    -H "Authorization: Bearer $UKC_TOKEN" \
    -H "Content-Type: application/json" \
    "https://api.$UKC_METRO.unikraft.cloud/v1/instances" \
    -d "[{
        'name': '<instance-name>',
        'prop': 'delete_lock',
        'op': 'set',
        'value': false 
    }]"

Behaviour

• Deletion blocked: Any DELETE request on a locked resource returns an error.
• Autokill skipped: The autokill subsystem skips instances and service groups that have a delete lock set.
• Templates: Delete locks are independently configurable on instance templates and volume templates via their respective PATCH endpoints.

Learn more

• The CLI reference and the legacy CLI reference.
• Unikraft Cloud's REST API reference, in particular the sections on instances and volumes.