Lifecycle Cleanup

Direct upload flows can create orphaned temporary files. A browser may upload to tmp/ and then close before submitting the final command. Lifecycle cleanup deletes stale temporary objects automatically at the provider.

Managed Rule

Default rule ID:

vortos-object-store-expire-temporary-uploads

Default prefix:

tmp/

Default TTL:

86400 seconds

Configure:

$config->bucketConfig()
    ->temporaryKeyPrefix('tmp')
    ->orphanTtlSeconds(86400);

$config->lifecycle()
    ->enabled(true)
    ->manageTemporaryUploads(true)
    ->ruleId('vortos-object-store-expire-temporary-uploads')
    ->requireConfirmation(true);

Commands

Show current provider lifecycle rules:

php bin/console vortos:object-store:lifecycle show
php bin/console vortos:object-store:lifecycle show --json

Plan changes:

php bin/console vortos:object-store:lifecycle plan
php bin/console vortos:object-store:lifecycle plan --json

Apply:

php bin/console vortos:object-store:lifecycle apply --confirm

Remove the managed rule:

php bin/console vortos:object-store:lifecycle remove --confirm

Dry-run mutations:

php bin/console vortos:object-store:lifecycle apply --dry-run
php bin/console vortos:object-store:lifecycle remove --dry-run

Enterprise Safety Behavior

The lifecycle manager reads existing provider lifecycle config, modifies only the Vortos-managed rule, preserves unrelated rules, and writes the merged configuration back.

It does not run automatically during:

• HTTP requests.
• Worker boot.
• Container compilation.
• Cache warmup.

Infrastructure mutation belongs in deployment or operations workflows.

Recommended Policy

• Put all direct uploads under tmp/.
• Set lifecycle cleanup to one day unless your UX requires longer resumability.
• Promote valid uploads to permanent keys after the domain command succeeds.
• Never use tmp/ as a permanent prefix.
• Alert on unusually high tmp/ object growth because it may indicate frontend failures or abuse.