Document repository request lifecycle
This commit is contained in:
@@ -33,6 +33,15 @@ database: such a marker would not create a native repository lock.
|
||||
`repository.lock.confirm` can consume its `request_id`; confirmation always
|
||||
uses the immutable object set stored in the request.
|
||||
|
||||
Manual requests expire after `ONEC_REPOSITORY_REQUEST_TTL_SECONDS` (24 hours
|
||||
by default) and may be explicitly cancelled with
|
||||
`repository.lock.request.cancel`. Manual confirmations expire after
|
||||
`ONEC_REPOSITORY_CONFIRMATION_TTL_SECONDS` (2 hours by default). After the user
|
||||
releases the objects in Configurator, `repository.lock.close` closes the
|
||||
confirmation and immediately blocks further SQL writes through that session.
|
||||
The adapter keeps a bounded audit trail of request creation, confirmation,
|
||||
cancellation, and closure and exposes it to the administrative requests view.
|
||||
|
||||
Both backends invoke standard Designer repository commands. A Karman/Filebox
|
||||
backend is an opaque native TCP transport and does not own credentials, object
|
||||
locks, or repository transactions. For configured bases, saved-state apply is
|
||||
|
||||
Reference in New Issue
Block a user