Create a new patch against a source resource.
Records a patch definition with compatibility constraints. The patch can later be applied to any compatible resource.
Returns: Created patch record with generated ID.
Request body for creating a new patch.
Attributes: definition: Patch content describing the action and parameters. constraints: Compatibility constraints for target resource eligibility.
Definition of a patch to apply to a resource.
Patches are migration scripts, schema diffs, or configuration changes that can be applied to a resource. They include compatibility constraints to ensure they are only applied to eligible resources.
Attributes: patch_id: Unique identifier for this patch. description: Human-readable description of what this patch does. constraints: Compatibility constraints the resource must satisfy. payload: Patch-specific data (e.g., migration script, schema diff). metadata: Additional context about the patch (author, source, etc.).
Successful Response
A patch record stored in SurrealDB.
Patches are migration scripts, schema diffs, or configuration changes recorded against a source resource. They can be applied to any compatible resource that satisfies the declared constraints.
Attributes: patch_id: Unique identifier for this patch. resource_id: SurrealDB ID of the source resource this patch was created against. definition: Patch content (action, parameters, description). constraints: Compatibility constraints for target resource eligibility. status: Current lifecycle status (pending, applied, failed). created_by: User or agent ID that created the patch. created_at: When the patch was created. error: Error message if patch application failed.
Definition of a patch to apply to a resource.
Patches are migration scripts, schema diffs, or configuration changes that can be applied to a resource. They include compatibility constraints to ensure they are only applied to eligible resources.
Attributes: patch_id: Unique identifier for this patch. description: Human-readable description of what this patch does. constraints: Compatibility constraints the resource must satisfy. payload: Patch-specific data (e.g., migration script, schema diff). metadata: Additional context about the patch (author, source, etc.).
Lifecycle status of a patch record.
Attributes: PENDING: Patch recorded but not yet applied. DISPATCHED: Patch event sent to provider, awaiting confirmation. APPLIED: Patch confirmed applied by the provider. FAILED: Patch application failed.
pending, dispatched, applied, failed