Table of Contents

Interface IErasureSchemaValidator

Namespace
Excalibur.Compliance
Assembly
Excalibur.Compliance.Abstractions.dll

Implemented by an erasure store whose backing schema can be verified — or provisioned — before the store serves its first request.

public interface IErasureSchemaValidator

Remarks

Schema provisioning is a configuration concern, so it is settled once at startup rather than on the path of every write. A store that verified its schema inside SaveRequestAsync reports a deployment fault as a failure of that one erasure request, at the moment a data subject's request is being filed and to a caller with no way to tell the two apart.

The hosted service registered by AddErasureSchemaValidation() calls every registered validator during host startup, so a mis-provisioned deployment fails to start instead of failing one erasure request at a time. Stores keep a first-use check as the fail-closed floor for consumers that never run that hosted service.

Methods

ValidateSchemaAsync(CancellationToken)

Verifies the store's backing schema, provisioning it first if the store is configured to do so.

ValueTask ValidateSchemaAsync(CancellationToken cancellationToken)

Parameters

cancellationToken CancellationToken

A token to observe while awaiting the verification.

Returns

ValueTask

A task that completes when the schema has been verified.

Exceptions

ErasureStoreNotProvisionedException

A required table is absent, or is present but missing columns this store's statements bind, and automatic provisioning is disabled.