service
Business logic for the pending change queue: proposal, approval, and application workflows.
PendingQueueService
High-level orchestration around the pending queue store.
Source code in src/horde_model_reference/pending_queue/service.py
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 | |
__init__
Initialize the service with its storage backend and audit writer.
enqueue_change
enqueue_change(
*,
category: MODEL_REFERENCE_CATEGORY,
model_name: str,
operation: AuditOperation,
payload: dict[str, Any] | None,
requestor_id: str,
requestor_username: str,
notes: str | None = None,
request_metadata: dict[str, Any] | None = None,
related_models: list[str] | None = None,
) -> PendingChangeRecord
Create a new pending change entry.
Source code in src/horde_model_reference/pending_queue/service.py
get_change
list_changes
list_changes(
*,
queue_filter: PendingQueueFilter | None = None,
offset: int = 0,
limit: int | None = None,
) -> PendingQueuePage
Return filtered queue entries plus pagination metadata.
Source code in src/horde_model_reference/pending_queue/service.py
purge_changes
purge_changes(
*,
queue_filter: PendingQueueFilter | None,
purged_by: str,
purged_username: str,
) -> list[PendingChangeRecord]
Remove queued changes matching a filter and emit audit entries.
Source code in src/horde_model_reference/pending_queue/service.py
process_batch
process_batch(
*,
approver_id: str,
approver_username: str,
batch_title: str,
approved_ids: Collection[int] | None,
rejected_ids: Collection[int] | None,
reject_reason: str | None = None,
) -> PendingBatchResult
Approve and/or reject subsets of the current pending queue.
Batch ID Semantics: - All approved-but-unapplied changes share the same batch ID. - When approving new changes, they join the existing open batch if one exists. - A new batch ID is only created when no APPROVED changes exist (i.e., all previous batches have been fully applied or this is the first approval). - After partial batch application, remaining APPROVED changes are reassigned to a new batch ID (see mark_applied and _handle_partial_batch_apply).
Source code in src/horde_model_reference/pending_queue/service.py
126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 | |
mark_applied
mark_applied(
*,
change_id: int,
applied_by: str,
applied_username: str,
job_id: str | None = None,
) -> MarkAppliedResult
Mark an APPLYING change as APPLIED by a downstream job.
Batch Split Semantics: - After applying a change, if other APPROVED changes remain in the same batch, this constitutes a "partial apply" and those changes are reassigned to a new batch ID. - This ensures that the next approval operation creates a fresh batch rather than mixing with partially-applied batches. - A 'batch_split' audit event is emitted when reassignment occurs.
Returns:
-
MarkAppliedResult–MarkAppliedResult containing the updated record and any batch split info.
Source code in src/horde_model_reference/pending_queue/service.py
_handle_partial_batch_apply
Reassign remaining APPROVED changes to a new batch after partial application.
When a batch is partially applied (some changes applied, others still APPROVED), the remaining APPROVED changes must be moved to a new batch ID. This ensures: 1. The partially-applied batch is "closed" and won't receive new approvals. 2. Future approvals will create or join a new batch. 3. The audit trail clearly shows the batch split event.
Parameters:
-
original_batch_id(int) –The batch ID that was partially applied.
-
applied_by(str) –The user ID who triggered the partial application.
Returns:
-
BatchSplitInfo | None–BatchSplitInfo if a split occurred, None if the batch was fully applied.
Source code in src/horde_model_reference/pending_queue/service.py
_require_pending
reserve_for_apply
Reserve an approved change for application using a reservation id.
Source code in src/horde_model_reference/pending_queue/service.py
clear_apply_reservation
Release a reservation when an apply attempt fails.
Source code in src/horde_model_reference/pending_queue/service.py
scan_stuck_applying
Detect records stuck in APPLYING state after a crash and revert them.
Should be called once on startup. Each stuck record is reverted to APPROVED so it can be retried, and a warning is logged.
Returns:
-
list[PendingChangeRecord]–The records that were reverted.